Traces, logs, metrics, service map, API health, dashboard
What the core observability pages do.
- Dashboard: request pulse (p95 latency colored by error rate), recent deploys, incidents and alerts, and services ranked worst first. - Traces: every request across services with timing and errors; search and filter by attributes; trace history. - Logs: a live stream with filters, logs linked to their trace, and patterns that group similar lines by template. - Metrics: dashboards built from templates (HTTP traffic, runtime, dependencies); every chart can be changed, moved or removed. - Service map: who calls whom, including databases, queues and external APIs; select a node to see callers and dependencies. - API health: per-endpoint traffic, error rate and latency; thresholds decide what counts as failing, slow or rejecting callers. - Statistics: business numbers (orders, revenue, sign-ups, refunds) counted straight from span and log attributes, with suggestions. - Ingestion errors: telemetry that couldn't be kept and the setting that fixes it.