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
Package Version - azure-monitor-opentelemetry-exporter = {version = "^1.0.0-beta.3", allow-prereleases = true}
opentelemetry-instrumentation-fastapi = "^0.19b0"
Operating System - macOS Mojave v10.14.6 Python Version - v3.9.0
Steps to reproduce
When using the azure-monitor-opentelemetry-exporter in conjunction with opentelemetry-instrumentation-fastapi
the response code is not populated by the exporter, raised this issue with Azure monitor team and was redirected here;
Looking at the output, it seems like the spans are missing some attributes. This is probably an issue in the opentelemetry-instrumentation-asgi, could you file an issue here for this problem specifically? Basically, the exporter sees if http.status_code is populated in the span attributes to populate response_Code in app insights. Since the attribute is not there, this is why you are seeing 0s. Normally, it is up to the instrumentation to populate this.
Describe your environment
Package Version - azure-monitor-opentelemetry-exporter = {version = "^1.0.0-beta.3", allow-prereleases = true}
opentelemetry-instrumentation-fastapi = "^0.19b0"
Operating System - macOS Mojave v10.14.6
Python Version - v3.9.0
Steps to reproduce
When using the azure-monitor-opentelemetry-exporter in conjunction with opentelemetry-instrumentation-fastapi
the response code is not populated by the exporter, raised this issue with Azure monitor team and was redirected here;
Azure monitor issue#17839
Spans obtained from console exporter:
json.zip
Screen grab from Azure App Insights indication reponse code as 0:
What is the expected behavior?
Compatibility with Azure monitor exporter
Additional context
Detailed context for this issue
Azure monitor issue#17839
Please let me know in case of additional info required.
Thanks.
The text was updated successfully, but these errors were encountered: