"An operator should never need a debugger to answer 'is the Twilio connector healthy?'"
The Problem Today
There is no runtime view of the connectors registered in a running application. Diagnosing misconfiguration, capability mismatches, or degraded connector state requires attaching a debugger or reading logs — neither of which is practical in staging or production.
What We Are Building
An opt-in ASP.NET Core middleware that exposes a /messaging/diagnostics endpoint returning a structured JSON document: all registered connectors, their declared channel schemas and capabilities, current health status, and rolling send/receive counters. The endpoint is secured by a configurable authorization policy and disabled by default in production unless explicitly enabled.
Benefits
- Connector registration and capability declarations are verifiable at runtime without code changes
- Health and throughput state is accessible to ops dashboards and alerting systems
- Misconfigured or unhealthy connectors are immediately visible without log diving
The Problem Today
There is no runtime view of the connectors registered in a running application. Diagnosing misconfiguration, capability mismatches, or degraded connector state requires attaching a debugger or reading logs — neither of which is practical in staging or production.
What We Are Building
An opt-in ASP.NET Core middleware that exposes a
/messaging/diagnosticsendpoint returning a structured JSON document: all registered connectors, their declared channel schemas and capabilities, current health status, and rolling send/receive counters. The endpoint is secured by a configurable authorization policy and disabled by default in production unless explicitly enabled.Benefits