Healthie.NET.Temporal
4.1.0
Prefix Reserved
dotnet add package Healthie.NET.Temporal --version 4.1.0
NuGet\Install-Package Healthie.NET.Temporal -Version 4.1.0
<PackageReference Include="Healthie.NET.Temporal" Version="4.1.0" />
<PackageVersion Include="Healthie.NET.Temporal" Version="4.1.0" />
<PackageReference Include="Healthie.NET.Temporal" />
paket add Healthie.NET.Temporal --version 4.1.0
#r "nuget: Healthie.NET.Temporal, 4.1.0"
#:package Healthie.NET.Temporal@4.1.0
#addin nuget:?package=Healthie.NET.Temporal&version=4.1.0
#tool nuget:?package=Healthie.NET.Temporal&version=4.1.0
Healthie.NET.Temporal
▶ 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.
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.0)
- Temporalio (>= 1.17.0)
-
net8.0
- Healthie.NET.Abstractions (>= 4.1.0)
- Temporalio (>= 1.17.0)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
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