---
updatedAt: 2026-09-22T17:02:45.000Z
agentTools:
  projectIndex: https://docs.observeinc.com/llms.txt
---

# APM runtime metrics

Observe by Snowflake APM can automatically plot runtime metrics and infrastructure metrics for your services. This provides a fast way to answer questions like: "how is garbage collection affecting my CPU usage and service response times?" or "are we seeing an increase of goroutines associated with the service erroring?"

To view runtime metrics for your services, perform the following steps:

1. Click **APM** in the left navigation.
2. Select a service.
3. Click the metric you want to investigate, such as **Infrastructure metrics** or **Go metrics** in this example:

<Image src="https://files.readme.io/924a71cfd5f94eb70e3df35df3dfbadb474857057749c024dfb1b4ccb3022a2f-Screenshot_2026-04-30_at_8.50.22_AM.png" align="center" border={true} />

# Requirements to enable runtime metrics

The following requirements must be met in order for metrics to be plotted in APM:

1. The metrics must be sent to Observe by Snowflake in OTel format and be written to the **Metrics/OpenTelemetry** Dataset.
   * If you are running the Observe Agent on a host or containerized environment, make sure the `forwarding.metrics.output_format: otel` option is set in the `values.yaml` file. This value is set automatically if you install the Observe Agent from the Add Data portal.
   * If you are running the Observe Agent in Kubernetes, make sure the `node.forwarder.metrics.outputFormat=otel` option is set in your `values.yaml` file when installing or upgrading the Observe Agent Helm chart.  This value is set automatically if you install the Observe Agent from the Add Data portal.
2. The metrics must have temporality `delta`. This can be configured using the [standard OTel environment variable](https://opentelemetry.io/docs/specs/otel/metrics/sdk_exporters/otlp/#additional-environment-variable-configuration) `OTEL_EXPORTER_OTLP_METRICS_TEMPORALITY_PREFERENCE=delta`. For compatibility, the Observe Agent can also be configured to convert all metrics to `delta` temporality by setting `forwarding.metrics.convert_cumulative_to_delta: true` in the agent config or `node.forwarder.metrics.convertCumulativeToDelta=true` in your Helm chart `values.yaml` file.
3. Incoming metrics must include at least one of `host.name`, `k8s.pod.name`, or `container.id`. One way to do this is to set the `OTEL_RESOURCE_ATTRIBUTE` value, as shown below:
   ```text
   OTEL_RESOURCE_ATTRIBUTES=host.name=<hostname>
   ```
   You can also add an SDK Host / Pod resource detector like `.AddDetector(new HostDetector())`.

To associate your infra metrics with your services and display them alongside runtime metrics in APM, see [Associate infrastructure metrics with services](https://docs.observeinc.com/docs/associate-infrastructure-metrics-with-services).

# Supported languages and runtimes

Select a language for more information.

<Tabs>
  <Tab title="Go">
    Supported versions are v0.55.0 and later, but starting with v0.62.0 the environment variable `OTEL_GO_X_DEPRECATED_RUNTIME_METRICS` must be set to `true`.

    APM Runtime metrics plot data for the following metric names:

    * `process.runtime.go.cgo.calls`
    * `process.runtime.go.gc.count`
    * `process.runtime.go.gc.pause_ns`
    * `process.runtime.go.gc.pause_ns.count`
    * `process.runtime.go.gc.pause_ns.max`
    * `process.runtime.go.gc.pause_ns.min`
    * `process.runtime.go.gc.pause_ns.sum`
    * `process.runtime.go.gc.pause_total_ns`
    * `process.runtime.go.goroutines`
    * `process.runtime.go.mem.heap_alloc`
    * `process.runtime.go.mem.heap_idle`
    * `process.runtime.go.mem.heap_inuse`
    * `process.runtime.go.mem.heap_objects`
    * `process.runtime.go.mem.heap_released`
    * `process.runtime.go.mem.heap_sys`
    * `process.runtime.go.mem.live_objects`
    * `process.runtime.go.mem.lookups`
  </Tab>

  <Tab title="Java">
    Java runtime metric support is available when using the OTel zero-code instrumentation Java agent. See <a href="https://opentelemetry.io/docs/zero-code/java/agent/getting-started/">Getting started</a> in the OpenTelemetry documentation.

    <Callout icon="📘" theme="info">
      ### Note

      Micronaut is not supported.
    </Callout>

    Supported versions are v2.0.0 and later.

    APM Runtime metrics plot data for the following metric names:

    * `jvm.gc.duration.count`
    * `jvm.gc.duration.sum`
    * `jvm.memory.committed`
    * `jvm.memory.limit`
    * `jvm.memory.used`
    * `jvm.thread.count`
  </Tab>

  <Tab title=".NET">
    .Net runtime metric support is available when using OTel .NET zero-code instrumentation. See <a href="https://opentelemetry.io/docs/zero-code/dotnet/">.NET zero-code instrumentation</a> in the OpenTelemetry documentation.

    Supported versions are v1.4.0 and later.

    APM Runtime metrics plot data for the following metric names:

    * `process.runtime.dotnet.gc.collections.count`
    * `process.runtime.dotnet.gc.pause.time`
    * `process.runtime.dotnet.gc.last_collection.heap.fragmentation.size`
    * `process.runtime.dotnet.thread_pool.thread.count`
    * `process.runtime.dotnet.exceptions`
  </Tab>

  <Tab title="NodeJS">
    NodeJS runtime metric support is available when using OTel JavaScript zero-code instrumentation. See  <a href="https://opentelemetry.io/docs/zero-code/js/">JavaScript zero-code instrumentation</a> in the OpenTelemetry documentation.

    Supported versions are v0.62.0 and later.

    APM Runtime metrics plot data for the following metric names:

    * `nodejs.eventloop.utilization`
    * `nodejs.eventloop.delay.p99`
    * `nodejs.eventloop.time`
    * `v8js.gc.duration`
    * `v8js.memory.heap.used`
    * `v8js.memory.heap.limit`
  </Tab>
</Tabs>