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
I'm attempting to verify a custom open telemetry metric in my .net framework application using the .net SDK though the otel collector and into datadog exporter. I've verified that I can export traces and that the collect is receiving my metric using the debug exporter.
Steps to Reproduce
Start collector inside docker.
Start application
Observe metric reporting through console exporter
Observe metric collected inside of collector through debug exporter
DataDog exporter does not export metric.
Expected Result
Custom application metric exported to DataDog
Actual Result
Custom metric is not exported to datadog and no error is reported.
Collector version
0.113.0
Environment information
Environment
container: otel/opentelemetry-collector-contrib:0.113.0 thru docker desktop
OS: windows 11
@songy23 - Using delta over cumulative did resolve my issue. Thanks. I'm guessing the underlying issue was the following from the linked docs or something similar.
"Datadog might not send the first point it receives from a given timeseries if it cannot ensure this point is the true start of the timeseries. This may lead to missing points upon restarts."
Component(s)
exporter/datadog
What happened?
Description
I'm attempting to verify a custom open telemetry metric in my .net framework application using the .net SDK though the otel collector and into datadog exporter. I've verified that I can export traces and that the collect is receiving my metric using the debug exporter.
Steps to Reproduce
Expected Result
Custom application metric exported to DataDog
Actual Result
Custom metric is not exported to datadog and no error is reported.
Collector version
0.113.0
Environment information
Environment
container: otel/opentelemetry-collector-contrib:0.113.0 thru docker desktop
OS: windows 11
OpenTelemetry Collector configuration
Log output
Additional context
No response
The text was updated successfully, but these errors were encountered: