APM v2
APM v2 is the next generation of Coralogix Application Performance Monitoring. It brings your services and databases together as entities under one health model, so you can tell which users are impacted, why, and what to do - across every service you run.
It traces requests across your services and databases, surfaces RED metrics (Rate, Errors, Duration), and correlates traces with logs, profiles, and infrastructure so you can detect and resolve issues faster.
A single catalog lists all your services and databases, and each entity opens a drilldown with the telemetry that matters for its type - health, transactions, errors, dependencies, and more.
Instrument your first service in the onboarding tutorial.
What you can do
- Explore entities in one catalog: browse every instrumented service and database, sort by health or ownership, and filter by environment, team, or health.
- Drill into a single entity: open a service or database to see its health, transactions, errors, dependencies, traces, logs, profiles, and infrastructure.
- Correlate signals: pivot from a metric spike to the traces, logs, and profiles behind it without leaving APM v2.
- Track health over time: compare current performance against a previous period and watch annotations for deployments, alerts, and configuration changes.
Entities
APM v2 monitors two entity types:
- Services: instrumented applications that receive and send requests. Services expose the full feature set: health, transactions, errors, runtime metrics, dependencies, traces, logs, profiles, and infrastructure.
- Databases: database systems your services query. Databases expose a focused set: operations, errors, traces, and their place in the service map.
Use the sidebar to switch the catalog between services and databases.
Signals
Each entity reports one or more observability signals. The catalog shows which signals are active for an entity and links you to set up any that are missing:
- Spans: distributed traces from your instrumented services.
- Span metrics: the RED metrics derived from spans. Span metrics power the catalog and the health model.
- Logs: application logs correlated to the entity.
- Profiles: CPU profiles from Continuous Profiling.
- Infrastructure: resource metrics for the hosts, pods, and containers the entity runs on.
Health
Every entity is assigned a health state based on its monitoring policies - apdex, cases, error rate, latency, log errors, and SLOs:
- Critical: one or more policies are breached.
- Warning: one or more policies are at risk.
- Healthy: all policies are within range.
- Unmonitored: no health policies evaluate for this entity yet.
How it's organized
| Surface | What it shows |
|---|---|
| Catalog | The main screen - a filterable table of all services or databases, with RED and health overview widgets above it. |
| Entity drilldown | A single entity's detail view, split into tabs for health, transactions, errors, dependencies, and more. |
| Getting started | Instrument your services with span metrics so they appear here. |
| Use cases | Common tasks mapped to features, plus a role-based tour. |
What you need
- Instrumented services that send spans to Coralogix. See the onboarding tutorial.
- Compact span metrics enabled for both services and databases. This is what gives an account access to APM v2 - regular Span Metrics alone is not enough. See Using compact Span Metrics.
Related resources
Next steps
See how each role uses APM v2 in Use cases.