Open in ChatGPTOpen in Claude

APM v2 isn't showing my data

When an entity or a metric you expect isn't there, work from the symptom you see. Each row below maps a symptom to its most likely cause and the fix.

Symptom	Likely cause	Fix
No entities at all	The Collector isn't running, or it exports to the wrong region endpoint.	Check the Collector's exporter logs, and confirm the region endpoint.
A service is missing	Its spans carry no service.name.	Set the service.name resource attribute on the service's spans.
A service appears, but has no RED metrics	The spanMetrics preset is disabled.	Enable it in your values.yaml - see the onboarding tutorial.
Databases are missing	Client spans lack db.system or db.operation.name.	Emit database client spans that follow the OpenTelemetry database semantic conventions.
An entity shows as Unmonitored	No health policy has data to evaluate yet.	Expected for a new service. See Service health to add or wait for policies.
Everything is present, but APM v2 is unavailable	The account isn't sending compact span metrics on services and databases.	Migrate - see Using compact Span Metrics.
The Transactions tab is empty	The transactions processor isn't enabled.	See Enable the transactions processor.
The Runtime tab is empty on a Java service	JVM runtime metrics aren't being exported.	See Send JVM metrics.

Still stuck?

If data is flowing but a specific tab stays empty, open the entity's drilldown - a tab with no data names the signal it needs and links to its setup. For anything else, contact [email protected].

Next steps

Once your data appears, explore it in the catalog.