Azure Monitor OpenTelemetry Exporter using deprecated semantic conventions

[dasiths]

• Package Name: azure-monitor-opentelemetry-exporter
• Package Version: latest
• Operating System: n/a/
• Python Version: n/a

Describe the bug
The azure monitor opentelemetry exporter uses deprecated semantic conventions.

• azure-sdk-for-python/sdk/monitor/azure-monitor-opentelemetry-exporter/azure/monitor/opentelemetry/exporter/export/trace/_exporter.py

  Line 351 in 54e0fa6

  elif SpanAttributes.HTTP_METHOD in span.attributes: # HTTP

Example:
Uses the SpanAttributes.HTTP_METHOD which is deprecated as per https://github.com/open-telemetry/opentelemetry-python/blob/d03a62245357eb40cac81d5e671fc2df83aef767/opentelemetry-semantic-conventions/src/opentelemetry/semconv/trace/__init__.py#L49

When using a span with SpanKind.Client you have to rely on the deprecated semantic conventions for Azure Monitor to pick it up.

with tracer.start_as_current_span("OpenAI completion api request", kind=SpanKind.CLIENT) as span:
    span.set_attribute("http.method", "GET") 
    span.set_attribute("http.url", "https://my-deployed-service.openai.azure.com/")
    
   # or span.set_attribute("db.system", "my-deployed-service.openai.azure.com") 

[mccoyp]

Hi @dasiths, thank you for opening an issue! I'll get this routed to the appropriate folks; we'll take a look as soon as possible.

[github-actions]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @jeremydvoss @lzchen.

[lzchen]

This is an issue for upstream OpenTelemetry. We are in the process of adding new semantic conventions to various http instrumentations. See the tracking issue here. Once these are done, the exporters will be changed to allow for those new signals.

[dasiths]

This is an issue for upstream OpenTelemetry. We are in the process of adding new semantic conventions to various http instrumentations. See the tracking issue here. Once these are done, the exporters will be changed to allow for those new signals.

Thanks for the update. Is there a recommended workaround or migration guidance until this is completed? i.e. Do we use db.system or az.namespace attribute until then or keep using the deprecated http attributes?

EDIT: I've just seen this and assume we keep using existing http semantic conventions. https://github.com/open-telemetry/semantic-conventions/tree/main/docs/http#semantic-conventions-for-http

[lzchen]

@dasiths
Yes, please continue to use old semantic attributes until otherwise notified.

[lzchen]

Tracking issue: #35933

[lzchen]

Tracking issue in OT upstream for implementing migration plan for instrumentations: open-telemetry/opentelemetry-python-contrib#2453