feat: add OpenTelemetry instrumentation and dual log transport - #3
Open
bautrey wants to merge 1 commit into
Open
feat: add OpenTelemetry instrumentation and dual log transport#3bautrey wants to merge 1 commit into
bautrey wants to merge 1 commit into
Conversation
Add observability stack following the Gateway API reference pattern: - OTel SDK with auto-instrumentation for HTTP, Fastify, and pino - pino-opentelemetry-transport for dual log output (stdout + Grafana Loki) - Separate logger module with sensitive header redaction - Health check endpoint filtering from traces - Gated activation via OTEL_EXPORTER_OTLP_ENDPOINT env var Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
instrumentation.ts— loaded via--importbefore app codelib/logger.ts— pino with dual transport (stdout + Grafana Cloud Loki)OTEL_EXPORTER_OTLP_ENDPOINT— zero impact when not setPart of
Fortium Observability Standardization (PRD-OBS-001, Phase 2)
Post-merge action required
Set in Render dashboard:
OTEL_EXPORTER_OTLP_ENDPOINT— Grafana OTLP gateway URLOTEL_EXPORTER_OTLP_HEADERS— Basic auth headerOTEL_SERVICE_NAME=outbound-apiTest plan
OTEL_EXPORTER_OTLP_ENDPOINTset{service_name="outbound-api"}{service_name="outbound-api"}🤖 Generated with Claude Code