APM

APM in the console combines three write paths:

• Application metrics and errors posted to https://api.sensobit.com/api/v1/apm/*
• Distributed traces ingested over OTLP
• RUM page timings

Service metrics and errors

curl -X POST https://api.sensobit.com/api/v1/apm/metrics \
  -H "Content-Type: application/json" \
  -H "X-API-Key: YOUR_API_KEY" \
  -d '{
    "service": "checkout",
    "name": "request.duration_ms",
    "value": 248,
    "tags": { "route": "/pay" }
  }'

curl -X POST https://api.sensobit.com/api/v1/apm/errors \
  -H "Content-Type: application/json" \
  -H "X-API-Key: YOUR_API_KEY" \
  -d '{
    "service": "checkout",
    "message": "Null invoice id",
    "type": "TypeError"
  }'

The APM page lists services, latency, error rate, and recent exceptions. Click a service to open traces that share the same service name.

Traces

The Traces view searches Tempo by service, operation, duration, and status. Opening a trace shows the span waterfall. If logs include the same trace_id, the console can correlate them.

RUM

RUM charts break down LCP, CLS, FID, and load time by page URL, browser, device, and country. Use them to catch regressions that never appear in server-side APM.

Related console pages

• Services — discovered listeners reported by the agent
• OTLP status — whether the OTLP receiver is accepting spans
• Infrastructure — the hosts those services run on