NetEvolve.HealthChecks.Dapr
4.1.23
dotnet add package NetEvolve.HealthChecks.Dapr --version 4.1.23
NuGet\Install-Package NetEvolve.HealthChecks.Dapr -Version 4.1.23
<PackageReference Include="NetEvolve.HealthChecks.Dapr" Version="4.1.23" />
paket add NetEvolve.HealthChecks.Dapr --version 4.1.23
#r "nuget: NetEvolve.HealthChecks.Dapr, 4.1.23"
// Install NetEvolve.HealthChecks.Dapr as a Cake Addin #addin nuget:?package=NetEvolve.HealthChecks.Dapr&version=4.1.23 // Install NetEvolve.HealthChecks.Dapr as a Cake Tool #tool nuget:?package=NetEvolve.HealthChecks.Dapr&version=4.1.23
NetEvolve.HealthChecks.Dapr
This package provides a health check for Dapr, based on the Dapr.Client package. The main purpose is to check if the Dapr is available and if the sidecar is available.
💡 This package is available for .NET 6.0 and later.
Installation
To use this package, you need to add the package to your project. You can do this by using the NuGet package manager or by using the dotnet CLI.
dotnet add package NetEvolve.HealthChecks.Dapr
Health Check - Dapr Liveness
The health check is a liveness check. It checks if the Dapr is available and if the database is online.
If the query needs longer than the configured timeout, the health check will return Degraded
.
If the query fails, for whatever reason, the health check will return Unhealthy
.
Usage
After adding the package, you need to import the namespace and add the health check to the health check builder.
using NetEvolve.HealthChecks.Dapr;
Therefor you can use two different approaches. In both approaches you have to provide a name for the health check.
Parameters
options
: The configuration options for the health check. If you don't provide any options, the health check will use the configuration based approach.tags
: The tags for the health check. The tagsDapr
anddatabase
are always used as default and combined with the user input. You can provide additional tags to group or filter the health checks.
Variant 1: Configuration based
The first one is to use the configuration based approach. This approach is recommended if you have multiple Dapr instances to check.
var builder = services.AddHealthChecks();
builder.AddDapr();
The configuration looks like this:
{
..., // other configuration
"HealthChecks": {
"DaprSidecar": {
"Timeout": "<timeout>" // optional, default is 100 milliseconds
}
}
}
Variant 2: Builder based
The second approach is to use the builder based approach. This approach is recommended if you have only one Dapr instance to check or dynamic programmatic values.
var builder = services.AddHealthChecks();
builder.AddDapr(options =>
{
options.Timeout = "<timeout>"; // optional, default is 100 milliseconds
});
💡 You can always provide tags to all health checks, for grouping or filtering.
var builder = services.AddHealthChecks();
builder.AddDapr(options => ..., "Dapr");
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 is compatible. |
-
net8.0
- Dapr.Client (>= 1.14.0)
- NetEvolve.Arguments (>= 1.3.0)
- NetEvolve.Extensions.Tasks (>= 1.3.0)
- NetEvolve.HealthChecks.Abstractions (>= 4.1.23)
-
net9.0
- Dapr.Client (>= 1.14.0)
- NetEvolve.Arguments (>= 1.3.0)
- NetEvolve.Extensions.Tasks (>= 1.3.0)
- NetEvolve.HealthChecks.Abstractions (>= 4.1.23)
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.23 | 79 | 12/19/2024 |
4.1.0 | 80 | 12/16/2024 |
4.0.67 | 86 | 11/29/2024 |
4.0.1 | 94 | 11/4/2024 |
4.0.0 | 85 | 11/3/2024 |
3.4.139 | 113 | 9/12/2024 |
3.4.112 | 106 | 8/26/2024 |
3.4.52 | 108 | 6/24/2024 |
3.4.20 | 102 | 6/4/2024 |
3.4.0 | 105 | 5/23/2024 |
3.3.0 | 116 | 5/22/2024 |
3.2.52 | 116 | 5/22/2024 |
3.2.31 | 112 | 5/21/2024 |
3.2.9 | 129 | 4/8/2024 |
3.2.0 | 104 | 4/4/2024 |
3.1.10 | 100 | 2/18/2024 |
3.1.8 | 103 | 2/16/2024 |
3.1.0 | 117 | 2/15/2024 |