Healthie.NET.Uptime
4.1.2
Prefix Reserved
See the version list below for details.
dotnet add package Healthie.NET.Uptime --version 4.1.2
NuGet\Install-Package Healthie.NET.Uptime -Version 4.1.2
<PackageReference Include="Healthie.NET.Uptime" Version="4.1.2" />
<PackageVersion Include="Healthie.NET.Uptime" Version="4.1.2" />
<PackageReference Include="Healthie.NET.Uptime" />
paket add Healthie.NET.Uptime --version 4.1.2
#r "nuget: Healthie.NET.Uptime, 4.1.2"
#:package Healthie.NET.Uptime@4.1.2
#addin nuget:?package=Healthie.NET.Uptime&version=4.1.2
#tool nuget:?package=Healthie.NET.Uptime&version=4.1.2
Healthie.NET.Uptime
Deprecated as of 4.1.0
Uptime reporting now ships in Healthie.NET, the core package. Call
AddHealthieUptime()there and drop this reference — uptime over any window works exactly as it does here.Nothing breaks if you keep it. This package is still published, as an assembly of type forwards, so an application referencing it keeps compiling and running untouched. It carried no third-party dependency, so keeping it separate cost you an install and saved you nothing. It will not gain features.
▶ 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.
Answers "what was our uptime last quarter" — which the rolling history cannot, because it holds the last hundred results and for a one-second checker that is the last hundred seconds.
Installation
dotnet add package Healthie.NET.Uptime
Usage
using Healthie.Uptime;
builder.Services
.AddHealthie(typeof(Program).Assembly)
.AddHealthieUptime();
Then ask:
public sealed class SlaReport(IUptimeStore store)
{
public async Task<UptimeReport> LastQuarterAsync(string checkerName)
{
var to = DateTime.UtcNow;
var from = to.AddDays(-90);
var segments = await store.GetSegmentsAsync(checkerName, from, to);
return UptimeCalculator.Calculate(checkerName, segments, from, to);
}
}
report.UptimePercentage // 99.94
report.Met(99.9) // true
report.Unhealthy // 00:47:31
report.Unknown // 00:12:05 -- see below
It stores transitions, not checks
A checker running every second produces 86,400 results a day and perhaps four transitions. Both can answer "how long was it down", but only one is exact and only one is small enough to keep for a year.
That is also why this is a separate store from IStateProvider: state is one small document per checker, overwritten on every check; this is an append-only series read occasionally and kept for months. Putting them together would mean every check rewriting a document that grows for ever.
Unknown time is neither up nor down
Time when the application was not running is time nothing was watching.
Counting it as downtime would report an outage for every deployment. Counting it as uptime would claim a component was fine over a period nobody looked at it. So it is neither: it is reported separately as Unknown, and UptimePercentage is measured against observed time.
A checker that never ran has UptimePercentage == null rather than 0 or 100 — either number would be a claim about a period with no evidence.
Storage
InMemoryUptimeStore is the default, so uptime works out of the box. It does not survive a restart. Implement IUptimeStore and register it before or after AddHealthieUptime() — registration is order-independent, as with the state providers.
Recording cannot hurt a check. A store that is slow, remote or briefly unavailable is not the component being monitored, so transitions go through a bounded queue and are written on the recorder's own loop; a store that throws loses one transition rather than ending recording.
| 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.DependencyInjection (>= 4.1.2)
-
net8.0
- Healthie.NET.DependencyInjection (>= 4.1.2)
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 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