healthcheck-dotnet-rabbitmq

Register RabbitMQ readiness health checks in ASP.NET Core projects.

12|2|Updated May 4, 2020
One-click install
npx skills add https://github.com/hoangnh2412/jarvis --skill healthcheck-dotnet-rabbitmq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: healthcheck-dotnet-rabbitmq
Source: https://github.com/hoangnh2412/jarvis/tree/main/.opencode/skills/healthcheck-dotnet/providers/rabbitmq
Command: npx skills add https://github.com/hoangnh2412/jarvis --skill healthcheck-dotnet-rabbitmq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires AspNetCore.HealthChecks.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.

Frequently Asked Questions about healthcheck-dotnet-rabbitmq

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add RabbitMQ readiness probes to ASP.NET Core health checks?

RabbitMQ readiness probes integrate into ASP.NET Core health checks by registering a connection status check in the standard HealthChecks:Readiness pipeline using configuration-driven connection strings and failure status tagging.

Why do I need a RabbitMQ health check in my .NET microservice?

A RabbitMQ health check ensures your .NET microservice fails its readiness probe if the message broker is unreachable, preventing Kubernetes or load balancers from routing traffic to the instance until RabbitMQ is available.

Does this RabbitMQ health check integration require hardcoded connection strings?

No, this RabbitMQ health check integration uses a configuration-driven setup that loads the RabbitMQ connection string directly from application configuration, supporting environment-specific settings without hardcoded values.

Can I use this RabbitMQ readiness probe with any .NET backend framework?

This RabbitMQ readiness probe is specifically designed for .NET 9 projects using the Jarvis framework, aligning with its standard health check registration pattern to ensure consistency across all service modules.

What is the best way to monitor message broker availability for Kubernetes readiness in .NET?

The best way to monitor message broker availability for Kubernetes readiness in .NET is adding a RabbitMQ health check to the standard ASP.NET Core HealthChecks pipeline to verify connection status before receiving traffic.

Do I need the AspNetCore.HealthChecks.RabbitMQ package to set up message broker readiness probes?

Yes, setting up these message broker readiness probes requires the AspNetCore.HealthChecks.RabbitMQ dependency to provide the underlying RabbitMQ connection status monitoring functionality for the health checks pipeline.