https://community.splunk.com/t5/Getting-Data-In/NET-Application-Runtime-Metrics-Not-Showing-in-Splunk-APM/m-p/752835#M119519 <P>I’m currently instrumenting a .NET application to send telemetry to Splunk Observability Cloud using the Splunk Distribution of OpenTelemetry. I can successfully see traces, spans, and infrastructure metrics in the dashboard, but runtime metrics (GC, memory, thread pool, exceptions, etc.) are not appearing for my service. I have followed the official Splunk documentation for .NET instrumentation, yet I do not see any configuration block related to runtime metrics in the docs. My current setup is deployed via Helm and Kubernetes manifests, and I want everything to be fully declarative. Traces and spans are flowing fine, and infrastructure metrics (CPU, memory at the host level) are visible.<BR />Do .NET applications instrumented with Splunk OTel automatically produce runtime metrics, or is there a separate step to enable them?<BR />If runtime metrics need to be explicitly enabled, what is the official, supported way to do this for .NET apps?<BR />Is there any documented reference from Splunk that explains enabling runtime metrics for .NET applications? I want to avoid relying on unofficial or community-inferred environment variables and stick to officially supported methods.<BR />Any guidance, examples, or references would be highly appreciated! Thank you in advance.</P> Tue, 09 Sep 2025 09:51:08 GMT sirisha 2025-09-09T09:51:08Z https://community.splunk.com/t5/Getting-Data-In/NET-Application-Runtime-Metrics-Not-Showing-in-Splunk-APM/m-p/752835#M119519 <P>I’m currently instrumenting a .NET application to send telemetry to Splunk Observability Cloud using the Splunk Distribution of OpenTelemetry. I can successfully see traces, spans, and infrastructure metrics in the dashboard, but runtime metrics (GC, memory, thread pool, exceptions, etc.) are not appearing for my service. I have followed the official Splunk documentation for .NET instrumentation, yet I do not see any configuration block related to runtime metrics in the docs. My current setup is deployed via Helm and Kubernetes manifests, and I want everything to be fully declarative. Traces and spans are flowing fine, and infrastructure metrics (CPU, memory at the host level) are visible.<BR />Do .NET applications instrumented with Splunk OTel automatically produce runtime metrics, or is there a separate step to enable them?<BR />If runtime metrics need to be explicitly enabled, what is the official, supported way to do this for .NET apps?<BR />Is there any documented reference from Splunk that explains enabling runtime metrics for .NET applications? I want to avoid relying on unofficial or community-inferred environment variables and stick to officially supported methods.<BR />Any guidance, examples, or references would be highly appreciated! Thank you in advance.</P> Tue, 09 Sep 2025 09:51:08 GMT https://community.splunk.com/t5/Getting-Data-In/NET-Application-Runtime-Metrics-Not-Showing-in-Splunk-APM/m-p/752835#M119519 sirisha 2025-09-09T09:51:08Z