I started to play around with the Logging/Profiling and when in Logging and clicking the trace request link, I see the trace id GUID but it brings me to the profiling page with no results.
When I go directly to the Profiling page, I do not see any TRACE ID neither the USER ID in any entries.
I am missing a config somewhere?
What’s your environment and configuration? are you seeing any profiling events in the profiling page?
While I am testing on my Dev IIS server, I have removed the IsDevelopment() condition to add the feature. I get the Profiling page with entries but no TRACE ID as seen here
public class ConfigureRequestLogs : IHostingStartup
{
public void Configure(IWebHostBuilder builder) => builder
.ConfigureServices((context, services) => {
services.AddPlugin(new RequestLogsFeature {
RequestLogger = new SqliteRequestLogger(),
EnableRequestBodyTracking = true,
EnableResponseTracking = true,
EnableErrorTracking = true
});
services.AddHostedService<RequestLogsHostedService>();
});
}
public class ConfigureProfiling : IHostingStartup
{
public void Configure(IWebHostBuilder builder) => builder
.ConfigureServices((context, services) => {
services.AddPlugin(new ProfilingFeature
{
IncludeStackTrace = true,
});
// if (context.HostingEnvironment.IsDevelopment())
// {
//
// }
});
}
Using a demo ASP.NET Core Identity Auth template and adding profiling, I get the same thing
There was an issue with the Diagnostics Activity not being initialized with Endpoint Routing Requests which should now be resolved from v8.8.1+ that’s now available in pre-release packages.
The UserId is only going to be populated in Authenticated Endpoints, but if your App enables another way of identifying the user for the Request (e.g. stored in cookies) you can override TryGetUserId(IRequest req) to return the UserId for non-authenticated requests also.