-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[exporter/datadog] Services view operation name do not match with Traces view operation names #11727
Comments
Hi @Nighttraveler! This should not be an issue once we merge #9693, which will happen this week I am hoping. Let's wait and confirm before closing the issue though! |
@Nighttraveler v0.55 is out and it includes #9693, it would be great if you can try it out and give us feedback :) |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Describe the bug
Services view operation name do not match with Traces view operation names. It looks to be sanitized in one place but not in the other.
What did you expect to see?
We expected to see the same operation name in both views, without it the traces list in Service view is useless.
If you click "view in traces" it searches for "operation_name:Web:/foo" and does not show any result, but if you manually change the
:/
to_
it does show results.We relay a lot in operation_name since in our case resource in only GET or POST without much further detail.
Image example
What did you see instead?
An inconsistency in Services tab between
operation
at the top of the page andoperation_name
under Traces tabImage example
What version did you use?
Collector versions:otel/opentelemetry-collector-contrib:0.45.0, otel/opentelemetry-collector-contrib:0.52.0
What config did you use?
Environment
OS: (e.g., "Ubuntu 20.04")
Collector running in docker
The text was updated successfully, but these errors were encountered: