xabaril/aspnetcore.diagnostics.healthchecks

Enterprise HealthChecks for ASP.NET Core Diagnostics Package

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 58 minutes ago
Added to GitGenius on September 15th, 2026
Created on September 27th, 2018
Open Issues & Pull Requests: 379 (+0)
GitHub issues: Enabled
Number of forks: 867
Total Stargazers: 4,373 (+0)
Total Subscribers: 96 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 10.2 days
Mean response time: 94.3 days
90th percentile: 297.8 days
Tracked items: 87

Most active contributors

Sign in to see contributor activity.

How this project is maintained

96% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 59% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 101
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 665 days
Stale 30+ days: 97
Stale 90+ days: 92

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • Ups for grabs (6)
  • enhancement (6)
  • UI (5)
  • help wanted (4)
  • question (3)
  • azure (2)
  • bug (2)
  • good first issue (2)

Detailed Description

Aspnetcore.diagnostics.healthchecks is a health check library for ASP.NET Core applications that provides enterprise-grade diagnostic capabilities.

The library addresses the need to monitor the health and availability of application dependencies and services in production environments. It works by integrating with ASP.NET Core's built-in health check infrastructure, allowing developers to define custom health checks that probe various system components—databases, external APIs, message queues, and other critical resources—and report their status through standardized endpoints. This enables applications to expose health information that orchestration platforms, load balancers, and monitoring systems can consume to make routing and scaling decisions.

Teams building ASP.NET Core applications that require comprehensive dependency monitoring should consider this tool, particularly those running in containerized or cloud environments where health checks drive infrastructure decisions. It suits projects that need to verify connectivity and responsiveness across multiple external services as part of their operational readiness checks. The library integrates directly with ASP.NET Core's native health check system rather than requiring a separate framework, making it a natural fit for applications already using that platform.

The project maintains steady activity with regular updates addressing bug fixes and compatibility improvements. Development includes ongoing refinement of existing health check implementations and responsiveness to issues raised by users. The maintainers demonstrate commitment to keeping the library compatible with current ASP.NET Core versions and addressing reported problems in a timely manner.