-
Notifications
You must be signed in to change notification settings - Fork 782
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Track Cancelled/Aborted Request #5302
Comments
Can you clarify the ask some more? |
Sure. Here is an example of how we could do it with enrich. .AddAspNetCoreInstrumentation(opts =>
{
opts.Enrich = (string _, HttpContext context, ref TagList tags) =>
{
tags.Add("cancelled", context.RequestAborted.IsCancellationRequested);
};
}) |
I see you are asking if the asp.net core instrumentation should do this by default, without having to write the Enrich? Then the answer is generally no, as the instrumentation follows otel conventions, and there isn't anything about "cancellation requested". It is possible to propose something to the Otel Semantic Conventions group, but its usually accepted for very common things. Your best bet would likely be to do such customizations via Enrich itself. |
thanks @cijothomas that makes sense. I looked around in the semantic conventions at this PR and this open issue https://opentelemetry.io/docs/specs/semconv/http/http-spans/#common-attributes According to the docs for error.type we could stipulate timeout or requestAborted in the error.type. Currently a request would display as successful in the traces/metrics but actually be aborted (aka failed)? |
This issue was marked stale due to lack of activity and will be closed in 7 days. Commenting will instruct the bot to automatically remove the label. This bot runs once per day. |
Closed as inactive. Feel free to reopen if this issue is still a concern. |
@cijothomas is this possible now? The linked pull request isn't very clear |
Feature Request
I would like to track the percentage of aborted/cancelled http server requests
Describe the solution you'd like:
https://learn.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.http.httpcontext.requestaborted?view=aspnetcore-8.0
Describe alternatives you've considered.
Custom Enrichment
Additional Context
Add any other context about the feature request here.
The text was updated successfully, but these errors were encountered: