Skip to content
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

Azure SDK Tracing Nickel Semester (Jul-Dec21) #3202

Closed
27 of 36 tasks
lmolkova opened this issue Jul 22, 2021 · 1 comment
Closed
27 of 36 tasks

Azure SDK Tracing Nickel Semester (Jul-Dec21) #3202

lmolkova opened this issue Jul 22, 2021 · 1 comment
Assignees
Labels
Epic Monitor - Exporter Monitor OpenTelemetry Exporter Monitor Monitor, Monitor Ingestion, Monitor Query

Comments

@lmolkova
Copy link
Member

lmolkova commented Jul 22, 2021

Azure SDK tracing distributed sample app

Azure SDK support in .NET OTel

HTTP telemetry duplication:

HTTP instrumentation consistency

HTTP span naming:

HTTP spans have /path?query name and OTel spec says it should be HTTP VERB

x-ms-request-id and x-ms-client-request-id attributes consistency

Investiage OTel policy place in HTTP pipeline (should be per try)

Azure SDK span conventions

Misc

Cosmos DB (Java): Azure/azure-sdk-for-java#23032

Populate tracer information with SDK name and version

To track usage of tracing per SDK, we can leverage Azure Monitor pipelines, if we populate tracer info (currently Azure-OpenTelemetry, no version).

@lmolkova lmolkova self-assigned this Jul 22, 2021
@joshfree joshfree changed the title Tracing (Jul-Dec21) Azure SDK Tracing Nickel Semester (Jul-Dec21) Jul 23, 2021
@lmolkova lmolkova transferred this issue from Azure/azure-sdk-for-java Aug 4, 2021
@ghost ghost added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Aug 4, 2021
@lmolkova lmolkova added Epic Monitor Monitor, Monitor Ingestion, Monitor Query Monitor - Exporter Monitor OpenTelemetry Exporter and removed needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. labels Aug 4, 2021
Copy link

Hi @lmolkova, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 15, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Mar 15, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Epic Monitor - Exporter Monitor OpenTelemetry Exporter Monitor Monitor, Monitor Ingestion, Monitor Query
Projects
None yet
Development

No branches or pull requests

1 participant