You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I have a .net 6 core Web API that I've added OpenTelemetry to. I'm using the automatic instrumentation libraries for incoming HTTP requests and SQL calls. But I can't seem to figure out what is taking the time before my code hits the DB. I added an activity at the entry point of my controller endpoint but something else seems to be occurring further upstream on the .net core side. Are there ways to trace any of the .net core internal code that is executed before my endpoint is hit? I thought this may work, .AddSource("Microsoft.AspNetCore"), but doesn't.
[HttpGet("{id}")]
public async Task<CartEntity> Get(Guid id, int portalId, int userId)
{
using var activity = this.activitySource.StartActivity("Starting Request");
return await _cartService.GetCart(id, portalId, userId);
}
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello, I have a .net 6 core Web API that I've added OpenTelemetry to. I'm using the automatic instrumentation libraries for incoming HTTP requests and SQL calls. But I can't seem to figure out what is taking the time before my code hits the DB. I added an activity at the entry point of my controller endpoint but something else seems to be occurring further upstream on the .net core side. Are there ways to trace any of the .net core internal code that is executed before my endpoint is hit? I thought this may work,
.AddSource("Microsoft.AspNetCore")
, but doesn't.Beta Was this translation helpful? Give feedback.
All reactions