Healthie.NET.Checkers 4.1.2

Prefix Reserved

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

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

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.2" />

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.2" />
                    

                            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.2

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

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

#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.2

#: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.2
                    

                            Install as a Cake Addin

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

                            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 — board.healthie-dotnet.dev — a read-only Healthie.NET dashboard watching real status pages (Anthropic, OpenAI, GitHub, Cloudflare, and more), built from these packages. Full documentation at healthie-dotnet.dev.

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.2)
- Microsoft.Extensions.Http (>= 10.0.11)
net8.0
- Healthie.NET.Abstractions (>= 4.1.2)
- Microsoft.Extensions.Http (>= 10.0.11)

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.2	63	9/12/2026
4.1.1	253	8/14/2026
4.1.0	124	7/30/2026
4.0.0	106	7/30/2026

### Fixed

- The dashboard event-log and about dialogs now move focus inside, keep keyboard focus contained,
close with Escape, and restore focus to the control that opened them.
- Dashboard checker rows now expose selection as a real button alongside their action buttons,
removing nested interactive controls while preserving whole-row pointer selection.
- A dashboard state-provider failure now shows a recoverable unavailable state with a retry action
instead of looking like an empty installation with no registered checkers.
- The Blazor sample now keeps the dashboard stylesheet in its static host head, preventing an
unstyled flash while the interactive head reconnects on a slow network.
- HTTP checker display names and result messages now omit URI user information, query strings, and
fragments, server-controlled reason phrases, and transport exception details, preventing embedded
credentials and tokens from reaching stored history, alerts, logs, or the dashboard while requests
still use the complete configured URI.
- Alert-history persistence now loads durable history before its first post-restart write and
coalesces changes raised during a slow state-provider write into one latest-state follow-up. This
preserves earlier alerts without duplicating the new one and avoids an unbounded queue of tasks
and redundant full-history writes during alert bursts.
- The Web API sample maps its unauthenticated management API and mutation-enabled MCP endpoint only
in Development, so deploying the sample with a production environment no longer exposes those
local demonstration surfaces. Liveness and readiness probes remain available.
- History clearing and startup trimming now use optimistic concurrency, so they no longer overwrite
a check result or setting changed by another replica between the read and write.
- Leader election now serializes schedule changes with leadership transitions and reconciles every
registered checker's persisted active state and schedule through a bulk read on lease renewal. A
pause or cadence change made through another replica now reaches the leader, a fresh leader
removes inactive durable jobs left by the previous process, and reconciliation runs with bounded
concurrency while an independent lease heartbeat prevents slow scheduler calls from expiring an
otherwise healthy leader. Partial and cancelled transitions remain tracked until cleanup succeeds,
and shutdown does not release the lease over work it could not stop.
- CosmosDB multi-state reads now use `ReadManyItemsAsync`, avoiding one sequential network round
trip per checker during dashboard loads and leader renewal.
- The in-memory lease provider now returns exactly one winner when replicas contend concurrently.
- Coravel, Hangfire, Temporal, and the leader-election decorator now validate schedules before they
are persisted. Cronos expressions requiring an absent jitter seed are reported as validation
failures instead of escaping as server errors. The built-in timer also rejects periods outside
`PeriodicTimer`'s supported range before replacing a working schedule.
- Temporal now preserves Healthie.NET's six-field, leading-seconds cron meaning by translating it
to Temporal's seven-field seconds form. It rejects Cronos-only relative-day and descending-range
expressions whose Temporal meaning differs, and fixed periods outside Temporal's supported range,
before an existing schedule is removed.
- Uptime recording now starts a new observation segment on the first fresh result after a process
restart, even when its health matches persisted state. Time while no process was observing the
checker remains unknown, and a transition that finds the bounded queue full is retried by the next
fresh result.

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