Minor Changes
-
#443
178a1f9Thanks @chrisdoc! - Add OpenTelemetry instrumentation with dual export to Sentry and an
OTel Collector (forwarding to Honeycomb and other backends).- New
src/utils/telemetry.tsinitializes OpenTelemetry with a custom
tracer provider that has dual span processors:SentrySpanProcessor
for Sentry (errors + traces) andBatchSpanProcessorwith
OTLPTraceExporterrouted through our own OTel Collector, which
forwards traces and metrics to Honeycomb and other backends. - New
src/utils/metrics.tsdefines metric instruments (counters and
histograms) for tool invocations, errors, duration, API calls, API
latency, stdio parse errors, and server startups. - Migrated all
Sentry.startSpan()calls to the OpenTelemetry API
(tracer.startActiveSpan()) for vendor-neutral span creation.
Spans are still exported to Sentry via theSentrySpanProcessor. - Added axios interceptors to
hevyClientKubb.tsfor automatic HTTP
tracing and metrics recording on every Hevy API call. - The collector endpoint and auth token are injected at build time
from theOTEL_COLLECTOR_ENDPOINTandOTEL_COLLECTOR_TOKEN
GitHub secrets viatsdown.config.tsdefine. Traces and metrics
are sent to the OTel Collector, which forwards them to Honeycomb
and other observability backends. - Sentry remains the error monitoring backend (captureException,
setUser, withScope, wrapMcpServerWithSentry).
- New