Healthie.NET.Uptime
4.1.1
Prefix Reserved
See the version list below for details.
dotnet add package Healthie.NET.Uptime --version 4.1.1
NuGet\Install-Package Healthie.NET.Uptime -Version 4.1.1
<PackageReference Include="Healthie.NET.Uptime" Version="4.1.1" />
<PackageVersion Include="Healthie.NET.Uptime" Version="4.1.1" />
<PackageReference Include="Healthie.NET.Uptime" />
paket add Healthie.NET.Uptime --version 4.1.1
#r "nuget: Healthie.NET.Uptime, 4.1.1"
#:package Healthie.NET.Uptime@4.1.1
#addin nuget:?package=Healthie.NET.Uptime&version=4.1.1
#tool nuget:?package=Healthie.NET.Uptime&version=4.1.1
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.1)
-
net8.0
- Healthie.NET.DependencyInjection (>= 4.1.1)
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