evernote-observability

# Evernote Observability ## Overview Comprehensive observability setup for Evernote integrations: Prometheus metrics for API call tracking, structured JSON logging, OpenTelemetry tracing, health check endpoints, and alerting rules. ## Prerequisites - Monitoring infrastructure (Prometheus, Datadog, or CloudWatch) - Log aggregation (ELK, Loki, or CloudWatch Logs) - Alerting system (PagerDuty, Opsgenie, or Slack webhooks) ## Instructions ### Step 1: Metrics Collection Track key metrics with Prometheus counters and histograms: `evernote_api_calls_total` (by method and status), `evernote_api_duration_seconds` (latency histogram), `evernote_rate_limits_total` (rate limit hits), `evernote_quota_usage_bytes` (upload quota consumption). ```javascript const { Counter, Histogram } = require('prom-client'); const apiCalls = new Counter({ name: 'evernote_api_calls_total', help: 'Total Evernote API calls', labelNames: ['method', 'status'] }); const apiDuration = new Histogram({ name: 'evernote_api_duration_seconds', help: 'Evernote API call duration', labelNames: ['method'], buckets: [0.1, 0.5, 1, 2, 5, 10] }); ``` ### Step 2: Instrumented Client Wrap the NoteStore with a Proxy that automatically records metrics for every API call. Increment counters on success/failure, observe latency in histograms, and count rate limit events. ### Step 3: Structured Logging Use JSON-formatted logs with consistent fields: `timestamp`, `level`, `method`, `duration`, `userId` (hash...