Gauge metrics stop getting exported after 10-12 hours of running #4065
Unanswered
tgrieger-sf
asked this question in
Q&A
Replies: 2 comments 1 reply
-
Are you using the opentelemetry-dotnet-instrumentation project? Or are you just using the SDK and programmatically configuring metrics? If the latter, then the environment variables documented here do not apply. If using the SDK, you can try enabling self-diagnostics to see if that surfaces up any issues. |
Beta Was this translation helpful? Give feedback.
1 reply
-
This can be closed, discussed in #2360 (comment) and now know the real issue. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm setting up an observable gauge:
Because of the added
LogDebug
, I'm seeing how many measurements I'm getting back and it continues to be between 500 and 3000 at any given time. In my exporter, I'm also logging what metrics are going through my exporter and see that it's not reaching the exporter at all. Other metrics continue to work after this gauge stops working.I've tried enabling the environment variables for extra OpenTelemetry logging outlined here but no extra logs come through.
Anyone know of why this might be happening? I'm using OpenTelemetry 1.3.2 and OpenTelemetry.Extensions.Hosting 1.0.0-rc9.6 and on .NET 6.0 running on a dotnet/aspnet:6.0-alpine container running in Kubernetes.
Beta Was this translation helpful? Give feedback.
All reactions