Dash0
Traces and metrics from influence-api, over OpenTelemetry.
Track: Stop Flying BlindWhat we built
influence-api sends its traces and metrics to Dash0 over OpenTelemetry (OTLP), so every reading, find and alert can be followed from the phone's post to the response. A rule for every pull request keeps it that way: instrument new behaviour, then show it on the dashboard.
How it works
influence-api/telemetry.mjsstarts OpenTelemetry's Node auto-instrumentation before the server (node --import ./telemetry.mjs server.js), only whenOTEL_EXPORTER_OTLP_ENDPOINTis set. The zone sets Dash0's endpoint (us-west-2, datasetdefault) and its token as secret env inOTEL_EXPORTER_OTLP_HEADERS; a local run sends nothing./api/integrationstells the map that telemetry is on and to which host, never a key or a header.- The instrumentation rule,
hero-goggles/.gitar/rules/instrumentation.md(also in influence-api): spans named likeinfluence.find, counters and histograms namedinfluence_<what>_<unit>, a dashboard panel for each, and one structured log line per failure with its trace id.
Status
Live influence-api's traces and metrics in Dash0 since 9 November 2026, v0.1.4, sent directly over OTLP, without Dash0's operator.
Not live The dashboards as code: the rule names a dashboards/ folder of Perses YAML, which Dash0 reads, but no repo has one yet.
Not live Browser telemetry from hero-goggles.