Healthie.NET.Uptime 4.1.0

Prefix Reserved
There is a newer version of this package available.
See the version list below for details.
dotnet add package Healthie.NET.Uptime --version 4.1.0
                    
NuGet\Install-Package Healthie.NET.Uptime -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.Uptime" 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.Uptime" Version="4.1.0" />
                    
Directory.Packages.props
<PackageReference Include="Healthie.NET.Uptime" />
                    
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.Uptime --version 4.1.0
                    
#r "nuget: Healthie.NET.Uptime, 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.Uptime@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.Uptime&version=4.1.0
                    
Install as a Cake Addin
#tool nuget:?package=Healthie.NET.Uptime&version=4.1.0
                    
Install as a Cake Tool

Healthie.NET - Trust your uptime

Healthie.NET.Uptime

NuGet

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

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 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. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

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.4 99 9/30/2026
4.1.3 93 9/29/2026
4.1.2 117 9/12/2026
4.1.1 128 8/14/2026
4.1.0 128 7/30/2026
4.0.0 133 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