observability-tools

Designing effective alerts and runbooks for incident response. PROACTIVELY activate for: (1) Creating alerting rules, (2) Writing runbooks, (3) Reducing alert fatigue, (4) On-call escalation setup, (5) Incident response procedures. Triggers: "alerting", "runbook", "on-call", "pagerduty", "incident", "alert fatigue", "escalation", "playbook"

Sampling strategies for logs and traces to optimize costs while maintaining observability. PROACTIVELY activate for: (1) Configuring trace sampling, (2) Log volume reduction, (3) Head-based vs tail-based sampling, (4) Priority-based sampling, (5) Cost optimization. Triggers: "sampling", "trace sampling", "log sampling", "cost optimization", "head-based", "tail-based", "sample rate"

Unified JSON logging across Next.js, Python, and Firebase Functions using Pino and structlog. PROACTIVELY activate for: (1) Setting up structured logging, (2) Configuring Pino for Node.js, (3) Configuring structlog for Python, (4) Implementing PII redaction, (5) Log correlation with trace IDs. Triggers: "logging", "pino", "winston", "structlog", "logger", "console.log", "firebase functions logger", "setup-logging", "json logging"

W3C Trace Context propagation across service boundaries for distributed tracing. PROACTIVELY activate for: (1) Implementing trace context propagation, (2) Cross-service correlation, (3) Setting up traceparent headers, (4) Baggage propagation, (5) Multi-service debugging. Triggers: "distributed tracing", "trace context", "traceparent", "correlation", "span", "baggage", "propagation"

Sentry integration for error tracking across Next.js, Python, and Firebase. PROACTIVELY activate for: (1) Setting up Sentry SDK, (2) Configuring error boundaries, (3) Adding custom context to errors, (4) Source map configuration, (5) Release tracking. Triggers: "sentry", "error tracking", "error boundary", "exception monitoring", "crash reporting", "source maps"