可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试):
问题:
I'm trying to log exceptions to Application Insights. I succeeded in doing this by calling TelemetryClient.TrackException
directly. However, I would like to abstract away from this in my code in case I'd want to log to other platforms in the future, so I would like to stick to only the ILogger interface.
I found that you can use ILoggerFactory.AddApplicationInsights
(as implemented here) but no matter what I did, I don't see the logs showing up in ApplicationInsights with this.
Below is my code:
Startup.cs
IConfigurationRoot Configuration { get; set; }
ILoggerFactory LoggerFactory { get; set; }
IServiceProvider ServiceProvider { get; set; }
public Startup( IHostingEnvironment hostingEnvironment, ILoggerFactory loggerFactory )
{
this.LoggerFactory = loggerFactory;
string configurationFilePath = "abc.json";
this.Configuration = new ConfigurationBuilder()
.SetBasePath( hostingEnvironment.ContentRootPath )
.AddJsonFile( configurationFilePath, optional: true, reloadOnChange: true )
.AddEnvironmentVariables()
.Build();
}
public void Configure(
IApplicationBuilder applicationBuilder,
IHostingEnvironment hostingEnvironment,
ILoggerFactory loggerFactory,
IServiceProvider serviceProvider )
{
this.ServiceProvider = serviceProvider;
loggerFactory.AddApplicationInsights( serviceProvider );
applicationBuilder.UseMvc();
}
public void ConfigureServices( IServiceCollection services )
{
services.AddApplicationInsightsTelemetry( this.Configuration );
services.AddMvc( .... // A bunch of options here ... )
}
Then, I try to use this in my controller like this:
ILogger<XController> Logger { get; set; }
public XController( ILogger<XController> logger )
{
this.Logger = logger;
}
[HttpPost]
[Route( "v3.0/abcd" )]
public async Task PostEvent( [FromBody] XEvent xEvent )
{
this.Logger.LogError( 0, new Exception( "1234" ), "1234" );
}
However, I don't see any exceptions associated with the request at all. If I replace the Logger.LogError
line with TelemetryClient.TrackException
(and create the TelemetryClient
first), then I can see the exception without any issues.
I don't know what I'm doing wrong. Could anyone help?
回答1:
According to your description, I suggest you could try below codes to enable ILogger log the error to the ApplicationInsights.
You could directly use loggerFactory.AddApplicationInsights() method to enable the ApplicationInsights ILogger.
More details, you could refer to below codes:
The startup class:
public class Startup
{
public Startup(IHostingEnvironment env)
{
var builder = new ConfigurationBuilder()
.SetBasePath(env.ContentRootPath)
.AddJsonFile("appsettings.json", optional: true, reloadOnChange: true)
.AddJsonFile($"appsettings.{env.EnvironmentName}.json", optional: true)
.AddEnvironmentVariables();
Configuration = builder.Build();
}
public IConfigurationRoot Configuration { get; }
// This method gets called by the runtime. Use this method to add services to the container.
public void ConfigureServices(IServiceCollection services)
{
services.AddApplicationInsightsTelemetry(Configuration);
// Add framework services.
services.AddMvc();
}
// This method gets called by the runtime. Use this method to configure the HTTP request pipeline.
public void Configure(IApplicationBuilder app, IHostingEnvironment env, ILoggerFactory loggerFactory)
{
loggerFactory.AddApplicationInsights(app.ApplicationServices,LogLevel.Warning);
if (env.IsDevelopment())
{
app.UseDeveloperExceptionPage();
app.UseBrowserLink();
}
else
{
app.UseExceptionHandler("/Home/Error");
}
app.UseStaticFiles();
app.UseMvc(routes =>
{
routes.MapRoute(
name: "default",
template: "{controller=Home}/{action=Index}/{id?}");
});
}
}
The appsettings.json:
{
"ApplicationInsights": {
"InstrumentationKey": "yourkey"
}
}
Result:
Update:
The record find in the search feature.
回答2:
There is now first-class support for logging to Application Insights, using the Microsoft.Extensions.Logging.ApplicationInsights provider.
回答3:
I finally figured out. There are two ways to solve my issue:
Easy way:
I was using older versions of the Application Insights NuGets. Specifically,
Microsoft.ApplicationInsights.2.2.0
and Microsoft.ApplicationInsights.AspNetCore.2.0.0
.
Once I upgrade to
Microsoft.ApplicationInsights.2.4.0
and Microsoft.ApplicationInsights.AspNetCore.2.1.1
, everything works as expected. You also see the LogXXX
with an exception as an argument showing up as Exception, and one without an exception showing up as Trace as expected.
Slightly more difficult way:
For some reason, the IApplicationBuilder
and IServiceProvider
in Configure
does not provide the correct service provider to use in AddApplicationInsights
, so you need to add the provider in the ConfigureServices:
public void ConfigureServices( IServiceCollection services )
{
IServiceProvider serviceProvider = services.BuildServiceProvider();
this.LoggerFactory.AddApplicationInsights( serviceProvider, Extensions.Logging.LogLevel.Information );
...
}
This means that you need to save the loggerFactory
from the constructor into a property/field since it's not available via dependency injection in ConfigureServices
.
What I ended up doing (probably the best solution for now in my opinion):
Even though just doing either of the solutions above solves the problem, I decided to do both. This is because I want to be able to log error in ConfigureServices
as well. Were I to put loggerFactory.UseApplicationInsights
in Configure
, then I would not be able to see the error in ConfigureServices
on ApplicationInsights. I also prefer to see both Traces and Exceptions, a feature that only comes with the new package version.
回答4:
Unfortunately the SDK was updated to fire Exception Telemetry only recently (see commit), and the change was not published yet.
The only routes I see right now is to either leave the explicit call to TelemetryClient.TrackException
in your code, or wrap it all with your own implementation of ILogger
- both as temporary solutions until the official SDK support this
回答5:
Here is the documentation of App Insights with ILogger. For me it worked however got tons of Trace log so recommend you to apply custom filters:
builder.AddApplicationInsights("ikey");
builder.AddFilter<Microsoft.Extensions.Logging.ApplicationInsights.ApplicationInsightsLoggerProvider>
("", LogLevel.Information);
builder.AddFilter<Microsoft.Extensions.Logging.ApplicationInsights.ApplicationInsightsLoggerProvider>
("Microsoft", LogLevel.Warning);