TelemetryConfiguration.Active is deprecated

Question

TelemetryConfiguration.Active is deprecated

mikegoatly opened this issue 5 years ago · 72 comments

Context: I've been working to upgrade some applications to .NET Core 3.0 - this has led me to update a number of packages as well, including App Insights.

Previously the recommendation was to configure AppInsights and Serilog together using the IHostBuilder in Program.cs, e.g.:

return builder
    .UseApplicationInsights()
    .UseSerilog((context, configuration) =>
{
    var telemetry = TelemetryConfiguration.Active;

    configuration
        .ReadFrom.Configuration(context.Configuration)
        .MinimumLevel.Override("Microsoft.AspNetCore.Authentication", LogEventLevel.Information)
        .Enrich.FromLogContext()
        .WriteTo.Console(outputTemplate: "[{Timestamp:HH:mm:ss} {Level}] {SourceContext}{NewLine}{Message:lj}{NewLine}{Exception}{NewLine}", theme: AnsiConsoleTheme.Literate)
        .WriteTo.ApplicationInsights(telemetry, new TraceTelemetryConverter());
},
writeToProviders: true);

But after upgrading to the latest AppInsights, I'm starting to get the warnings (as errors):

'ApplicationInsightsWebHostBuilderExtensions.UseApplicationInsights(IWebHostBuilder)' is obsolete: 'This method is deprecated in favor of AddApplicationInsightsTelemetry() extension method on IServiceCollection.'

and

'TelemetryConfiguration.Active' is obsolete: 'We do not recommend using TelemetryConfiguration.Active on .NET Core. See https://github.com/microsoft/ApplicationInsights-dotnet/issues/1152 for more details'

The first can be overcome by configuring App Insights during ConfigureServices, but I'm left a bit stumped as to how to configure Serilog without TelemetryConfiguration.Active - is there a recommended way to do this?

Apologies if I've missed something in the documentation - I couldn't spot anything relevant to this.

Answer 1 · 2019-09-30T13:35:34.000Z

Yes, this is puzzling. Logging is set up in UseSerilog, but the logging setup depends on a telemetry configuration that isn't set up before ConfigureServices (in the call to AddApplicationInsightsTelemetry).

Any insights are most welcome.

Related: serilog/serilog-aspnetcore#84

Answer 2 · 2019-10-01T12:07:03.000Z

Cross-posting potential workaround from serilog/serilog-aspnetcore#84 (comment):

After checking library sources and experimenting for many hours today, here is a workaround I have arrived at which seems to work. Let me know if I'm shooting myself in the foot.

In doing this I have sacrificed logging early startup errors (in main or Startup.ConfigureServices up to and including where I configure the logger), but I am successfully logging "late" startup errors (e.g. in the Startup.Configure method) to Application Insights, and everything else seems to work as normal after (very) cursory testing.

Program.fs

[<EntryPoint>]
let main args =
  WebHost
    .CreateDefaultBuilder(args)
    .CaptureStartupErrors(true)
    .UseSerilog(dispose = true)
    .UseStartup<Startup>()
    .Build()
    .Run()
  0

Startup.fs

type Startup() =

  member __.ConfigureServices(services: IServiceCollection) : unit =
    services.AddApplicationInsightsTelemetry() |> ignore
    let sp = services.BuildServiceProvider()
    let telemetryConfig = sp.GetRequiredService<TelemetryConfiguration>()

    Log.Logger <-
      LoggerConfiguration()
        .WriteTo.ApplicationInsights(telemetryConfig, TelemetryConverter.Traces)
        .CreateLogger()

    services.AddSingleton<ILogger>(Log.Logger) |> ignore

Answer 3 · 2019-10-08T18:33:23.000Z

@cmatskas it works for me 👍

Answer 4 · 2019-10-15T02:06:06.000Z

I changed it like this and it seems to be working for me:

var log = new LoggerConfiguration()
    .WriteTo
	.ApplicationInsights(TelemetryConfiguration.CreateDefault(), TelemetryConverter.Events)
    .CreateLogger();

Answer 5 · 2019-10-15T06:01:33.000Z

@crgolden AFAIK that will only work if you don't otherwise configure the telemetry configuration through DI (in ConfigureServices). Once you start adding telemetry processors and initializers, or changing other telemetry settings, those changes will not apply to the configuration you create directly in WriteTo.ApplicationInsights (or configurations you create directly any other places for that matter).

Answer 6 · 2019-10-15T09:40:19.000Z

In my AspNetCore 3.0 web app, I got this working with the recommended way of setting up logging in Program.cs with the following code:

private static IHostBuilder CreateHostBuilder(string[] args) =>
	Host.CreateDefaultBuilder(args)
		.ConfigureWebHostDefaults(webBuilder =>
		{
			webBuilder
				.ConfigureLogging((hostingContext, logging) => logging.ClearProviders())
				.UseSerilog((hostingContext, loggerConfiguration) =>
				{
					var telemetryConfiguration = TelemetryConfiguration.CreateDefault();
					telemetryConfiguration.InstrumentationKey = hostingContext.Configuration["ApplicationInsights:InstrumentationKey"];

					loggerConfiguration
						.MinimumLevel.Information()
						.MinimumLevel.Override("Microsoft", LogEventLevel.Warning)
						.MinimumLevel.Override("System", LogEventLevel.Warning)
#if DEBUG
						.MinimumLevel.Verbose()
						.WriteTo.Console()
						.WriteTo.Debug()
#endif
						.Enrich.FromLogContext()
						.Enrich.WithMachineName()
						.WriteTo.ApplicationInsights(telemetryConfiguration, TelemetryConverter.Traces);
				})
				.UseStartup<Startup>();
		});

In addition to the code above, I also have the normal services.AddApplicationInsightsTelemetry() in Startup/ConfigureServices and the "default" appsetting:

  "ApplicationInsights": {
    "InstrumentationKey": "mykey"
  },

However, I don't have a ApplicationInsights.config at all. I suspect that file won't be read with this code.

Answer 7 · 2019-10-15T11:42:01.000Z

@MathiasRonnblom-Cint I think my comment above applies to your solution, as well. Since you instantiate a new TelemetryConfiguration and pass it to WriteTo.ApplicationInsights, you won't get telemetry initializers/processors (configured in ConfigureServices) added to the one passed to WriteTo.ApplicationInsights.

Answer 8 · 2019-10-15T21:00:34.000Z

@cmeeren

Startup.fs

type Startup() =

  member __.ConfigureServices(services: IServiceCollection) : unit =
    services.AddApplicationInsightsTelemetry() |> ignore
    let sp = services.BuildServiceProvider()
    let telemetryConfig = sp.GetRequiredService<TelemetryConfiguration>()

    Log.Logger <-
      LoggerConfiguration()
        .WriteTo.ApplicationInsights(telemetryConfig, TelemetryConverter.Traces)
        .CreateLogger()

    services.AddSingleton<ILogger>(Log.Logger) |> ignore

I'd be a little wary of using BuildServiceProvider(). When the Startup class is constructed by the framework, there will already be a service provider built. If you built another one, it will not have the same lifetime scope, which could be problematic for singletons (which I think you'll find, is how TelemetryConfiguration is registered).

Instead, as I posted over in issue 84, I'd recommend using the constructor of Startup to request an instance of TelemetryConfiguration. serilog/serilog-aspnetcore#84 (comment)

Also, I agree with your feedback above about people creating new instances of TelemetryConfiguration. It will "work" at a superficial level, but you won't be sharing around the same instance, which would cause unexpected outcomes if you do any further configuration on the instance.

Answer 9 · 2019-10-16T19:57:39.000Z

I got this working in AspNet Core 3.0 and I believe it avoids the pitfalls of the previous solutions. I had to replace UseSerilog with my own registration to access the built IServiceProvider.

return Host.CreateDefaultBuilder(args)
                .ConfigureAppConfiguration((context, config) =>
                {
                    // Add Key Vault or whatever
                })
                .ConfigureLogging((context, logging) =>
                {
                    logging.ClearProviders();
                })
                .ConfigureServices((HostBuilderContext context, IServiceCollection services) =>
                {
                    // Explicitly use the configuration previously built above
                    services.AddApplicationInsightsTelemetry(context.Configuration);
                    // Add enrichers and processors
                    services.AddApplicationInsightsKubernetesEnricher();
                    services.AddApplicationInsightsTelemetryProcessor<HealthCheckTelemetryFilter>();
                    
                    services.AddSingleton<ILoggerFactory>(provider =>
                    {
                        TelemetryConfiguration telemetryConfiguration = provider.GetRequiredService<TelemetryConfiguration>();
                        var loggerConfiguration = new LoggerConfiguration();

                        loggerConfiguration.ReadFrom.Configuration(context.Configuration)
                           .Enrich.WithExceptionDetails()
                           .Enrich.FromLogContext()
                           .WriteTo.Console()
                           .WriteTo.ApplicationInsights(telemetryConfiguration, TelemetryConverter.Traces);

                        Serilog.Core.Logger logger = loggerConfiguration.CreateLogger();
                       
                        Log.Logger = logger;

                        var factory = new SerilogLoggerFactory(logger, true);

                        return factory;
                    });
                })
                .ConfigureWebHostDefaults(webBuilder =>
                {
                    webBuilder.UseStartup<T>();
                });

Answer 10 · 2019-10-17T08:00:15.000Z

By removing UseSerilog you miss out on additional work done by that method (directly or through internal helper functions). In your case, that seems to be limited to registering the IDiagnosticsContext:

https://github.com/serilog/serilog-aspnetcore/blob/71165692d5f66c811c3b251047b12c259ac2fe23/src/Serilog.AspNetCore/SerilogWebHostBuilderExtensions.cs#L149-L156

If additional arguments were supplied to the initial UseSerilog call, even more functionality must be duplicated, starting to destroy the purpose of having a library in the first place.

Answer 11 · 2019-10-17T08:10:38.000Z

Yeah, I do register those manually for my own app but left them out of the example code above.

Answer 12 · 2019-11-12T20:25:28.000Z

So far the conversation has focused on asp.net core applications but this also needs to be solved for non-http context applications and console applications. for console applications I think something like this should work but have yet to figure out why it is not. Any feed back on how to make this work or improve this is appreciated

using Microsoft.ApplicationInsights.Extensibility;
using Microsoft.ApplicationInsights.WorkerService;
using Microsoft.Extensions.Configuration;
using Microsoft.Extensions.DependencyInjection;
using Microsoft.ApplicationInsights;
using Microsoft.ApplicationInsights.DataContracts;
using Microsoft.Extensions.DependencyInjection;
using PowerArgs;
using Serilog;
using System;
using System.Net.Http;
using System.Threading;
using System.Threading.Tasks;
using Microsoft.ApplicationInsights.Extensibility;
using Microsoft.ApplicationInsights.WorkerService;
using Microsoft.Extensions.Configuration;
using Microsoft.Extensions.Logging;
using Serilog.Events;
using Serilog.Exceptions;
using Serilog.Extensions.Logging;
using System.Collections.Generic;
using System.Text;

namespace YourApplication
{

    class Program
    {

        static int Main(string[] args)
        {
            using (var source = new CancellationTokenSource())
            {
                Console.CancelKeyPress += (sender, e) =>
                {
                    source.Cancel();
                };


                return MainAsync( source.Token)
                    .GetAwaiter()
                    .GetResult();
            }
        }

        private static async Task<int> MainAsync(CancellationToken cancellationToken)
        {
            ServiceProvider serviceProvider = null;
            TelemetryClient telemetryClient = null;
            try
            {
                serviceProvider = Bootstrapper.ConfigureServices()
                        .BuildServiceProvider();

                telemetryClient = serviceProvider.GetRequiredService<TelemetryClient>();


                var httpClient = new HttpClient();
                var logger = serviceProvider.GetService<ILogger>();
                var i = 0;
                while (i < 10) // This app runs indefinitely. replace with actual application termination logic.
                {
                    logger.Information("Worker running at: {time}", DateTimeOffset.Now);

                    // Replace with a name which makes sense for this operation.
                    using (telemetryClient.StartOperation<RequestTelemetry>("operation"))
                    {
                        logger.Warning("A sample warning message. By default, logs with severity Warning or higher is captured by Application Insights");
                        logger.Information("Calling bing.com");
                        var res = await httpClient.GetAsync("https://bing.com");
                        logger.Information("Calling bing completed with status:" + res.StatusCode);
                        logger.Fatal("Fatal action");
                        telemetryClient.TrackEvent("Bing call event completed");
                    }

                    await Task.Delay(1000);
                    i++;
                }
                return 0;
            }
            catch (Exception e)
            {
                ILogger logger = null;
                try
                {
                    if (serviceProvider != null)
                    {
                        logger = serviceProvider.GetService<ILogger>();
                    }
                }
                catch { }

                if (logger != null)
                {
                    logger.Error(e, "An error has occurred");
                }
                else
                {
                    Console.Error.WriteLine("An error has occurred" + e.ToString());
                }
                return -500;
            }
            finally
            {
                Log.CloseAndFlush();


                // This is to ensure that even if application terminates, telemetry is sent to the back-end.
                if (telemetryClient != null)
                {
                    telemetryClient.Flush();
                    await Task.Delay(5000);
                }

                if (serviceProvider != null)
                {
                    serviceProvider.Dispose();
                }
            }
        }
    }


    public static class Bootstrapper
    {
        private const string InstrumentationKeyFromConfig = "ApplicationInsights:InstrumentationKey";

        public static ServiceCollection ConfigureServices()
        {
            var config = BuildConfiguration();
            var services = new ServiceCollection();
            services.AddSingleton(provider => config);
            // https://docs.microsoft.com/en-us/azure/azure-monitor/app/worker-service
            services.AddApplicationInsightsTelemetryWorkerService(config[InstrumentationKeyFromConfig]);
            services.ConfigureLogging();
            return services;
        }

        private static IConfiguration BuildConfiguration() => new ConfigurationBuilder()
                .AddJsonFile("config/ai.json", false, true)
                .Build();

        private static void ConfigureLogging(this IServiceCollection services)
        {
            services.AddSingleton<Serilog.ILogger>(provider =>
            {
                var configuration = provider.GetRequiredService<IConfiguration>();
                var telemetryConfiguration = provider.GetRequiredService<TelemetryConfiguration>();

                var logger = new LoggerConfiguration()
                    .ReadFrom.Configuration(configuration)
                    .MinimumLevel.Override("Microsoft", LogEventLevel.Warning)
                    .MinimumLevel.Override("System", LogEventLevel.Warning)

                    .Enrich.FromLogContext()
                    .Enrich.WithMachineName()
                    .Enrich.WithExceptionDetails()
                    .WriteTo.Console()
                    .WriteTo.ApplicationInsights(telemetryConfiguration, TelemetryConverter.Traces)
                    .CreateLogger();

                Log.Logger = logger;
                return Log.Logger;
            });

            services.AddSingleton<ILoggerFactory>(provider =>
            {
                var logger = provider.GetRequiredService<Serilog.ILogger>();
                return new SerilogLoggerFactory(logger, true);
            });
        }
    }
}

Answer 13 · 2019-11-14T17:06:51.000Z

I have the the same problem i can't figure out, how set this up properly (for asp net core and console).

Answer 14 · 2019-11-27T15:47:28.000Z

Also wondering what the recommendation is here, doesn't seem like there are any good solutions to this issue yet.

Answer 15 · 2019-12-02T15:03:48.000Z

I'm wondering if there's some potential issues with configuring the Logger inside the "Configure" block or a hosted service.
I'm thinking that there's a possibility that:

Instances might be created before the static Logger is updated
And if they have an ILogger injected, I assume they're going to end up with the wrong one.

Answer 16 · 2020-01-16T07:34:52.000Z

Any updates on this? What's the recommendation to use this in Console apps?

Answer 17 · 2020-01-16T14:17:13.000Z

TelemetryConfiguration.CreateDefault() has been working for me:

builder.Services.AddLogging(builder => builder .AddSerilog( new LoggerConfiguration() .MinimumLevel.Debug() .WriteTo.Console() .WriteTo.ApplicationInsights(TelemetryConfiguration.CreateDefault(), TelemetryConverter.Traces) .CreateLogger(), true) );

Any updates on this? What's the recommendation to use this in Console apps?

Answer 18 · 2020-02-04T00:13:18.000Z

Just created PR #128 in order to update the README so new users can go straight into TelemetryConfiguration.CreateDefault() instead of the deprecated one.

Answer 19 · 2020-02-05T09:44:41.000Z

Is there any real solution to this problem? Creating new telemetry configuration is no-go for me, because then traces are not corellated as well as when they used to with TelemetryConfiguration.Active.

Answer 20 · 2020-02-09T14:42:17.000Z

Is there any real solution to this problem? Creating new telemetry configuration is no-go for me, because then traces are not corellated as well as when they used to with TelemetryConfiguration.Active.

I also need a way to get the default processors, like adaptive sampling etc, when retrieving the TelemetryConfiguration. For now I need to use TelemetryConfiguration.Active until either a default TelemetryConfiguration is added to the IoC, or Microsoft describe more clearly how I should construct a good confiugration.

Answer 21 · 2020-02-23T14:34:13.000Z

Has a recommended way of doing this come out on top? I'm having a hard time weighing all these suggestions up against each other.

Answer 22 · 2020-02-26T23:51:25.000Z

Likewise.

I'm currently doing this:

.UseSerilog((hostingContext, loggerConfiguration) => {
    // Logging setup needs to be part of Azure Service Fabric setup atm.
    // If you work with hostingContext outside the ASF config class library, it will fail due hostingContext not being available. (even though you are literally passing it as a parameter)
    loggerConfiguration
        .ReadFrom.Configuration(hostingContext.Configuration)
        .Enrich.FromLogContext()
        .Enrich.WithProperty("ApplicationName", typeof(T).Assembly.GetName().Name)
        .Enrich.WithProperty("Environment", hostingContext.HostingEnvironment)
        // TODO: Wait for a solution to have full AppInsights support:
        // https://github.com/serilog/serilog-sinks-applicationinsights/issues/121
        .WriteTo.Async(x => x.ApplicationInsights(TelemetryConfiguration.CreateDefault(), TelemetryConverter.Traces));

#if DEBUG
    // Used to filter out potentially bad data due debugging.
    // Very useful when doing Seq dashboards and want to remove logs under debugging session.
    loggerConfiguration.Enrich.WithProperty("DebuggerAttached", System.Diagnostics.Debugger.IsAttached);
#endif

It works on most apps but when running it on Azure Service Fabric, it doesn't work.
I suspect that ASF creates its own instance of ApplicationInsights before the application is bootstrapped since it can kill and restart the ASP .NET core web app without killing the app. (the entry point is ASF rather than ASP .NET)

UPDATE: Using TelemetryConfiguration.Active seems to be the solution for now when using Azure Service Fabric.

Answer 23 · 2020-03-06T08:35:00.000Z

Hi, any update on this issue? I've faced the same problem here.

Answer 24 · 2020-03-27T21:33:43.000Z

Cross-posting potential workaround from serilog/serilog-aspnetcore#84 (comment):

After checking library sources and experimenting for many hours today, here is a workaround I have arrived at which seems to work. Let me know if I'm shooting myself in the foot.

To me the best workaround after wasting huge amounts of time on this seems to be from @cmeeren. Just had to convert it to C#. Ignored it originally to look at the C# solutions.

So my Startup.cs has the following. Hope this gets someone faster to this workaround, while possibly waiting for long term solution. Put the logging setup on top to hopefully reduce the amount of Singletons getting double instantiation, as there is this build warning: "Calling 'BuildServiceProvider' from application code results in an additional copy of singleton services being created. Consider alternatives such as dependency injecting services as parameters to 'Configure'"

        // This method gets called by the runtime. Use this method to add services to the container.
        public void ConfigureServices(IServiceCollection services)
        {
            services.AddApplicationInsightsTelemetry();
            // TODO: Use workaround from following GitHub issue on Serilog Sink. Keep the
            //       workaround code at top to avoid duplicating too many singletons.
            //       https://github.com/serilog/serilog-sinks-applicationinsights/issues/121
            var sp = services.BuildServiceProvider();
            var telemetryConfig = sp.GetRequiredService<TelemetryConfiguration>();
            SetupSerilog(telemetryConfig);

            services.AddControllers();

            /* Do IoC container registrations here */

            services.AddSingleton<Serilog.ILogger>(Log.Logger);
        }

        /// <summary>
        /// Setup Serilog logging.
        /// </summary>
        /// <param name="telemetryConfig">
        /// Telemetry configuration to be passed to applicatio insights sink.
        /// </param>
        private void SetupSerilog(TelemetryConfiguration telemetryConfig)
        {
            Log.Logger = new LoggerConfiguration()
                .Enrich.FromLogContext()
                .MinimumLevel.Debug()
                .MinimumLevel.Override("Microsoft", LogEventLevel.Warning)
                .WriteTo
                    .ApplicationInsights(telemetryConfig, TelemetryConverter.Traces)
                .WriteTo.Console()
                .CreateLogger();

            Log.Information("Starting up");
        }

Answer 25 · 2020-03-28T22:10:27.000Z

I was able to get it up and running by creating my own scope in the main method to pull from the service provider.

var host = CreateHostBuilder(args).Build();
TelemetryConfiguration configuration;
using (var scope = host.Services.CreateScope())
{
    configuration = scope.ServiceProvider.GetRequiredService<TelemetryConfiguration>();
}

Log.Logger = new LoggerConfiguration()
    .MinimumLevel.Debug()
    .MinimumLevel.Override("Microsoft", LogEventLevel.Warning)
    .MinimumLevel.Override("System", LogEventLevel.Warning)
    .MinimumLevel.Override("Microsoft.AspNetCore.Authentication", LogEventLevel.Information)
    .Enrich.FromLogContext()
    .WriteTo.ApplicationInsights(configuration, TelemetryConverter.Traces)
    .CreateLogger();

Answer 26 · 2020-03-29T06:01:03.000Z

Cross-posting potential workaround from serilog/serilog-aspnetcore#84 (comment):
After checking library sources and experimenting for many hours today, here is a workaround I have arrived at which seems to work. Let me know if I'm shooting myself in the foot.

To me the best workaround after wasting huge amounts of time on this seems to be from @cmeeren. Just had to convert it to C#. Ignored it originally to look at the C# solutions.

So my Startup.cs has the following. Hope this gets someone faster to this workaround, while possibly waiting for long term solution. Put the logging setup on top to hopefully reduce the amount of Singletons getting double instantiation, as there is this build warning: "Calling 'BuildServiceProvider' from application code results in an additional copy of singleton services being created. Consider alternatives such as dependency injecting services as parameters to 'Configure'"
        // This method gets called by the runtime. Use this method to add services to the container.
        public void ConfigureServices(IServiceCollection services)
        {
            services.AddApplicationInsightsTelemetry();
            // TODO: Use workaround from following GitHub issue on Serilog Sink. Keep the
            //       workaround code at top to avoid duplicating too many singletons.
            //       https://github.com/serilog/serilog-sinks-applicationinsights/issues/121
            var sp = services.BuildServiceProvider();
            var telemetryConfig = sp.GetRequiredService<TelemetryConfiguration>();
            SetupSerilog(telemetryConfig);

            services.AddControllers();

            /* Do IoC container registrations here */

            services.AddSingleton<Serilog.ILogger>(Log.Logger);
        }

        /// <summary>
        /// Setup Serilog logging.
        /// </summary>
        /// <param name="telemetryConfig">
        /// Telemetry configuration to be passed to applicatio insights sink.
        /// </param>
        private void SetupSerilog(TelemetryConfiguration telemetryConfig)
        {
            Log.Logger = new LoggerConfiguration()
                .Enrich.FromLogContext()
                .MinimumLevel.Debug()
                .MinimumLevel.Override("Microsoft", LogEventLevel.Warning)
                .WriteTo
                    .ApplicationInsights(telemetryConfig, TelemetryConverter.Traces)
                .WriteTo.Console()
                .CreateLogger();

            Log.Information("Starting up");
        }

Why not just use var client = app.ApplicationServices.GetService<TelemetryClient>(); (or TelemetryConfiguration) in Configure(IApplicationBuilder app, IWebHostEnvironment env) and pass that to Serilog? It looks like you are using ASP.NET Core.

Answer 27 · 2020-03-29T09:07:40.000Z

I was able to get it up and running by creating my own scope in the main method to pull from the service provider.

var host = CreateHostBuilder(args).Build();
TelemetryConfiguration configuration;
using (var scope = host.Services.CreateScope())
{
    configuration = scope.ServiceProvider.GetRequiredService<TelemetryConfiguration>();
}

Log.Logger = new LoggerConfiguration()
    .MinimumLevel.Debug()
    .MinimumLevel.Override("Microsoft", LogEventLevel.Warning)
    .MinimumLevel.Override("System", LogEventLevel.Warning)
    .MinimumLevel.Override("Microsoft.AspNetCore.Authentication", LogEventLevel.Information)
    .Enrich.FromLogContext()
    .WriteTo.ApplicationInsights(configuration, TelemetryConverter.Traces)
    .CreateLogger();

Why not just use the host.GetService(typeof(TelemetryConfiguration)) (if you are on ASP.NET Core)? Or is it better to do a scope? I am not that into when to use a scope.

Answer 28 · 2020-03-29T20:55:51.000Z

I was able to get it up and running by creating my own scope in the main method to pull from the service provider.

var host = CreateHostBuilder(args).Build();
TelemetryConfiguration configuration;
using (var scope = host.Services.CreateScope())
{
    configuration = scope.ServiceProvider.GetRequiredService<TelemetryConfiguration>();
}

Log.Logger = new LoggerConfiguration()
    .MinimumLevel.Debug()
    .MinimumLevel.Override("Microsoft", LogEventLevel.Warning)
    .MinimumLevel.Override("System", LogEventLevel.Warning)
    .MinimumLevel.Override("Microsoft.AspNetCore.Authentication", LogEventLevel.Information)
    .Enrich.FromLogContext()
    .WriteTo.ApplicationInsights(configuration, TelemetryConverter.Traces)
    .CreateLogger();

Worked for me after adding

Following code in ConfigureServices=> StartUp.cs

 public class StartUp{
  ConfigureServices(IServiceCollection services){
  services.AddApplicationInsightsTelemetry(); 

  .....
 }
}

ApplicationInsights:InstrumentationKey in appsettings.json (ref: https://docs.microsoft.com/en-us/azure/azure-monitor/app/asp-net-core#enable-application-insights-server-side-telemetry-no-visual-studio)

"ApplicationInsights": {
        "InstrumentationKey": "AppInsightsInstrumentationKeyHere"
    }

Answer 29 · 2020-03-30T09:05:12.000Z

Creating new scope is not ideal since you end-up with two separate instances of DI containers.

Answer 30 · 2020-03-30T17:32:40.000Z

Creating new scope is not ideal since you end-up with two separate instances of DI containers.

Then why not just

        public static void Main(string[] args)
        {
            var host = CreateHostBuilder(args).Build();

            var client = (TelemetryClient) host.Services.GetService(typeof(TelemetryClient));

            Log.Logger = new LoggerConfiguration()
            .MinimumLevel.Debug()
            .MinimumLevel.Override("Microsoft", LogEventLevel.Information)
            .Enrich.FromLogContext()
            .WriteTo.Console()
            .WriteTo
            .ApplicationInsights(client, TelemetryConverter.Traces)
            .CreateLogger();

            host.Run();
        }

        public static IHostBuilder CreateHostBuilder(string[] args) =>
            Host.CreateDefaultBuilder(args)
                .ConfigureWebHostDefaults(webBuilder =>
                {
                    webBuilder.UseStartup<Startup>();
                })
            .UseSerilog();

? Isn't this perfectly vaild, or am I missing something?

Answer 31 · 2020-03-31T07:17:39.000Z

@mslot looks good!

Answer 32 · 2020-04-02T20:28:23.000Z

@mslot Works great. Was not really happy with the earlier solution being quite hacky, so did not go forward with it, but this I can live with. Just moved from .Net Framework, so that deep into the startup piping yet in DotNet Core.

Answer 33 · 2020-04-02T21:01:37.000Z

@mslot Some problems with this and some other solutions though, since the logger is created so late logging startup exceptions does not work through serilog. Need to log those some other way.

Additionally registering Serilog interface as single instance like this does not work anymore (pardon my turning to Autofac IoC in the mean time):

builder.RegisterInstance<Serilog.ILogger>(Serilog.Log.Logger).SingleInstance();

Had to use instance per lifetime scope, which is not a problem of course:

builder.Register<Serilog.ILogger>(x => Serilog.Log.Logger).InstancePerLifetimeScope();

Answer 34 · 2020-04-02T21:20:51.000Z

@mslot Some problems with this and some other solutions though, since the logger is created so late logging startup exceptions does not work through serilog. Need to log those some other way.

Additionally registering Serilog interface as single instance like this does not work anymore (pardon my turning to Autofac IoC in the mean time):
builder.RegisterInstance<Serilog.ILogger>(Serilog.Log.Logger).SingleInstance();
Had to use instance per lifetime scope, which is not a problem of course:
builder.Register<Serilog.ILogger>(x => Serilog.Log.Logger).InstancePerLifetimeScope();

Well i dont know about Serilog.ILogger I just use The regular ILogger. The earliest i can get to work without it being hacky is:

        public void Configure(IApplicationBuilder app, IWebHostEnvironment env)
        {
            if (env.IsDevelopment())
            {
                app.UseDeveloperExceptionPage();
            }

            var client = app.ApplicationServices.GetService<TelemetryClient>();

            Log.Logger = new LoggerConfiguration()
            .MinimumLevel.Debug()
            .MinimumLevel.Override("Microsoft", LogEventLevel.Information)
            .Enrich.FromLogContext()
            .WriteTo.Console()
            .WriteTo
            .ApplicationInsights(client, TelemetryConverter.Traces)
            .CreateLogger();

 //omitted code
        }

But i dont know if that helps with startup exceptions inConfigureServices.
What about your services.BuildServiceProvider(); method? Does that catch the startup exceptions? I can't get it to work.

Could I get you to elaborate on what you mean with that it doesnt catch startup exceptions? Could you provide an example of this? Just so I could experiment a bit with it.

Answer 35 · 2020-04-02T21:23:29.000Z

Thanks all for ideas. I've been using the overload with just the ITelemetryConverter, and it seems to work fine, including using custom filtering added in ConfigureServices with services.AddApplicationInsightsTelemetryProcessor<TCustomFilter>()

Am I missing anything dumb? My Program.Main:

Log.Logger = new LoggerConfiguration()
    .Enrich.FromLogContext()
    .WriteTo.Console()
    .WriteTo.Debug()
    .WriteTo.ApplicationInsights(TelemetryConverter.Traces)
    .CreateLogger();
...

Answer 36 · 2020-04-02T21:44:03.000Z

Thanks all for ideas. I've been using the overload with just the ITelemetryConverter, and it seems to work fine, including using custom filtering added in ConfigureServices with services.AddApplicationInsightsTelemetryProcessor<TCustomFilter>()

Am I missing anything dumb? My Program.Main:
Log.Logger = new LoggerConfiguration()
    .Enrich.FromLogContext()
    .WriteTo.Console()
    .WriteTo.Debug()
    .WriteTo.ApplicationInsights(TelemetryConverter.Traces)
    .CreateLogger();
...

Just remember to get the proper TelemetryClient or TelemetryConfiguration from the IoC so you get all the predefined processors and initializers.

Answer 37 · 2020-04-02T22:05:12.000Z

In doing a bit more digging, it appears that the Serilog integration just uses TelemetryConfiguration.Active internally if you don't provide one, as of now:
https://github.com/serilog/serilog-sinks-applicationinsights/blob/a5a6b2cbed74249c2cb5c27723ede86c26c4cca5/src/Serilog.Sinks.ApplicationInsights/LoggerConfigurationApplicationInsightsExtensions.cs#L65

I wanted to compare results of resolving a TelemetryConfiguration from the services container vs using .Active. At least in inspecting the values and comparing serialized versions, using .Active is the same as resolving, at least in my aspnet core 3.1 web app:

var resolved = (TelemetryConfiguration)host.Services.GetService(typeof(TelemetryConfiguration));
var active = TelemetryConfiguration.Active;

string resolvedJson = JsonConvert.SerializeObject(resolved);
string activeJson = JsonConvert.SerializeObject(active);

bool same = resolvedJson == activeJson; // true

Based on this, it would seem not necessarily breaking anything currently to just use the overload without a client, and wait until the Serilog integration either changes to require an injected configuration/client, or the AI SDK team provides more guidance. Of course, I could be wrong. :)

By the way, here is the original deprecation announcement with more info.

Answer 38 · 2020-04-03T06:30:15.000Z

In doing a bit more digging, it appears that the Serilog integration just uses TelemetryConfiguration.Active internally if you don't provide one, as of now:
https://github.com/serilog/serilog-sinks-applicationinsights/blob/a5a6b2cbed74249c2cb5c27723ede86c26c4cca5/src/Serilog.Sinks.ApplicationInsights/LoggerConfigurationApplicationInsightsExtensions.cs#L65

I wanted to compare results of resolving a TelemetryConfiguration from the services container vs using .Active. At least in inspecting the values and comparing serialized versions, using .Active is the same as resolving, at least in my aspnet core 3.1 web app:
var resolved = (TelemetryConfiguration)host.Services.GetService(typeof(TelemetryConfiguration));
var active = TelemetryConfiguration.Active;

string resolvedJson = JsonConvert.SerializeObject(resolved);
string activeJson = JsonConvert.SerializeObject(active);

bool same = resolvedJson == activeJson; // true
Based on this, it would seem not necessarily breaking anything currently to just use the overload without a client, and wait until the Serilog integration either changes to require an injected configuration/client, or the AI SDK team provides more guidance. Of course, I could be wrong. :)

By the way, here is the original deprecation announcement with more info.

That is correct, is uses Active.

Could you still elaborate to me what you mean with with that it doesnt catch startup exceptions? I am not sure i know exactly what you refer to.

Answer 39 · 2020-04-07T18:30:15.000Z

This should provide what is needed to implement correctly serilog/serilog-aspnetcore#177. This library will still need to be updated, but this would be the first step imo

Answer 40 · 2020-05-18T00:36:16.000Z

Thanks for making the note, here, @jstafford5380 👍 - yes, this should be resolved in the current -dev version of the Serilog/Hosting/ASP.NET Core integration, with a UseSerilog() overload that provides access to the IServiceProvider on which GetRequiredService<TelemetryConfiguration>() can be called.

    .UseSerilog((hc, services, lc) =>  lc
        .WriteTo.ApplicationInsights(
            services.GetRequiredService<TelemetryConfiguration>(),
            TelemetryConverter.Traces))

All, if we can have some confirmation that this resolves the issue, I'll get things moving on an RTM version of the updated packages. 🎉

Answer 41 · 2020-05-18T05:42:52.000Z

Thanks for making the note, here, @jstafford5380 - yes, this should be resolved in the current -dev version of the Serilog/Hosting/ASP.NET Core integration, with a UseSerilog() overload that provides access to the IServiceProvider on which GetRequiredService<TelemetryConfiguration>() can be called.
    .UseSerilog((hc, services, lc) =>  lc
        .WriteTo.ApplicationInsights(
            services.GetRequiredService<TelemetryConfiguration>(),
            TelemetryConverter.Traces))
All, if we can have some confirmation that this resolves the issue, I'll get things moving on an RTM version of the updated packages.

This will resolve the issue. Looks great!! Can't wait for it to be released!!

Answer 42 · 2020-05-19T00:23:30.000Z

@mslot thanks for the feedback! Have you upgraded to the -dev package and successfully used the new overload to configure AI?

There are still subtleties around order-of-initialization, potential dependency cycles, and so-on that might pop up, and since I don't run AI for anything myself, I can't be confident it will actually work, so ideally some confirmation along those lines will speed the release :-) 👍

Answer 43 · 2020-05-19T05:10:49.000Z

@mslot thanks for the feedback! Have you upgraded to the -dev package and successfully used the new overload to configure AI?

There are still subtleties around order-of-initialization, potential dependency cycles, and so-on that might pop up, and since I don't run AI for anything myself, I can't be confident it will actually work, so ideally some confirmation along those lines will speed the release :-) 👍

I haven't tried it yet. I will see if I can set some time of to upgrade.

Answer 44 · 2020-05-20T17:41:43.000Z

Thanks @nblumhardt! I was able to upgrade to the latest Serilog.AspNetCore (3.4.0-dev-00168) and give it a whirl across 3 projects in my aspnetcore 3.1 solution. From what I can tell, the new overload seems to work well. My TelemetryProcessors declared in Startup are respected, other services can be resolved from the service provider including environment. Tested locally and deployed in Azure App Service.

Here's my snippet, with braces around body not present in snippet above. The resolved appInsightsConfig instance can be used to disable telemetry in development, for example, before providing to Serilog.

public static IHostBuilder CreateHostBuilder(string[] args) =>
    Host.CreateDefaultBuilder(args)
        .ConfigureWebHostDefaults(webBuilder =>
        {
            webBuilder.UseStartup<Startup>();
        })
        .UseSerilog((context, services, config) =>
        {
            var appInsightsConfig = (TelemetryConfiguration)services.GetService(typeof(TelemetryConfiguration));
            config.WriteTo.ApplicationInsights(appInsightsConfig, TelemetryConverter.Traces);
        });

Answer 45 · 2020-05-20T21:35:35.000Z

Great, thanks @NoahStahl 👍

Answer 46 · 2020-05-20T22:31:20.000Z

I tested with Serilog.AspNetCore 3.4.0-dev-00168 too and so far so good. It is configured and logging correctly. Thanks.

    public static IHostBuilder CreateHostBuilder(string[] args) =>
        Host.CreateDefaultBuilder(args)
            .ConfigureWebHostDefaults(webBuilder =>
            {
                webBuilder.UseStartup<Startup>();
            })
            .UseSerilog((context, services, configuration) => configuration
                .Enrich.FromLogContext()
                .WriteTo.ApplicationInsights(
                    services.GetRequiredService<TelemetryConfiguration>(), 
                    TelemetryConverter.Traces)
            );

Answer 47 · 2020-05-25T10:56:29.000Z

Thanks for making the note, here, @jstafford5380 👍 - yes, this should be resolved in the current -dev version of the Serilog/Hosting/ASP.NET Core integration, with a UseSerilog() overload that provides access to the IServiceProvider on which GetRequiredService<TelemetryConfiguration>() can be called.
    .UseSerilog((hc, services, lc) =>  lc
        .WriteTo.ApplicationInsights(
            services.GetRequiredService<TelemetryConfiguration>(),
            TelemetryConverter.Traces))
All, if we can have some confirmation that this resolves the issue, I'll get things moving on an RTM version of the updated packages. 🎉

I've tried it with console/background service/windows service and it seems to be working fine. Tested on Serilog.Extensions.Hosting 3.1.0-dev-00037.

public static void Main(string[] args)
{
	using var host = CreateHostBuilder(args).Build();
	host.Run();
}

private static IHostBuilder CreateHostBuilder(string[] args) =>
	Microsoft.Extensions.Hosting.Host.CreateDefaultBuilder(args)
		.UseSerilog(ConfigureLogger)
		.UseWindowsService()
		.ConfigureServices(ConfigureServices);

private static void ConfigureLogger(HostBuilderContext context, IServiceProvider services, LoggerConfiguration loggerConfiguration) =>
	loggerConfiguration
		.ReadFrom.Configuration(context.Configuration)
		.WriteTo.ApplicationInsights(services.GetRequiredService<TelemetryConfiguration>(), TelemetryConverter.Events);

Answer 48 · 2020-07-16T15:02:53.000Z

Am I missing something or has the API changed again? 3.4.0-dev-00173 doesn't offer the service collection in the action

public static IWebHostBuilder UseSerilog(this IWebHostBuilder builder, Action<WebHostBuilderContext, LoggerConfiguration> configureLogger, bool preserveStaticLogger = false, bool writeToProviders = false)

Ah... This all works with ASP.NET Core 3+

Answer 49 · 2020-07-31T15:23:17.000Z

Any chance 3.4.0-dev-00173 could be published to nuget 'pre-release' please? Where I work allows pre-release packages but only from MS nuget not third parties.

Answer 50 · 2020-07-31T19:53:24.000Z

Any chance 3.4.0-dev-00173 could be published to nuget 'pre-release' please?

The service provider overload exists in 3.1.0 and works great. Note that it's on IHostBuilder and not IWebHostBuilder. See the readme for details.

Answer 51 · 2020-07-31T21:30:16.000Z

Should we close this now, or are there doc tasks yet to pick up?

Answer 52 · 2020-08-01T09:04:59.000Z

@DalSoft @nblumhardt Sorry, I got the packages mixed up. My previous comment was about Serilog.AspNetCore 3.4.0. Not sure though what changes are needed/commited in this repo; with the service provider overload in Serilog.AspNetCore 3.4.0 I don't have the problem mentioned in this issue.

Answer 53 · 2020-08-02T13:18:35.000Z

Anyone using Serilog with AzureFunctions? No-one mentions azure functions in this whole thread, and the Serilog documentation for azurefunctions specifically says to use .Active. So... if we're using Azure functions and can't use any of the suggested work-arounds above, are we back to square one?

Answer 54 · 2020-08-18T16:43:47.000Z

I've tried with the various suggestions that have come up in this thread, but I can't get it to work. Created a separate issue: #142

Answer 55 · 2021-01-05T16:31:17.000Z

Do I need to literally read this entire thread in order to work out how to setup ApplicationInsights with Serilog in ASP.NET Core 5 or can the README maybe get updated with a small section describing all the 20 million configuration steps that one has to go through in .NET Core in order to just get logging working?

Answer 56 · 2021-01-05T23:30:45.000Z

Would be awesome if someone can bake this down into some README updates; thanks for the nudge @dustinmoris 👍

I don't use AppInsights and don't work on this sink, personally - happy to help where I can, though! Anyone keen to give this a shot?

Answer 57 · 2021-01-07T19:01:15.000Z

If we mark something as deprecated can we put a link to a solution or at least to this thread?

Answer 58 · 2021-01-07T20:37:09.000Z

It seems like this can work

private static void ConfigureLogger(HostBuilderContext context, IServiceProvider services, LoggerConfiguration loggerConfiguration) =>
loggerConfiguration
	.ReadFrom.Configuration(context.Configuration)
	.WriteTo.ApplicationInsights(services.GetRequiredService<TelemetryConfiguration>(), TelemetryConverter.Events);

But is there a way to configure the sink to use the IoC container provided TelemetryConfiguration while using the appSettings.json configuration? We currently use the appSettings so that configuring the sinks do not require a code change but we can't do that if we need to take this ☝️ programmatic approach.

Answer 59 · 2021-01-08T00:01:07.000Z

@eluchsinger hi!

If we mark something as deprecated can we put a link to a solution or at least to this thread?

"We" would be the App Insights SDK team in this case - the deprecated API isn't one that Serilog controls.

Answer 60 · 2021-01-08T00:09:59.000Z

Do I need to literally read this entire thread in order to work out how to setup ApplicationInsights with Serilog in ASP.NET Core 5 or can the README maybe get updated with a small section describing all the 20 million configuration steps that one has to go through in .NET Core in order to just get logging working?

I was considering writing a blog post about this in the style I have written for Serilog + Seq on ASP.NET Core.
https://jkdev.me/asp-net-core-serilog/

I had a blog post ready over a year ago but it was hacky and I didn't felt like it was a good solution.
The metadata on Seq and AppInsights were inconsistent depending on how they were logged and I couldn't get them consistent with the issues we had a year ago. I think some of the logs no longer went to Serilog/Seq.

I can revisit this, see if I can make it work well and I'll post it here.

Answer 61 · 2021-01-08T06:33:48.000Z

In case it's helpful, here is what I'm doing (simplified):

open System
open Microsoft.ApplicationInsights.Extensibility
open Microsoft.AspNetCore.Hosting
open Microsoft.Extensions.DependencyInjection
open Microsoft.Extensions.Hosting
open Serilog
  
let initLogger (ctx: HostBuilderContext) (services: IServiceProvider) (loggerConfig: LoggerConfiguration) =
  loggerConfig.WriteTo.ApplicationInsights(
    services.GetRequiredService<TelemetryConfiguration>(),
    TelemetryConverter.Traces)
  |> ignore

[<EntryPoint>]
let main args =
  Host
    .CreateDefaultBuilder(args)
    .UseSerilog(initLogger)   // This is the relevant line here
    .ConfigureWebHostDefaults(..)
    .Build()
    .Run()
  0

Answer 62 · 2021-02-26T12:17:31.000Z

Hey everyone.

I am currently using the solution posted by @jbrezina (And others): #121 (comment).

Does anyone know if it is possible to have my app insights logging config in appsettings.json with the right telemtryconfiguration? Right now I have my console config in appsettings.json, but thanks to the issue mentioned above I don't have the app insights in my appsettings. If I could have both that would be great!

Answer 63 · 2021-02-27T23:34:53.000Z

Hey everyone.

I am currently using the solution posted by @jbrezina (And others): #121 (comment).

Does anyone know if it is possible to have my app insights logging config in appsettings.json with the right telemtryconfiguration? Right now I have my console config in appsettings.json, but thanks to the issue mentioned above I don't have the app insights in my appsettings. If I could have both that would be great!

Hi, it's a bit of shame the documentation is kind of unhelpful in this regard.

The following works for me as a workaround. Because the respective extension method in LoggerConfigurationApplicationInsightsExtensions.cs is called.

"Serilog": {
    "MinimumLevel": {
      "Default": "Information",
      "Override": {
        "Microsoft": "Information",
        "Microsoft.Hosting.Lifetime": "Information",
        "Microsoft.EntityFrameworkCore": "Warning"
      }
    },
    "WriteTo": [
      {
        "Name": "ApplicationInsights",
        "Args": {
          "restrictedToMinimumLevel": "Information",
          "telemetryClient": {},
          "telemetryConverter": "Serilog.Sinks.ApplicationInsights.Sinks.ApplicationInsights.TelemetryConverters.TraceTelemetryConverter, Serilog.Sinks.ApplicationInsights"
        }
      }
    ]
  }

If an application instrumentation key is necessary or not available through other means, you will also need to set the env variable APPINSIGHTS_INSTRUMENTATIONKEY for this approach.

Or provide it manually through:

        "telemetryClient": {
          "configuration": {
            "instrumentationKey": "xxx"
          }
        }

Answer 64 · 2021-03-01T05:42:20.000Z

We're still keen to update the README if someone familiar with AppInsights can PR some improvements :-)

Answer 65 · 2021-03-14T07:08:18.000Z

This is pretty hacky (sorry), but just wanted to post a possible solution to getting DI configured telemetry into the App Insights sink. Not sure if we need to actually get the TelemetryClient from DI or the TelemetryConfiguration - should be easy enough to change the code to do either. Basically, the code iterates through the configured sinks and uses reflection to find any instance of the App Insights sink. It then injects the client into the sink. When the configuration is built, the logger has the DI configuration instead of whatever defaults. This is especially useful because if you use the Microsoft.ApplicationInsights.WorkerService package, it doesn't set the Active configuration, which causes the the sink to use a basically unconfigured default value.

This should allow you to fully configure App Insights/Serilog in appSettings.json separately and per recommendations for both products and make them work together while not relying on the TelemetryConfiguration.Active singleton.

        public static LoggerConfiguration WithTelemetryConfiguration(this LoggerConfiguration loggerConfiguration, IServiceProvider services)
        {
            //get the DI configuration
            TelemetryConfiguration telemetryConfiguration = services.GetRequiredService<TelemetryConfiguration>();
            TelemetryClient telemetryClient = new TelemetryClient(telemetryConfiguration);

            Log.Information("Attempting to inject AI telemetryConfiguration");
            Log.Information("AI Instrumentation Key Present: {keyExists}", !String.IsNullOrEmpty(telemetryConfiguration.InstrumentationKey));
            Log.Information("AI Endpoint: {endpoint}", telemetryConfiguration.TelemetryChannel.EndpointAddress);

            var sinksInfo = loggerConfiguration.GetType().GetField("_logEventSinks", BindingFlags.Instance | BindingFlags.NonPublic);
            if(sinksInfo != null)
            {
                var sinks = (List<Serilog.Core.ILogEventSink>)sinksInfo.GetValue(loggerConfiguration);
                foreach(Serilog.Core.ILogEventSink sink in sinks)
                {
                    var possibleSink = sink;

                    var wSinkInfo = sink.GetType().GetField("_sink", BindingFlags.Instance | BindingFlags.NonPublic);
                    if (wSinkInfo != null)
                    {
                        var wSink = wSinkInfo.GetValue(sink) as Serilog.Core.ILogEventSink;
                        if (wSink != null)
                            possibleSink = wSink;
                    }

                    if (possibleSink is Serilog.Sinks.ApplicationInsights.ApplicationInsightsSink)
                    {
                        possibleSink.GetType()
                                .GetField("_telemetryClient", BindingFlags.Instance | BindingFlags.NonPublic)
                                .SetValue(possibleSink, telemetryClient);

                        Log.Information("Injected telemetry client into sink!");
                    }
                }
            }

            return loggerConfiguration;
        }

Just put this into a static class, and then call it at the end of your logger configuration. Make sure to call the appropriate App Insights telemetry method in your services code so that App Insights is properly initialized by time the logger is created. This code isn't extensively tested, and won't handle all wrappers/sink aggregates, but I think it gets many of the main wrappers that I saw in the core source.

Though Serilog itself isn't built with introspection in mind, it may make sense to modify the configuration extensions to allow introspection, it would be pretty powerful for making things all work together. Alternatively, it would be nice for the Serilog App Insights Sink to be able to grab the TelemetryConfiguration/Client from the service provider, not sure of the order of operations that would be needed to make that happen though.

Answer 66 · 2021-03-14T10:38:59.000Z

For ASP.NET Core, I think the problem is solved by the new version of Serilog.AspNetCore: https://nblumhardt.com/2020/10/bootstrap-logger

This allows configuring a bootstrap logger to capture startup errors, and then replace this logger with DI-dependent config later on.

Answer 67 · 2021-03-14T14:21:25.000Z

For ASP.NET Core, I think the problem is solved by the new version of Serilog.AspNetCore: https://nblumhardt.com/2020/10/bootstrap-logger

This allows configuring a bootstrap logger to capture startup errors, and then replace this logger with DI-dependent config later on.

Unfortunately, the new bootstrapper doesn't solve this particular issue. The only reason it works (for now) is because deep in the bowels of the MSFT App Insights package for ASP.NET, they are actually initializing TelemetryConfig.Active. Other versions of the MSFT App Insights packages (for example WorkerService), don't initialize TelemetryConfig.Active. The current sink design either uses TelemetyConfig.Active or you have to pass in the config through code. The former case won't always work, the latter forces you to define the sink in code. Either way, it causes problems.

I'm actually using the bootstrapper in my code, and while it's good for its purpose of capturing logs earlier, it doesn't resolve this issue.

Answer 68 · 2021-03-15T12:09:38.000Z

Getting to the end of this long thread, oh man! Has someone succeeded in using Serilog + AppInsight as sink in WebJob?

I wonder since .ConfigureWebJobs & AddApplicationInsightsWebJobs is not compatible with the ordinary AppInsights addition and for a reason or another I fail to add the configuration so it both works and has the instrumentation key provided. I may be missing something simple, though...

Answer 69 · 2021-03-15T14:32:16.000Z

Getting to the end of this long thread, oh man! Has someone succeeded in using Serilog + AppInsight as sink in WebJob?

I wonder since .ConfigureWebJobs & AddApplicationInsightsWebJobs is not compatible with the ordinary AppInsights addition and for a reason or another I fail to add the configuration so it both works and has the instrumentation key provided. I may be missing something simple, though...

I haven't tried, but it looks like ultimately WebJobs sets up the TelemetryConfiguration.Active singleton (see https://github.com/Azure/azure-webjobs-sdk/blob/6799c9f04c0244c9d0ce51fe2386bd7322a20a5e/src/Microsoft.Azure.WebJobs.Logging.ApplicationInsights/Extensions/ApplicationInsightsServiceCollectionExtensions.cs#L189). So, in theory, if you're using the bootstrapper, it should work since the ApplicationInsightsSink will take the configuration from the active configuration if nothing else is provided, and this should be configured by time you're initializing the logger in the UseSerilog extension. In this case, the bootstrapper may be the solution to your issue. Might want to debug after your ReadFrom.Configuration call and look at whether the Sink has the configuration you expect.

If they ever stop initializing TelemetryConfig.Active, we run into the same problem though.

Answer 70 · 2021-03-15T18:57:21.000Z

@simbaja Do you mean with the UseSerilog? Heh, I feel a bit thick. It also may be this is too fragile to production. In any event, I record here I tried the following in vain, but the solution presented here in this thread earlier for WebAPI works.

The one that follows next logs to a console locally, but in Azure the complaint is AI: TelemetryChannel found a telemetry item without an InstrumentationKey. This is a required field and must be set in either your config file or at application startup.. Puzzling to say the least and I found also microsoft/ApplicationInsights-dotnet#2070 related to this error message.

using Microsoft.ApplicationInsights.Extensibility;
using Microsoft.Extensions.Configuration;
using Microsoft.Extensions.DependencyInjection;
using Microsoft.Extensions.Hosting;
using Microsoft.Extensions.Logging;
using Serilog;
using System;

namespace LoggingText.WebJob
{
   public class Functions
    {
        public async Task SomeTimerTriggerOperation([TimerTrigger("0 */1 * * * *", RunOnStartup = true)] TimerInfo timerInfo, CancellationToken cancellationToken, ILogger log)
        {
            await Task.Delay(TimeSpan.FromMilliseconds(100), cancellationToken).ConfigureAwait(false);
            log.LogWarning("Ohoy!");
        }
    }

    class Program
    {
        private const string AppInsightKey = "InstrumentationKey=<the rest removed>";
        public static IHostBuilder CreateHostBuilder(string[] args)
        {
            return Host.CreateDefaultBuilder(args)
                .ConfigureLogging((hostContext, logBuilder) =>
                {
                    logBuilder.AddApplicationInsightsWebJobs(o => o.InstrumentationKey = AppInsightKey);
                })
                .ConfigureAppConfiguration((context, config) => config.AddJsonFile("appsettings.Development.json"))
                .ConfigureWebJobs(webJobsBuilder =>
                {
                    webJobsBuilder
                        .AddTimers()
                        .AddAzureStorage()
                        .AddAzureStorageCoreServices();
                })
                .ConfigureServices((ctx, services) =>
                {
                    services.AddApplicationInsightsTelemetry(AppInsightKey);
                })
                .UseSerilog((HostBuilderContext context, IServiceProvider services, LoggerConfiguration loggerConfiguration) =>
                    loggerConfiguration
                    .ReadFrom
                    .Configuration(context.Configuration)
                    .WriteTo
                    .ApplicationInsights(
                        services.GetRequiredService<TelemetryConfiguration>(), TelemetryConverter.Traces),
                        preserveStaticLogger: false, writeToProviders: false);
        }

        public static void Main(string[] args)
        {
            var host = CreateHostBuilder(args).Build();
            host.Run();
        }
    }
}

Answer 71 · 2021-03-16T13:41:14.000Z

@veikkoeeva, Looking through the source code, and if I'm reading it correctly, it looks like logBuilder.AddApplicationInsightsWebJobs internally calls the services.AddApplicationInsights: https://github.com/Azure/azure-webjobs-sdk/blob/6930c4ea9ec78db12a05a2d0bf38cce42ab04e13/src/Microsoft.Azure.WebJobs.Logging.ApplicationInsights/Extensions/ApplicationInsightsServiceCollectionExtensions.cs#L32.

However, if you're using Serilog, you probably don't need the logBuilder.AddApplicationInsightsWebJobs call, as that's setting up the MS loggers from what I see (and possibly adding duplicate services). Your call to services.AddApplicationInsightsTelemetry(AppInsightKey) should set it up for Serilog. If it doesn't perhaps change it to services.AddApplicationInsights(o => o.InstrumentationKey = "key") based on the call here: https://github.com/Azure/azure-webjobs-sdk/blob/6930c4ea9ec78db12a05a2d0bf38cce42ab04e13/src/Microsoft.Azure.WebJobs.Logging.ApplicationInsights/Extensions/ApplicationInsightsServiceCollectionExtensions.cs#L30 (which is what is called internally by WebJobs).

Not sure if this helps. It's a bit of a mess at the moment, too many extensions doing different things...

Answer 72 · 2021-03-16T22:15:39.000Z

Hi all,

Thanks for all your input on this thread 😃

As @cmeeren points out the original problems with TelemetryConfiguration.Active appears to be mitigated by recent changes to Serilog.AspNetCore.

It's difficult, because of the length of the thread, to tell what the state of any related peripheral issue is.

I'm closing and locking the thread to avoid losing valuable information in the clutter. Things you can do:

If you have a question on how to set up Serilog with Application Insights, please open a question on Stack Overflow
If you have a working configuration you'd like to share, please send a pull request to this repo with updates to README.md
If you think there's a scenario still not supported, or a bug, please raise an issue in this repo with a full description so that it can be addressed accurately

Thanks again!