healthcheck-dotnet-kafka

To add Kafka readiness checks to an ASP.NET Core microservice, you register the Kafka broker connectivity health check using the standard AddKafka() extension method. This validates broker availability and exposes status via the /health/ready endpoint.

Kafka health checks in a .NET application validate broker connectivity. They ensure your microservice only receives traffic when the Kafka messaging infrastructure is actually reachable, preventing routing requests to instances with broken dependencies.

Yes, you need the AspNetCore.HealthChecks.Kafka package to configure .NET Kafka probes. This dependency provides the AddKafka() extension method required to register connectivity validation within your ASP.NET Core health check pipeline.

Yes, you can configure Kafka health checks using application configuration. This setup reads Kafka bootstrap server addresses directly from your configuration sources, avoiding hardcoded connection strings and streamlining environment management.

You should use Kafka readiness probes for .NET microservices when your services produce or consume Kafka messages. This ensures the application only accepts traffic if the Kafka broker is verified as available during the health check pipeline execution.