Free, Open Source, Self-Hosted WhatsApp API Gateway
TypeScript apibotgatewayself-hostedwhatsappwhatsapp-apiwhatsapp-automationwhatsapp-botwhatsapp-gatewaywhatsapp-gateway-apiwhatsapp-webwhatsapp-web-api
docs(metrics): name both reconnect counter increment sites
Yudhi Armyndharis722c15b72e99
diff --git a/src/common/metrics/session-reconnect-metrics.ts b/src/common/metrics/session-reconnect-metrics.tsindex 934ca5ec3..b83e862ce 100644--- a/src/common/metrics/session-reconnect-metrics.ts+++ b/src/common/metrics/session-reconnect-metrics.ts@@ -1,6 +1,8 @@/**- * Process-local monotonic counters for session reconnect observability, incremented one-for-one in- * `SessionEngineLifecycle.scheduleReconnect`. Kept as plain in-process counters rather than a `COUNT(*)` over+ * Process-local monotonic counters for session reconnect observability, incremented by whichever layer+ * schedules the retry: `SessionEngineLifecycle.scheduleReconnect` for service-level reconnects, and the+ * engine `onReconnecting` callback wired in `session-engine-event-wiring.ts` for engine-internal ones+ * (Baileys). Kept as plain in-process counters rather than a `COUNT(*)` over* any persisted table because reconnect scheduling itself is not persisted at all — there is no* durable source to count, and a pruned/rotated one would be non-monotonic and therefore invalid as a* Prometheus `counter` (a prune would look like a counter reset to `rate()`/`increase()`). An