healthcheck-dotnet-signalr

To add SignalR hub readiness probes, you register a health check that validates the accessibility of your specified SignalR hub endpoint within your ASP.NET Core application's health check endpoint workflow.

Standard ASP.NET Core health checks return false readiness signals for SignalR because they do not natively validate if the real-time hub is accessible, which can break deployment pipelines or route traffic to non-functional backend instances.

Yes, you can use this SignalR health check for routing traffic in load balancers. It satisfies the requirement to integrate standard health checks readiness workflows to verify hub accessibility for deployment pipelines and load balancer traffic routing.

Yes, this SignalR readiness probe works with .NET microservices using real-time data streaming. It is ideal for backend applications using SignalR for live notifications or chat, ensuring the hub is fully ready before allowing traffic to reach the service.

The best way to verify SignalR hub accessibility is to apply a dedicated readiness check to your /health/ready endpoint. This validates the specified SignalR hub endpoint to confirm it is operational before allowing traffic during deployment.