How evertonvargas/observability works
This repository is a small Fastify service instrumented for observability, alongside configuration for an observability stack. An HTTP client reaches the service’s test and error routes; those routes record metrics, and the error route logs failures. The server starts the OpenTelemetry SDK, which configures metric and trace exporters. Logger and tracer implementations are included because they are core modules. The README is empty, and the configuration files were not excerpted, so their runtime wiring and backend relationships are not asserted.
Main entry points: tracer.ts Telemetry setup · server.ts Fastify server · logger.ts Pino logger
Components 13
Application
- Fastify server
app/src/server.ts - Test route
app/src/server.ts - Error route
app/src/server.ts - Pino logger
app/src/infra/logger.ts
Telemetry
- Telemetry setup
app/src/tracer.ts - OTLP metrics exporter
app/src/tracer.ts - OTLP trace exporter
app/src/tracer.ts
Observability Stack
- Collector config
config/otel/otel.yaml - Prometheus config
config/prometheus/prometheus.yaml - Mimir config
config/mimir/mimir.yaml - Tempo config
config/tempo/tempo.yaml - Grafana datasource
config/grafana/datasources.yaml
Other components
- HTTP client
Connections 9
- HTTP client → Fastify server: sends requests
app/src/server.ts - Fastify server → Test route: registers route
app/src/server.ts - Fastify server → Error route: registers route
app/src/server.ts - Fastify server → Telemetry setup: starts SDK
app/src/server.ts - Test route → Telemetry setup: records metrics
app/src/server.ts - Error route → Telemetry setup: records metrics
app/src/server.ts - Error route → Pino logger: logs errors
app/src/server.ts - Telemetry setup → OTLP metrics exporter: configures
app/src/tracer.ts - Telemetry setup → OTLP trace exporter: configures
app/src/tracer.ts