Healthie.NET.AI
3.1.3
Prefix Reserved
See the version list below for details.
dotnet add package Healthie.NET.AI --version 3.1.3
NuGet\Install-Package Healthie.NET.AI -Version 3.1.3
<PackageReference Include="Healthie.NET.AI" Version="3.1.3" />
<PackageVersion Include="Healthie.NET.AI" Version="3.1.3" />
<PackageReference Include="Healthie.NET.AI" />
paket add Healthie.NET.AI --version 3.1.3
#r "nuget: Healthie.NET.AI, 3.1.3"
#:package Healthie.NET.AI@3.1.3
#addin nuget:?package=Healthie.NET.AI&version=3.1.3
#tool nuget:?package=Healthie.NET.AI&version=3.1.3
Healthie.NET.AI
Explains what a pulse checker's recent history shows: whether it is failing consistently or intermittently, when it started, and what the errors point to. Provider-agnostic -- it depends on Microsoft.Extensions.AI.Abstractions and nothing else, so the model is your choice.
Installation
dotnet add package Healthie.NET.AI
Usage
Register any IChatClient, then add the diagnostician:
using Healthie.AI;
// Anthropic, OpenAI, Azure OpenAI, or a local model via Ollama -- this package depends on none of them.
builder.Services.AddSingleton<IChatClient>(
new AnthropicClient().AsIChatClient("claude-opus-4-8"));
builder.Services.AddHealthieAI();
Then ask it about a checker:
var diagnosis = await diagnostician.DiagnoseAsync("MyApp.Pulses.DatabasePulseChecker");
Console.WriteLine(diagnosis.Summary);
Console.WriteLine($"Failure rate rose: {diagnosis.Anomaly.IsAnomalous}");
Key Types
| Type | Description |
|---|---|
IPulseDiagnostician |
DiagnoseAsync(name) returns a PulseDiagnosis for one checker. |
PulseDiagnosis |
The checker's Name, a plain-English Summary, and an Anomaly report. |
AnomalyReport |
IsAnomalous, RecentFailureRate, EarlierFailureRate. |
StartupExtensions.AddHealthieAI() |
Registers IPulseDiagnostician. Requires an IChatClient in DI. |
The Anomaly Report Is Not a Model Call
Anomaly compares the recent failure rate against the earlier one arithmetically, from the checker's own history. It is deterministic and testable, and it is worth trusting on its own -- including when no model is configured to write the summary.
What Leaves Your Process
Diagnosing a checker sends its name, its health, and the messages its checks reported to whichever model you configured. Those messages are written by your own checkers, which is a good reason to keep credentials out of check results. This package never mutates state.
You May Not Need This
If your only consumer is an AI agent, use Healthie.NET.Mcp instead: an agent talking to the MCP endpoint can read get_check_history and reason about it itself. This package is for the surfaces where there is no model in the loop -- a REST response, a dashboard, an alert.
See Also
| 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 (>= 3.1.3)
- Microsoft.Extensions.AI.Abstractions (>= 10.8.0)
-
net8.0
- Healthie.NET.Abstractions (>= 3.1.3)
- Microsoft.Extensions.AI.Abstractions (>= 10.8.0)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
### Changed
- The dashboard now scrolls within its own board rather than the page, so its scrollbar is themed to
match the board -- a thin, rounded bar in the board's own line colour, on both the dark and light
themes -- instead of the platform's wide light-grey default running down the side of a dark tool.
The board owns a full-viewport (`100dvh`) scroll region, and a scroll that reaches its end no
longer drags the page behind an embedded board.
### Fixed
- The prerendered dashboard no longer risks dropping its own circuit on a board with much state.
3.1.1 carried the states from prerender to the interactive render by persisting them into the
page, which put the whole board -- every checker and all its history -- on the SignalR circuit.
That payload grows with each checker, and past SignalR's default 32 KB message limit the hub
rejects it and the circuit never starts: the board freezes on the prerendered snapshot, styled but
not live. The states now stay on the server between the two renders (Blazor Server holds them there
already) and only a short-lived token travels to the browser and back, so the wire cost is constant
whatever the size of the board. A token that no longer resolves falls back to a fresh read. No
SignalR limit needs raising, so no extra memory or denial-of-service exposure comes with it.
### Fixed
- The dashboard no longer flickers on load when it is prerendered. Hosted the usual
way -- `<HealthieDashboard />` on an interactive-server page, which prerenders by
default -- the server rendered the full board, then the circuit connected a moment
later and the component started again from an empty state, read every checker afresh,
and briefly replaced the board already on screen. In that gap a status icon, which the
dashboard stylesheet sizes against its surroundings, painted for a frame before those
rules applied and filled the board as one large ring. The states the prerender reads
are now carried across to the interactive render through `PersistentComponentState`,
so the first interactive render matches the prerendered one: nothing is replaced, no
frame shows an unsized icon, and the redundant second read of every checker is gone.
Full changelog: https://github.com/ivanvyd/Healthie.NET/blob/v3.1.3/CHANGELOG.md