healthcheck-dotnet-rabbitmq

What problem does it solve?

.NET backend projects require reliable readiness probes to verify that all dependent services, including message brokers like RabbitMQ, are available before the instance starts receiving traffic. Manually implementing and configuring RabbitMQ health checks is repetitive and error-prone, especially when following standardized architecture patterns like Clean Architecture.

Core Features & Use Cases

• Pre-configured RabbitMQ Readiness Registration: Provides ready-to-use code to add RabbitMQ health checks to the .NET HealthChecks pipeline with correct tagging for readiness probes.
• Configuration-Driven Setup: Loads the RabbitMQ connection string directly from application configuration, eliminating hardcoded values and supporting environment-specific settings.
• Jarvis Framework Integration: Aligns with the Jarvis backend framework's standard health check registration pattern, ensuring consistency across all service modules.
• Use Case: A microservice that processes async messages via RabbitMQ can use this skill to automatically add a readiness probe that fails if RabbitMQ is unreachable, preventing the service from being added to the load balancer pool until the message broker is available.

Quick Start

Use the healthcheck-dotnet-rabbitmq skill to register a RabbitMQ readiness health check in your .NET project's health check configuration.