Healthie.NET.Checkers 4.1.0

Prefix Reserved

dotnet add package Healthie.NET.Checkers --version 4.1.0

NuGet\Install-Package Healthie.NET.Checkers -Version 4.1.0

This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.

<PackageReference Include="Healthie.NET.Checkers" Version="4.1.0" />

For projects that support PackageReference, copy this XML node into the project file to reference the package.

<PackageVersion Include="Healthie.NET.Checkers" Version="4.1.0" />
                    

                            Directory.Packages.props

<PackageReference Include="Healthie.NET.Checkers" />
                    

                            Project file

For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.

paket add Healthie.NET.Checkers --version 4.1.0

The NuGet Team does not provide support for this client. Please contact its maintainers for support.

#r "nuget: Healthie.NET.Checkers, 4.1.0"

#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.

#:package Healthie.NET.Checkers@4.1.0

#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.

#addin nuget:?package=Healthie.NET.Checkers&version=4.1.0
                    

                            Install as a Cake Addin

#tool nuget:?package=Healthie.NET.Checkers&version=4.1.0
                    

                            Install as a Cake Tool

The NuGet Team does not provide support for this client. Please contact its maintainers for support.

Healthie.NET.Checkers

▶ Live demo — healthie.compiletheory.com — a read-only Healthie.NET dashboard watching real status pages (Anthropic, OpenAI, GitHub, Cloudflare, and more), built from these packages.

Ready-made pulse checkers for the things nearly every application ends up watching, so there is no checker code to write.

Installation

dotnet add package Healthie.NET.Checkers

Usage

using Healthie.Abstractions.Scheduling;
using Healthie.Checkers;

builder.Services
    .AddHealthie(typeof(Program).Assembly)
    .AddHealthieHttpChecker("payments-api", new Uri("https://payments.internal/health"),
        PulseSchedule.Every(TimeSpan.FromSeconds(30)))
    .AddHealthieTcpChecker("postgres", "db.internal", 5432,
        PulseSchedule.Every(TimeSpan.FromMinutes(1)))
    .AddHealthieCertificateChecker("public-tls", "example.com",
        PulseSchedule.Cron("0 3 * * *"), warnWithin: TimeSpan.FromDays(30))
    .AddHealthieDnsChecker("apex-dns", "example.com",
        PulseSchedule.Every(TimeSpan.FromMinutes(5)))
    .AddHealthieDiskSpaceChecker("data-volume", "/data",
        PulseSchedule.Cron("*/15 * * * *"));

Each call takes a name. The same type is usually registered several times — three endpoints, two drives — and the name is what separates them in storage, in the REST API and on the dashboard.

Unlike checkers you write yourself, these are not found by assembly scanning: each has to be told what to watch.

The checkers

Call	Watches	Healthy when
`AddHealthieHttpChecker`	An HTTP endpoint	The status passes your predicate (any 2xx by default)
`AddHealthieTcpChecker`	A TCP port	The port accepts a connection within the timeout
`AddHealthieCertificateChecker`	TLS certificate expiry	More than `warnWithin` left
`AddHealthieDnsChecker`	Name resolution	The name resolves to at least one address
`AddHealthieDiskSpaceChecker`	Free disk space	Above the warning threshold

Two of them use all three states

Certificate expiry and disk space are gradual and knowable in advance, so both report suspicious before they report unhealthy — a certificate inside its warning window, a drive below the warning threshold but above the critical one. That warning is the useful signal; by the time either is unhealthy it is already an outage.

The others are binary and only ever report healthy or unhealthy. Give them an unhealthyThreshold if you want a blip to read as suspicious rather than an outage.

HTTP client configuration

The HTTP checker resolves its client from IHttpClientFactory under the name HttpPulseChecker.HttpClientName. Configure its timeout, handler or retry policy by naming it in your own registration:

builder.Services.AddHttpClient(HttpPulseChecker.HttpClientName, client =>
{
    client.Timeout = TimeSpan.FromSeconds(5);
});

The request reads headers only — a health endpoint that returns a body is common, and downloading it to discard it is work this check does not need to do.

Product	Compatible and additional computed target framework versions.
.NET	net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 was computed. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed.

Product

.NET

Compatible target framework(s)

Included target framework(s) (in package)

Learn more about Target Frameworks and .NET Standard.

net10.0
- Healthie.NET.Abstractions (>= 4.1.0)
- Microsoft.Extensions.Http (>= 10.0.10)
net8.0
- Healthie.NET.Abstractions (>= 4.1.0)
- Microsoft.Extensions.Http (>= 10.0.10)

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version	Downloads	Last Updated
4.1.0	35	7/30/2026
4.0.0	38	7/30/2026

Twenty packages was too many, and two of them had no business being separate. This release fixes
that without breaking anything: **an application on 4.0.0 upgrades by changing nothing.**

### Added

- **`Healthie.NET`**, the package to install first. It carries no code of its own, only a dependency
on `Healthie.NET.DependencyInjection`, so it is one install and one dependency rather than a
bundle -- no provider, scheduler or UI framework arrives with it. The name people guess did not
exist before, and the actual entry point was called `DependencyInjection`, which reads like
plumbing rather than the way in.
- **Uptime reporting and leader election are in the core package.** `AddHealthieUptime()` and
`AddHealthieLeaderElection()` need nothing else installed. Both stay opt-in: nothing runs until
you call them.

### Deprecated

- **`Healthie.NET.Uptime`** and **`Healthie.NET.LeaderElection`**. Neither carried a third-party
dependency, so keeping them separate cost two installs and saved nothing -- the provider packages
exist to keep Npgsql or Temporalio off machines that do not use them, and these two were not
providers.

**Nothing breaks.** Both packages are still published, now as assemblies of type forwards, so an
application that references either keeps compiling *and* keeps running untouched. That is what
makes this a minor release: moving a type between assemblies is a binary break the compiler cannot
see, because source keeps building and only the runtime finds out. Remove the reference whenever it
suits you; neither package will gain features.

### Fixed

- **The sample Dockerfiles took their .NET base images by mutable tag.** A tag is a different image
next week, so the build that passed review is not the build that ships. Both are pinned by digest,
which Dependabot updates the way it updates a package version. Closes four OpenSSF Scorecard
*Pinned-Dependencies* findings.

### Security

- **An Azure CosmosDB key committed in May 2025 was confirmed dead and the alert closed.** It had
already been removed from the working tree; the account it belonged to no longer exists in the
owning tenant, verified by enumerating every Cosmos account across that tenant's subscriptions, so
the key authenticates to nothing. It remains in history at `ee0c78e`, inert.
- **Stray screenshots can no longer be committed.** Root-level PNGs are ignored, scoped to the root
so the images the docs and samples genuinely ship are untouched.

Full changelog: https://github.com/ivanvyd/Healthie.NET/blob/v4.1.0/CHANGELOG.md