Azure SDK Tracing Nickel Semester (Jul-Dec21) #3202
Labels
Epic
Monitor - Exporter
Monitor OpenTelemetry Exporter
Monitor
Monitor, Monitor Ingestion, Monitor Query
Azure SDK tracing distributed sample app
Azure SDK support in .NET OTel
Add wildcard support to AddLegacySource open-telemetry/opentelemetry-dotnet#2183HTTP telemetry duplication:
HTTP instrumentation consistency
HTTP span naming:
HTTP spans have
/path?query
name and OTel spec says it should be HTTP VERB.NET- won't change until conventions are stable (since shipped in stable version already)x-ms-request-id and x-ms-client-request-id attributes consistency
requestId
,serviceRequestId
)x-ms-request-id
) Http spans minor fixes azure-sdk-for-java#24954x-ms-request-id
,x-ms-client-request-id
)requestId
,serviceRequestId
)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).The text was updated successfully, but these errors were encountered: