Healthie.NET.CosmosDb 4.1.1

Prefix Reserved
dotnet add package Healthie.NET.CosmosDb --version 4.1.1
                    
NuGet\Install-Package Healthie.NET.CosmosDb -Version 4.1.1
                    
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.CosmosDb" Version="4.1.1" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Healthie.NET.CosmosDb" Version="4.1.1" />
                    
Directory.Packages.props
<PackageReference Include="Healthie.NET.CosmosDb" />
                    
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.CosmosDb --version 4.1.1
                    
#r "nuget: Healthie.NET.CosmosDb, 4.1.1"
                    
#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.CosmosDb@4.1.1
                    
#: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.CosmosDb&version=4.1.1
                    
Install as a Cake Addin
#tool nuget:?package=Healthie.NET.CosmosDb&version=4.1.1
                    
Install as a Cake Tool

Healthie.NET - Trust your uptime

Healthie.NET.CosmosDb

NuGet

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.

Azure CosmosDB IStateProvider implementation for Healthie.NET. Persists pulse checker state to CosmosDB for durable storage across application restarts and distributed environments.

Installation

dotnet add package Healthie.NET.CosmosDb

Usage

using Healthie.StateProviding.CosmosDb;
using Microsoft.Azure.Cosmos;

var cosmosClient = new CosmosClient("your-connection-string");

builder.Services
    .AddHealthie(typeof(Program).Assembly)
    .AddHealthieCosmosDb(cosmosClient, "your-database", "healthie-state");

The container is created on startup if it does not exist. The database is not, so create it yourself or point at an existing one.

If you would rather build the Container yourself, the original overload still works:

var container = cosmosClient.GetContainer("your-database", "healthie-state");

builder.Services
    .AddHealthie(typeof(Program).Assembly)
    .AddHealthieCosmosDb(container);

Important: The CosmosDB container must use /id as the partition key path. Startup fails with a clear error if an existing container is partitioned differently.

Key Types

Type Description
StartupExtensions.AddHealthieCosmosDb() Registers CosmosDbStateProvider as the singleton IStateProvider and CosmosDbStateProviderInitializer as an IStateProviderInitializer.
CosmosDbStateProvider Implements IStateProvider using CosmosDB ReadItemAsync / UpsertItemAsync.
CosmosDbStateProviderInitializer Creates the container on startup if it is missing and validates its partition key path.

How It Works

  • Each pulse checker's state is stored as a document with the checker's fully-qualified name as both the id and partition key.
  • GetStateAsync reads the document by id; returns default on 404 NotFound.
  • Each document records the assembly-qualified type of the state it holds, and reading it as a different type throws rather than returning a mismatched state. Documents written before the type was recorded carry no type and are read as-is.
  • SetStateAsync upserts the document, creating or replacing it atomically.

Concurrency

Writes can be made conditional. GetStateEntryAsync returns the state together with the document's ETag, and TrySetStateAsync sends it as If-Match, so a write made from a state that has since changed is refused (CosmosDB answers 412 PreconditionFailed) rather than silently overwriting whoever changed it. When nothing is stored yet there is no ETag to match, so the write becomes a create, which CosmosDB refuses a second time with 409 Conflict — the same guarantee at the one moment there is nothing to compare.

A refused write is reported as false, not thrown. Under contention losing is the expected outcome and the answer is always the same: read again, reapply, write again. StateProviderExtensions.UpdateStateAsync is that loop. Both writers go through it — the setting change and the check storing its result — which is what makes the guarantee hold in both directions: a check that read the state before a setting changed no longer writes the old setting back over it.

SetStateAsync still upserts unconditionally. It replaces a whole document with one the caller supplies, so there is no version to carry and nothing to compare — it is the escape hatch, not the path the library takes.

See Also

Back to main README

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.1 108 8/14/2026
4.1.0 99 7/30/2026
4.0.0 102 7/30/2026
3.1.4 106 7/19/2026
3.1.3 99 7/18/2026
3.1.2 100 7/18/2026
3.1.1 95 7/18/2026
3.1.0 103 7/17/2026
3.0.0 107 7/15/2026
2.3.0 140 2/24/2026
2.1.1-beta 120 2/24/2026
2.0.0-beta 120 2/22/2026
1.1.0-beta 134 5/31/2025
1.0.0-beta 206 5/18/2025

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