NetEvolve.HealthChecks.Azure.Kusto
5.0.0
Prefix Reserved
dotnet add package NetEvolve.HealthChecks.Azure.Kusto --version 5.0.0
NuGet\Install-Package NetEvolve.HealthChecks.Azure.Kusto -Version 5.0.0
<PackageReference Include="NetEvolve.HealthChecks.Azure.Kusto" Version="5.0.0" />
<PackageVersion Include="NetEvolve.HealthChecks.Azure.Kusto" Version="5.0.0" />
<PackageReference Include="NetEvolve.HealthChecks.Azure.Kusto" />
paket add NetEvolve.HealthChecks.Azure.Kusto --version 5.0.0
#r "nuget: NetEvolve.HealthChecks.Azure.Kusto, 5.0.0"
#:package NetEvolve.HealthChecks.Azure.Kusto@5.0.0
#addin nuget:?package=NetEvolve.HealthChecks.Azure.Kusto&version=5.0.0
#tool nuget:?package=NetEvolve.HealthChecks.Azure.Kusto&version=5.0.0
NetEvolve.HealthChecks.Azure.Kusto
This package provides a health check for Azure Kusto (Azure Data Explorer), based on the Microsoft.Azure.Kusto.Data package. The main purpose is to check that the Azure Kusto cluster is reachable and that the client can connect to it.
💡 This package is available for .NET 8.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.Azure.Kusto
Health Check - Azure Kusto Availability
The health check is a liveness check. It will check that the Azure Kusto cluster is reachable and that the client can connect to it. If the cluster needs longer than the configured timeout to respond, the health check will return Degraded. If the cluster is not reachable, the health check will return Unhealthy.
Usage
After adding the package, you need to import the namespace NetEvolve.HealthChecks.Azure.Kusto and add the health check to the service collection.
using NetEvolve.HealthChecks.Azure.Kusto;
Therefore, you can use two different approaches. In both approaches you have to provide a name for the health check.
Parameters
name: The name of the health check. The name is used to identify the configuration object. It is required and must be unique within the application.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 tagsazure,kustoandadxare 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. Therefore, you have to add the configuration section HealthChecks:AzureKusto to your appsettings.json file.
var builder = services.AddHealthChecks();
builder.AddKustoAvailability("<name>");
The configuration looks like this:
{
..., // other configuration
"HealthChecks": {
"AzureKusto": {
"<name>": {
"ConnectionString": "<connection-string>", // required (or ClusterUri)
"DatabaseName": "<database-name>", // optional
..., // other configuration
"Timeout": "<timeout>" // optional, default is 100 milliseconds
}
}
}
}
Variant 2: Options based
The second one is to use the options based approach. Therefore, you have to create an instance of KustoAvailableOptions and provide the configuration.
var builder = services.AddHealthChecks();
builder.AddKustoAvailability("<name>", options =>
{
options.ConnectionString = "<connection-string>";
options.DatabaseName = "<database-name>";
...
options.Timeout = "<timeout>";
});
💡 You can always provide tags to all health checks, for grouping or filtering.
var builder = services.AddHealthChecks();
builder.AddKustoAvailability("<name>", options => ..., "azure");
License
This project is licensed under the MIT License - see the LICENSE file for details.
| 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. 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
- Azure.Identity (>= 1.17.1)
- Microsoft.Azure.Kusto.Data (>= 14.0.2)
- NetEvolve.Extensions.Tasks (>= 1.3.74)
- Newtonsoft.Json (>= 13.0.4)
-
net8.0
- Azure.Identity (>= 1.17.1)
- Microsoft.Azure.Kusto.Data (>= 14.0.2)
- NetEvolve.Extensions.Tasks (>= 1.3.74)
- Newtonsoft.Json (>= 13.0.4)
-
net9.0
- Azure.Identity (>= 1.17.1)
- Microsoft.Azure.Kusto.Data (>= 14.0.2)
- NetEvolve.Extensions.Tasks (>= 1.3.74)
- Newtonsoft.Json (>= 13.0.4)
NuGet packages (1)
Showing the top 1 NuGet packages that depend on NetEvolve.HealthChecks.Azure.Kusto:
| Package | Downloads |
|---|---|
|
NetEvolve.HealthChecks.Azure
Contains HealthChecks for various Azure services. |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 5.0.0 | 0 | 11/20/2025 |