/api/v1/apm prefix and require a bearer token.
streams.query. A platform caller can use
sys.telemetry.read in the protected _sys scope.
Endpoints
Path parameters must be URL-encoded. Use the exact
transaction name or error fingerprint
returned by a list response.
Common query parameters
Filters must be non-empty and no longer than 192 bytes. The range cannot exceed the configured
maximum, which defaults to 30 days.
Sort fields
/overview accepts the same filters and resolution but does not paginate. Detail, comparison, and
health endpoints do not return paginated lists.
Query an overview
red, trend, service_health, services, top_transactions,
top_dependencies, top_errors, and recent_versions, plus a common meta object.
List and paginate services
next_cursor or previous_cursor unchanged with the same endpoint, filters, range, sort, and
direction. Cursors are signed and scoped to the original request context. Do not decode or edit a
cursor.
Disambiguate a transaction
Two transaction kinds can share a name. Pass the optionalkind parameter to select one:
http, rpc, messaging, span, and other.
Compare versions
Supply differentbaseline and candidate values. Add a service filter to compare one service.
sufficient_data becomes true only
when both versions meet the configured sample threshold, which defaults to 1,000 requests per
version.
Read response metadata
Every endpoint returns a commonmeta object:
- Treat
activation_boundary: trueas incomplete coverage beforeprojection_started_at. - Treat
data_quality.partial: trueas incomplete data, not as a complete zero. - Inspect
gapsfor queue, repository, flush, late-data, cardinality, or shutdown failures. - Use
last_complete_bucket_atto determine whether recent data is still being finalized. - Inspect
overflow_dimensionsbefore relying on a high-cardinality breakdown.
APM guide
Instrument services and investigate performance in the UI.
Trace intake
Send OpenTelemetry traces that feed APM.