Add optional LGTM stack subchart to rstudio-connect with preconfigured OTel integration

Summary

Add an optional LGTM stack (Loki, Grafana, Tempo, Mimir) as subchart dependencies to the rstudio-connect chart, preconfigured to receive telemetry from Connect via OpenTelemetry.

This would give operators a path to full observability when deploying Connect on Kubernetes.

Motivation

Connect 2026.03.0 deprecated the legacy Metrics.Enabled / Graphite-based pipeline in favor of OpenTelemetry (see #820). With that transition, Connect can now emit metrics, traces, and logs over standard OTel protocols — but users are left to wire up their own backend.

The LGTM stack is the natural Grafana-ecosystem target for OTel data:

Bundling these as opt-in subcharts with sane defaults would make Connect observability accessible out of the box for teams that don't already have a monitoring stack.

Proposed approach

1. Add optional subchart dependencies in Chart.yaml (all disabled by default):

   • grafana/grafana
   • grafana/loki
   • grafana/tempo
   • grafana/mimir-distributed (or prometheus-community/prometheus as a lighter alternative)

2. Preconfigure Connect OTel settings in values.yaml when the subcharts are enabled — pointing Connect's OTel exporter endpoints at the in-cluster Mimir, Tempo, and Loki services.

3. Ship a starter Grafana dashboard (as a ConfigMap) covering the key Connect OTel metrics exposed since 2026.03.0.

4. Document a values.yaml snippet that enables the full stack in one block, suitable for local dev/demo use.

Related

• #820 — removes the deprecated Metrics.Enabled setting and is a prerequisite for this work
• Connect OTel docs

Acceptance criteria

• LGTM subcharts are opt-in (no change to default deploys)
• When enabled, Connect metrics/traces/logs flow to the stack without additional configuration
• A starter Grafana dashboard is included and auto-provisioned
• README documents the feature and the values snippet to enable it

Start with Chart.yaml and values.yaml, then review the README and the proposed ConfigMap dashboard work. Read related issue #820 and the linked Connect OTel documentation before assessing the dependency and exporter configuration. Done means opt-in subcharts, end-to-end telemetry without extra configuration, an auto-provisioned starter dashboard, and documented enablement values.