observability-monitoring

What problem does it solve?

Production-ready guidance to instrument Node.js/TypeScript services so teams can reliably observe, debug, and operate systems using traces, metrics, and logs unified through OpenTelemetry and complementary tooling.

Core Features & Use Cases

• OpenTelemetry Initialization: Ensure SDK starts before other imports and configure OTLP exporters for traces and metrics.
• Distributed Tracing: Auto-instrument HTTP, Express, PostgreSQL, Redis, and Socket.IO and add custom spans for business logic to correlate performance and errors.
• Metrics Instrumentation: Define counters, histograms, and gauges with naming conventions, label usage, and recording patterns for system and business KPIs.
• Structured Logging with Trace Context: Use Pino to inject traceId and spanId into JSON logs to jump from logs to Jaeger traces and Grafana Loki entries.
• Alerting & Dashboards: Provide Prometheus alert rule patterns for critical and warning signals, sampling strategies per environment, and dashboard layouts for system and game activity monitoring.
• Use Case: When an alert fires for high error rate, trace a sampled request across services, inspect spans for slow operations, and read correlated logs to identify and fix the root cause.

Quick Start

Initialize the OpenTelemetry Node SDK before importing application modules and configure OTLP exporters and auto-instrumentations so traces, metrics, and logs flow to your telemetry backend.