Healthie.NET.Temporal
4.1.1
Prefix Reserved
dotnet add package Healthie.NET.Temporal --version 4.1.1
NuGet\Install-Package Healthie.NET.Temporal -Version 4.1.1
<PackageReference Include="Healthie.NET.Temporal" Version="4.1.1" />
<PackageVersion Include="Healthie.NET.Temporal" Version="4.1.1" />
<PackageReference Include="Healthie.NET.Temporal" />
paket add Healthie.NET.Temporal --version 4.1.1
#r "nuget: Healthie.NET.Temporal, 4.1.1"
#:package Healthie.NET.Temporal@4.1.1
#addin nuget:?package=Healthie.NET.Temporal&version=4.1.1
#tool nuget:?package=Healthie.NET.Temporal&version=4.1.1
Healthie.NET.Temporal
▶ 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.
Schedules pulse checks with Temporal, so the schedule lives in the cluster rather than in the process.
Installation
dotnet add package Healthie.NET.Temporal
Usage
using Healthie.Scheduling.Temporal;
using Temporalio.Extensions.Hosting;
builder.Services.AddSingleton<ITemporalClient>(await TemporalClient.ConnectAsync(new("localhost:7233")));
builder.Services
.AddHealthie(typeof(Program).Assembly)
.AddHealthieTemporal(options => options.TaskQueue = "healthie");
// A worker must be listening on the same queue, or the schedules fire and nothing runs.
builder.Services
.AddHostedTemporalWorker("healthie")
.AddScopedActivities<PulseCheckerActivities>()
.AddWorkflow<PulseCheckerWorkflow>();
The Temporal client is yours to create: its address, namespace, TLS and API key are your decisions, and a library that picked them would be picking which cluster your workflows run on.
What it buys, and what it costs
Buys: the schedule survives a restart and a redeploy, each occurrence is handed to exactly one worker however many replicas are running, and every run has a history somebody can look at.
Costs: a Temporal cluster. If you do not already run one, this is the wrong trade — Healthie.NET.Hangfire gives you the same survives-a-restart, runs-once-across-replicas properties against a database you probably already have, and the built-in timer needs nothing at all.
The SDK also carries a native Rust core, so it is a large dependency: it adds a few hundred megabytes to a build output. Worth knowing before adding it to something small.
Details
Schedules are named healthie-<checker name>, so they are recognisable in the Temporal UI and cannot collide with your own.
Overlap policy is Skip. A checker already refuses to run on top of itself, so buffering would queue occurrences that each return immediately — and a check that is late is worth less than the next one, which is current.
Cron expressions pass through untranslated: Temporal parses standard Unix cron, the same syntax Healthie.NET uses. Fixed periods become interval specs, which Temporal counts from an epoch rather than from creation time, so replicas agree on when a schedule fires.
The workflow does nothing but call an activity — workflow code must be deterministic, and a pulse check is not — and the activity is given the checker's name, because a schedule outlives the process that created it and a checker does not survive being serialized.
Testing
The mapping from a schedule to a Temporal specification is unit-tested. Everything else needs a running cluster, so it is not exercised in the default test suite — that suite deliberately requires no infrastructure. Run it against a dev server (temporal server start-dev) when changing this package.
| 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 (>= 4.1.1)
- Temporalio (>= 1.18.0)
-
net8.0
- Healthie.NET.Abstractions (>= 4.1.1)
- Temporalio (>= 1.18.0)
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