Healthie.NET.Checkers
4.1.1
Prefix Reserved
dotnet add package Healthie.NET.Checkers --version 4.1.1
NuGet\Install-Package Healthie.NET.Checkers -Version 4.1.1
<PackageReference Include="Healthie.NET.Checkers" Version="4.1.1" />
<PackageVersion Include="Healthie.NET.Checkers" Version="4.1.1" />
<PackageReference Include="Healthie.NET.Checkers" />
paket add Healthie.NET.Checkers --version 4.1.1
#r "nuget: Healthie.NET.Checkers, 4.1.1"
#:package Healthie.NET.Checkers@4.1.1
#addin nuget:?package=Healthie.NET.Checkers&version=4.1.1
#tool nuget:?package=Healthie.NET.Checkers&version=4.1.1
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 | Versions 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. |
-
net10.0
- Healthie.NET.Abstractions (>= 4.1.1)
- Microsoft.Extensions.Http (>= 10.0.11)
-
net8.0
- Healthie.NET.Abstractions (>= 4.1.1)
- 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.
### Fixed
- **The dashboard cropped its own rows on anything narrower than a laptop.** The row and its column
header share one track definition, and two rules overrode it: a read-only board drops the controls
column, and a narrow viewport folds the row down to three. Written as separate rule sets they
fought on specificity, and `.hpm-list--readonly .hpm-row` outranks a `.hpm-row` inside a media
query -- so on a read-only board the fold never applied at any width. Every row was drawn with
five tracks demanding 556px inside a 342px phone: 214px of columns clipped off the right, the name
squeezed to its 160px minimum to make room for columns that were not visible anyway, and no
scrollbar to reach them, because the overflow was clipped rather than scrolled. The definition is
now a single custom property on the list, which is the one element both variants already sit on,
so the fold cannot be outranked.
- **The last column was clipped on an ordinary 1280 laptop, read-only or not.** The detail panel
moved below the list at 1100px, but a full row needs a 706px column and the list only reaches that
at 1402px of viewport -- so between those two the three columns fitted the window while the middle
one no longer fitted a row. That threshold is now 1400px, calibrated on the editable board, which
is the wider of the two and the default.
- **Group and tag chips were sliced down the middle on a phone.** They sit on the row's sub-line,
which truncates with `text-overflow: ellipsis` -- and that ellipsizes text, not an inline-flex
pill, so a chip was cut mid-shape instead. The folded row has vertical room the wide one does not,
so the line now wraps there, exactly as it already does on a card.
- **Cards lost their rate, sparkline and last-checked time on a phone.** The three cells were hidden
for every layout below 820px, but only the row layout was short of width; a card stacks them into
areas down its own length, where they fit. They are now hidden for the row layout alone.
### Changed
- **The packages point at [healthie-dotnet.dev](https://healthie-dotnet.dev/).** `PackageProjectUrl`
is the landing site rather than the repository, because NuGet renders it as the package's "Project
website" and a reader who clicks it wants documentation and the live board, not a source tree.
`RepositoryUrl` still points at GitHub, so Source Link and NuGet's own source link are unaffected.
Every package README now links the documentation site alongside the live demo, which moved to
[board.healthie-dotnet.dev](https://board.healthie-dotnet.dev/).
- **Releases carry build provenance.** The release workflow attests which workflow, at which commit,
produced each package, so `gh attestation verify <package>.nupkg --repo ivanvyd/Healthie.NET`
proves a download came from this repository. The SBOM already said what went into a package; this
says who built it, which is the half a tampered build would otherwise be free to restate.
- The repository README leads with a screenshot rather than a 10MB animation, and `Healthie.NET.Redis`
gained the header every other package README already had.
Full changelog: https://github.com/ivanvyd/Healthie.NET/blob/v4.1.1/CHANGELOG.md