Observability

You cannot manage what you cannot measure. Monitoring SignalR requires looking at connection counts, message throughput, and transport types.

1. Performance Counters

SignalR exposes several .NET performance counters. You should track:
- **Current Connections:** Are we hitting our server limit?
- **Messages Sent/Received per sec:** Are we flooding the socket?
- **Errors:** Are users dropping frequently due to timeouts?

2. Azure Monitor Integration

If using the Azure SignalR Service, you get a beautiful dashboard with real-time metrics on message latency and connection health. You can set **Alerts** to notify the DevOps team if the 'Connection Drop Rate' exceeds 5% in a minute, indicating a network or infra issue.

3. Architect Insight

Q: "What is a 'Message Flood'?"

Architect Answer: "It's when a developer accidentally puts a Clients.All.SendAsync() inside a tight loop or a high-frequency timer. This can saturate the server's network bandwidth and freeze the client's UI thread. Always use **Throttling** or **Debouncing** for high-frequency updates on the server before pushing them to the Hub."