What each page needs
Which attributes turn on each page.
- Traces and Service map: OTEL_SERVICE_NAME; outgoing calls from auto-instrumentation draw the arrows (databases, queues, external APIs too). - API health: HTTP server auto-instrumentation with http.route. Shows each endpoint's traffic, errors and latency, with workspace thresholds. - Deployments: service.version in OTEL_RESOURCE_ATTRIBUTES; each new value is a release, detected within about 5 minutes and compared with the 30 minutes before it. - Health: add health.check.url=https://your-service/healthz to OTEL_RESOURCE_ATTRIBUTES; checked every minute. SLOs are set per service. - Environments: deployment.environment (for example production, staging) keeps environments apart on every page. - Incidents and Logs: record exceptions on spans and send logs through the OpenTelemetry logging bridge so each line carries its trace. - Metrics: runtime and HTTP metrics instrumentation (CPU, memory, GC, thread pool, request duration). Plan-dependent. - Behavior: frontend spans with session.id and journey.step_name (see behavior). - Security: mostly automatic; make sure client.address reaches services and post dependency manifests on deploy. Attribute mappings lets a workspace map its own attribute names (for example enduser.id as the user ID) instead of renaming them.