Library / SDK
Xabaril/AspNetCore.Diagnostics.HealthChecks avatar
Xabaril/AspNetCore.Diagnostics.HealthChecks

Xabaril's AspNetCore.Diagnostics.HealthChecks: one probe per dependency, and what it costs you

Enterprise HealthChecks for ASP.NET Core Diagnostics Package

4,372 stars863 forksC#Apache-2.0

At a glance

What is it?
A monorepo of health check packages for ASP.NET Core services, where each external system you depend on has its own NuGet package. The value is breadth and a UI with history; the cost is a large dependency tree and a support matrix that stops at .NET 8.
Who is it for?
Adopt the individual package for a dependency you actually run, and take the UI only if you have a storage provider and somewhere for the history to be useful. Skip the whole catalogue if you would rather write three lines of IHealthCheck against your own client.
Can I use it commercially?
Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 146 days ago.
What is it written in?
Mainly C#, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • Xabaril/AspNetCore.Diagnostics.HealthChecks4,372 ★ · -3
Star history
Repository2026-09-232026-11-15
Xabaril/AspNetCore.Diagnostics.HealthChecks4.4k4.4k

-3 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

One repository, one NuGet package per external dependency

The problem this repository solves is unglamorous and real: once a service leans on a dozen outside systems, somebody has to write a probe for each one, and hand-written probes rot. The answer here is a package per dependency, published under the AspNetCore.HealthChecks prefix, each registering itself with the health check system ASP.NET Core already ships in the framework. The catalogue runs from ApplicationStatus through ArangoDB to Amazon S3, Secrets Manager, SNS and SQS, and a long Azure line covering Key Vault secrets, Blob Storage and Event Hubs, with more listed in the README.

That breadth is the actual design. You take only the packages for systems you genuinely run, so a service sitting on SQL Server and a Redis queue inherits two targeted checks rather than one generic TCP ping that tells you nothing about authentication. The trade sits on the other side of the ledger: every package drags its own client library and its own upgrade cadence into your lock file, and two of those packages will not have identical support windows.

The UI turns a pass or fail endpoint into a timeline, and needs a store to do it

HealthChecks.UI is the piece that changes how the checks get used day to day. A bare health endpoint answers one question at one instant: are you up right now. Add the UI and each result is written down, then rendered as a health status history timeline, with storage providers and database migrations as the retention mechanism.

That dependency is where first contact with the UI usually goes sideways. The UI is not self-contained; history needs a backing store, and the repository ships a dedicated sample project, HealthChecks.UI.StorageProviders, alongside the UI sample itself. Configuration covers the UI, the storage providers and an HttpClient plus HttpMessageHandler setup for API and webhook endpoints, that last one existing because a dashboard which fans out failure notifications has to make outbound calls from inside the process being probed. Webhooks and failure notifications are a first-class feature, not an add-on.

A Kubernetes operator replaces hand-written probes in the cluster

Inside Kubernetes the usual probe story is a hand-written httpGet or exec block on every deployment manifest, which drifts from the checks your application already performs. This repository ships a Kubernetes operator, with a k8s-operator sample directory and a Docker image built by build-operator-image.ps1, and pairs it with automatic services discovery so the checks follow what is actually deployed rather than what a manifest said three deployments ago.

Probe results as an Azure DevOps pipeline condition

The DevOps angle is a documented section of its own: using health checks as a pipeline condition in Azure DevOps. The point is ordering. A pipeline that promotes an artifact before probing the running service treats a green build as proof of health, which it is not. This repository gives the pipeline something concrete to assert on, since each check reports a named dependency rather than a single aggregate verdict.

Backing services come from the repository docker-compose.yml, not from a quick start

Start from NuGet: pick the package matching your dependency, for example AspNetCore.HealthChecks.Azure.Storage.Blobs or AspNetCore.HealthChecks.Aws.S3, and add it the way you add any NuGet reference. To see the UI against real stores rather than guess, the repository ships the dependency stack it develops against. This excerpt runs SQL Server on a nonstandard host port so it does not collide with a local instance:

yaml
    sqlserver:
        image: mcr.microsoft.com/mssql/server
        restart: always
        ports:
            - 5433:1433
        environment:
            - ACCEPT_EULA=Y
            - SA_PASSWORD=Password12!

The file continues with redis, elasticsearch, solr, clickhouse, postgres, eventstore, mongodb, mysql and others, each with its port bound to a variable such as ${REDIS_PORT} or ${SOLR_PORT} rather than a fixed number. Expect to supply those variables from a .env file before anything starts, and note that the file is a development fixture with a default SA password in plain text, not a deployment template.

The version list stops at 8.0 and nothing above it is named

The README states the supported ASP.NET Core versions as 8.0, 7.0, 6.0, 5.0, 3.1, 3.0 and 2.2. Nothing above 8.0 appears in that list. If you are starting a service on a runtime past 8.0, the documentation gives you no confirmation that the packages target it, and that is the first thing to check before you adopt anything from this catalogue.

The repository is not archived, the last push was on 2026-06-22, and licensing is Apache-2.0, which matters if you plan to wrap these packages inside a proprietary product.

A hand-written IHealthCheck when the package is overkill

The alternative worth naming is the framework's own IHealthCheck interface, which you implement yourself in a few lines and register the same way. The difference in approach is specific. A package from this repository already knows the authentication scheme, the ping command and the failure strings for one named system. Your own implementation knows only what you already know and stays correct only as long as you maintain it.

So the choice is not library versus no library, it is breadth versus footprint. If you depend on Redis and Kafka, two packages here remove real work. If you depend on one internal HTTP service, you have written that check already, and adding a package buys you a dependency without a matching probe. The catalogue is persuasive precisely because it is long, which is also why choosing by row count is the wrong way in.

Editorial conclusion

Adopt the individual package for a dependency you actually run, and take the UI only if you have a storage provider and somewhere for the history to be useful. Skip the whole catalogue if you would rather write three lines of IHealthCheck against your own client. Before anything else, open the README version list and confirm your runtime appears in it, because 8.0 is the highest one named in that list. Then look for the migration that matches the storage provider you intend to use, since the UI stores every result somewhere and nothing works until that choice is settled.

Frequently asked questions

How can I perform health checks in ASP.NET Core with Xabaril's packages?

Add the AspNetCore.HealthChecks package that matches the dependency you need, such as AspNetCore.HealthChecks.Azure.Storage.Blobs or AspNetCore.HealthChecks.Aws.S3, from NuGet. Each package registers its own check with the health check system built into ASP.NET Core, and the repository documents support for ASP.NET Core 8.0, 7.0, 6.0, 5.0, 3.1, 3.0 and 2.2.

Is ASP.NET Core still supported by Xabaril's AspNetCore.Diagnostics.HealthChecks?

The README names 8.0 as the highest ASP.NET Core runtime supported, with 7.0, 6.0, 5.0, 3.1, 3.0 and 2.2 below it and nothing above it listed. Check the packages yourself if you run something newer.

How do you configure health checks in .NET Core microservices with AspNetCore.Diagnostics.HealthChecks?

Add one package per external dependency the service talks to, so each check is registered by its own package instead of a single generic probe. The UI package adds history on top, and it needs a storage provider plus the database migrations that go with it.

What alternative is there to AspNetCore.Diagnostics.HealthChecks?

You can implement the framework's own IHealthCheck interface yourself and register it in the same way, keeping full control over the probe and adding no third party package. The difference is that the packages here already encode the authentication and ping logic for named systems such as ArangoDB or Azure Key Vault secrets.

Official sources

  1. Issues
  2. License: Apache-2.0
  3. README
  4. Releases
  5. Xabaril/AspNetCore.Diagnostics.HealthChecks on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/xabaril-aspnetcore-diagnostics-healthchecks.svg)](https://hysenlabs.com/projects/xabaril-aspnetcore-diagnostics-healthchecks)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/xabaril-aspnetcore-diagnostics-healthchecks.svg)](https://hysenlabs.com/projects/xabaril-aspnetcore-diagnostics-healthchecks)

Was this useful?