CODEWITHSUNDEEP
c#azureazure-functionsazure-application-insightsazure-functions-runtime
DevPerson
DevPerson

Reputation: 419

Application Insight Logging for Azure Functions in C#

We have Service Bus Triggered Azure function in C#. I want to log information (Such as Function called, Result, Exception) in Application Insight. I have converted TraceWriter to Ilogger for loggin information. What I want to achieve is logging at console (on local) as well as on Application insight instance also. What is the perfect way to achieve this? 

    public static class AIFunction
{
    private static string key = TelemetryConfiguration.Active.InstrumentationKey = "************************";

    private static TelemetryClient telemetryClient =
        new TelemetryClient() { InstrumentationKey = key };

    [FunctionName("AIFunction")]
    public static void Run([ServiceBusTrigger("AIFunctionQueue", AccessRights.Manage, Connection = "ServiceBus")]string queueItem, ILogger log)
    {
        telemetryClient.Context.Cloud.RoleName = "AIFunction";
        log.LogInformation($"C# ServiceBus queue trigger function processed message: {queueItem}");
        log.LogInformation($"C# ServiceBus queue trigger function to test Application Insight Logging");
        telemetryClient.TrackEvent("AIFunction TrackEvent");
        telemetryClient.TrackTrace("AIFunction TrackTrace");
    }
}

Upvotes: 1

Views: 6115

Answers (1)

kamil-mrzyglod
kamil-mrzyglod

Reputation: 5008

You can just inject TraceWriter additionally:

private static string key = TelemetryConfiguration.Active.InstrumentationKey = "";

private static TelemetryClient telemetryClient =
    new TelemetryClient() { InstrumentationKey = key };

[FunctionName("Function1")]
public static async Task<HttpResponseMessage> Run(
    [HttpTrigger(AuthorizationLevel.Anonymous, "get", "post", Route = null)] HttpRequestMessage req,
    ILogger log,
    TraceWriter writer)
{
    telemetryClient.Context.Cloud.RoleName = "AIFunction";
    log.LogInformation($"C# ServiceBus queue trigger function processed message: ");
    log.LogInformation($"C# ServiceBus queue trigger function to test Application Insight Logging");
    writer.Info("C# ServiceBus queue trigger function processed message: ");
    writer.Info("C# ServiceBus queue trigger function to test Application Insight Logging");
    telemetryClient.TrackEvent("AIFunction TrackEvent");
    telemetryClient.TrackTrace("AIFunction TrackTrace");

    return req.CreateResponse(HttpStatusCode.OK, "Hello!");
}

Output:

[19.04.2018 06:41:06] Executing HTTP request: {
[19.04.2018 06:41:06]   "requestId": "d193e55d-305f-4a0c-9f17-40c0a062500a",
[19.04.2018 06:41:06]   "method": "GET",
[19.04.2018 06:41:06]   "uri": "/api/Function1"
[19.04.2018 06:41:06] }
[19.04.2018 06:41:06] Function started (Id=568798ce-f15f-4d8c-ac2b-c92aa47047a5)
[19.04.2018 06:41:06] Executing 'Function1' (Reason='This function was programmatically called via the host APIs.', Id=568798ce-f15f-4d8c-ac2b-c92aa47047a5)
[19.04.2018 06:41:06] C# ServiceBus queue trigger function processed message:
[19.04.2018 06:41:06] C# ServiceBus queue trigger function to test Application Insight Logging
[19.04.2018 06:41:07] Function completed (Success, Id=568798ce-f15f-4d8c-ac2b-c92aa47047a5, Duration=197ms)
[19.04.2018 06:41:07] Executed 'Function1' (Succeeded, Id=568798ce-f15f-4d8c-ac2b-c92aa47047a5)
[19.04.2018 06:41:07] Executed HTTP request: {
[19.04.2018 06:41:07]   "requestId": "d193e55d-305f-4a0c-9f17-40c0a062500a",
[19.04.2018 06:41:07]   "method": "GET",
[19.04.2018 06:41:07]   "uri": "/api/Function1",
[19.04.2018 06:41:07]   "authorizationLevel": "Anonymous",
[19.04.2018 06:41:07]   "status": "OK"
[19.04.2018 06:41:07] }

If you want to log only locally you can change Info method to e.g. Verbose:

writer.Verbose("C# ServiceBus queue trigger function processed message: ");
writer.Verbose("C# ServiceBus queue trigger function to test Application Insight Logging");

And then update your local host.json file:

{
  "tracing": {
    "consoleLevel": "verbose"
  }
}

But personally I don't find it useful once you've implemented Application Insights.

Upvotes: 5

Related Questions