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
Team, I have upgraded the SDK from 1.32 to 2.8.0. The Garbage collection data not reporting in build dashboards like Java runtime metrics (Otel 2.x) and AlwaysOn Profiling. And I haven't faced issues with 1.32.0. Based on the documentation I observed the necessary metrics jvm.gc.duration is reporting data. Also I did enabled histogram but no luck. Here is configuration for your review.
One thing you can do to verify whether or not the metric is being emitted is to enable verbose logging for metrics in your collector. In brief, this can be done by adding a logging exporter to your configuration. Once you do that, you can grep the logs for jvm.gc.duration to confirm that the datapoints are making it from the app to the collector.
Otherwise, it does look like you're looking at the new 2.x dashboard, and that's correct, so it's definitely odd that the gc metrics aren't showing up. If you've confirmed that the metric is indeed reaching the collector, I unfortunately think the next step would be to open a support ticket for additional help.
Team, I have upgraded the SDK from 1.32 to 2.8.0. The Garbage collection data not reporting in build dashboards like Java runtime metrics (Otel 2.x) and AlwaysOn Profiling. And I haven't faced issues with 1.32.0. Based on the documentation I observed the necessary metrics jvm.gc.duration is reporting data. Also I did enabled histogram but no luck. Here is configuration for your review.
Splunk Agent: Helm Chart 0.113.0
Splunk Observability Cloud
valueFrom:
fieldRef:
fieldPath: status.hostIP
- name: OTEL_EXPORTER_OTLP_ENDPOINT
value: "http://$(splunk_otel_agent):4318/"
- name: OTEL_SERVICE_NAME
value: ""
- name: SPLUNK_PROFILER_ENABLED
value: "true"
- name: SPLUNK_PROFILER_MEMORY_ENABLED
value: "true"
- name: SPLUNK_PROFILER_DIRECTORY
value: "/tmp"
Screen shots:
Much appreciate your timely help and please revert for additional details.
The text was updated successfully, but these errors were encountered: