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
CosmosDB creates public API spans, auto-instrumentation (with otel agent or app insights agent) tracks underlying HTTP calls.
Underlying HTTP calls (there is no way to suppress them currently) are siblings (not children) of Cosmos spans and are confusing and misleading. It's also not clear if they are coming from CosmosDb or user app. To, at least, reduce the confusion, we'd like to make them children of Cosmos calls.
Spans are INTERNAL, which breaks OTel expectations and means Azure Monitor can't show cosmos on the application map
Code Snippet
Add the code snippet that causes the issue.
Expected behavior
http spans are children of cosmos spans (in future, we may want them to be suppressed, but OpenTelemtry does not support it at the moment).
Additional context
CosmosDB can't fix it without support in azure-core to create spans and make them current, and allow to specify CLIENT kind. So this needs to be addressed first.
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report
Bug Description Added
Repro Steps Added
Setup information Added
The text was updated successfully, but these errors were encountered:
ghost
added
the
needs-triage
Workflow: This is a new issue that needs to be triaged to the appropriate team.
label
Jul 16, 2021
lmolkova
changed the title
[BUG] CosmosDb spans are not shown as parents of underlying HTTP spans
[BUG] CosmosDb spans are not parents of underlying HTTP spans
Jul 16, 2021
lmolkova
changed the title
[BUG] CosmosDb spans are not parents of underlying HTTP spans
[BUG] CosmosDb spans are INTERNAL and not parents of underlying HTTP spans
Jul 16, 2021
Describe the bug
CosmosDB creates public API spans, auto-instrumentation (with otel agent or app insights agent) tracks underlying HTTP calls.
Underlying HTTP calls (there is no way to suppress them currently) are siblings (not children) of Cosmos spans and are confusing and misleading. It's also not clear if they are coming from CosmosDb or user app. To, at least, reduce the confusion, we'd like to make them children of Cosmos calls.
Spans are INTERNAL, which breaks OTel expectations and means Azure Monitor can't show cosmos on the application map
To Reproduce
Code Snippet
Add the code snippet that causes the issue.
Expected behavior
http spans are children of cosmos spans (in future, we may want them to be suppressed, but OpenTelemtry does not support it at the moment).
Spans are CLIENT.
Screenshots
![image](https://user-images.githubusercontent.com/2347409/126013023-bb13f0e8-97d2-42bc-9e15-ddf91c6aa92b.png)
transaction link
Setup (please complete the following information):
Additional context
CosmosDB can't fix it without support in azure-core to create spans and make them current, and allow to specify CLIENT kind. So this needs to be addressed first.
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report
The text was updated successfully, but these errors were encountered: