OpenTelemetry

@opentelemetry is the semantic layer and app in one pack, and one of the two always-installed integrations. It reads the tables the collector already writes and adds no collector config of its own.

What it installs

• Base views — @opentelemetry/views/traces, views/logs, views/metrics_sum / metrics_gauge / metrics_histogram, views/storage, and the combined views/combined. These are page-less: they name the OpenTelemetry semantic conventions once — ServiceName, DurationP95, IsError, and the rest — as pure, reusable bindings that every other pack’s frames build on via imports. See Views.
• Dashboards — a tabbed hub (Overview, RUM, Infrastructure, Volume, Database, Reliability) whose Overview leads with what changed rather than raw levels, alongside separate top-level routes for the full services and traces inventories, plus per-entity pages: a service detail whose tab set adapts to what the service is (a backend, a browser app, or metrics only), entry operation, RUM session, trace waterfall, host, and Kubernetes namespace / workload / pod pages.

Settings

None beyond enabling — there’s no integrations.installed.opentelemetry configuration.