What problem does it solve?
When building .NET backend services, you need to confirm that external dependent APIs and services are reachable and healthy before marking your service as ready to accept traffic, preventing routing requests to a service that cannot fulfill them due to downstream outages.
Core Features & Use Cases
- Custom IHealthCheck Implementation: Uses IHttpClientFactory to send GET requests to configured external endpoints, returning a healthy status if the endpoint responds with a success HTTP status code.
- Robust Error Handling: Returns an unhealthy status if the endpoint returns a non-success status code or is unreachable due to network issues, with optional exception details for debugging.
- Use Case: For a .NET microservice that relies on a third-party payment processing API, use this skill to add a readiness probe that verifies the payment API is accessible before the service starts handling user requests.
Quick Start
Use the healthcheck-dotnet-http skill to add a readiness check for your external payment API endpoint configured in your application settings.