healthcheck-dotnet

Configure liveness, readiness, and startup probes for ASP.NET Core Jarvis projects.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually configuring health check endpoints, dependency readiness probes, and monitoring dashboards for ASP.NET Core applications built with the Jarvis clean architecture framework is time-consuming, error-prone, and requires deep familiarity with health check library wiring and configuration best practices.

Core Features & Use Cases

  • End-to-end health check orchestration: Automates setup of liveness, readiness, and startup probe endpoints aligned with Jarvis layer extension patterns, with guided workflows for initial setup, adding dependency probes, and enabling the monitoring dashboard.
  • Pre-built dependency provider snippets: Includes reusable, atomic configurations for common infrastructure dependencies including PostgreSQL, Redis, SQL Server, MySQL, Kafka, RabbitMQ, MinIO, and external HTTP services to add readiness checks without custom boilerplate.
  • Production-ready guardrails: Enforces best practices including configuration-based connection string resolution, timeout clamping, environment-specific UI enablement, and anti-pattern avoidance to ensure reliable, secure health check implementation.
  • Use case example: A backend team building a Jarvis-based .NET 9 e-commerce API can use this skill to add PostgreSQL and Redis readiness probes, plus a dev-only monitoring dashboard, in minutes instead of hours of manual work.

Quick Start

Use the healthcheck-dotnet skill to configure liveness, readiness, and HealthChecks UI for your existing Jarvis ASP.NET Core project.

Frequently Asked Questions about healthcheck-dotnet

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

FAQPage Schema
How do I configure ASP.NET Core health checks for a Jarvis backend project?

Setup involves wiring liveness, readiness, and startup probe endpoints using Jarvis layer extension patterns. The process applies correct endpoint wiring order, configuration-based connection string resolution, and tag-based probe categorization for infrastructure dependencies.

What infrastructure dependencies can I add readiness probes for in ASP.NET Core?

Readiness probes can be configured for relational databases, caches, message brokers, object storage, and external HTTP services. Pre-built snippets support PostgreSQL, Redis, SQL Server, MySQL, Kafka, RabbitMQ, and MinIO without custom boilerplate.

How do I set up a HealthChecks UI dashboard without exposing it in production?

HealthChecks UI dashboard setup is restricted to non-production environments through environment-specific UI enablement. This production-ready guardrail prevents exposing monitoring dashboards in production while allowing dev-only visibility.

Does this health check configuration handle connection strings and timeouts securely?

Configuration-based connection string resolution securely manages sensitive values. Timeout clamping ensures reliable health check execution, enforcing production-grade implementation requirements and avoiding common anti-patterns.

Can I use this for a .NET 9 e-commerce API built on the Jarvis framework?

Yes, it suits .NET 9 e-commerce APIs built on the Jarvis clean architecture framework. You can quickly add PostgreSQL and Redis readiness probes and a dev-only monitoring dashboard without manual boilerplate.