-
Notifications
You must be signed in to change notification settings - Fork 275
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
Errors not properly reported to Datadog #3516
Comments
Possibly related to #3226. We may not be creating events at the correct place right now. But we need to investigatge. |
Not exactly matches but we are also facing some OpenTelemetry issues here. Temporally @MatthiasLangGrover resolved it by creating a
|
It looks like there is an issue for events that was introduced in: #2999 In particular this optimization assumes that the otel layer is not interested in events, which is not the case. |
After removing the prefiltering I can see that via OTLP events are transmitted to Datadog: But it's not clear how to link that to the Datadog UI. The Datadog exporter fared even worst with no events sent at all. I think we need to do the following:
|
@Meemaw since #4102 it is possible to set the |
Describe the bug
When using otel datadog exporter, errors are not properly sent to Datadog. In the UI you can see there is an error, but its missing stack trace, description etc.
This is how it looks in router:
This is how it looks with a service that properly reports errors:
Expected behavior
Errors should be sent to Datadog in a way Datadog expects them.
The text was updated successfully, but these errors were encountered: