Strong argument for exporting an OpenTelemetry Asynchronous UpDownCounter to OTLP as a non-monotonic sum rather than as a gauge?
From the OpenTelemetry Docs / Specs / OTel 1.37.0 / Metrics / Supplementary Guidelines:
Autoinstrumention using OTEL collector for .NET framework 4.8 MVC deployed on IIS in Windows x64 not working
Trying auto instrumentation for .NET Framework 4.8 MVC application deployed on IIS Server but there is no metrics or traces generated. Added below environment variable in applicationHost file
Autoinstrumention using OTEL collector for .NET framework 4.8 MVC deployed on IIS in Windows x64 not working
Trying auto instrumentation for .NET Framework 4.8 MVC application deployed on IIS Server but there is no metrics or traces generated. Added below environment variable in applicationHost file
Autoinstrumentaion using OTEL collector for .NET framework 4.8 deployed on IIS in Windows x64 not working
Trying auto instrumentation for .NET Framework 4.8 application deployed on IIS Server but there is no metrics or traces generated. Added below environment variable in applicationHost file
Opentelemetry override or ignore client span error status
Using Opentelemetry, I am generating spans in a trace, and I have an external library that does a HTTP GET call (to Elasticsearch). This span is marked as “client” and it is marked as “error” by our otel agent. The library catches the exception and ignores it on certain http status codes, which we cannot control.
Is there something that can be done either to override that client error span status (with sdk or api) or to configure the agent so that it ignores these kind of span errors?