NetEvolve.HealthChecks.Azure.Tables 3.4.112

.NET 6.0 This package targets .NET 6.0. The package is compatible with this framework or higher.
There is a newer version of this package available.
See the version list below for details. 
dotnet add package NetEvolve.HealthChecks.Azure.Tables --version 3.4.112                

                    
                

            
NuGet\Install-Package NetEvolve.HealthChecks.Azure.Tables -Version 3.4.112
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="NetEvolve.HealthChecks.Azure.Tables" Version="3.4.112" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
paket add NetEvolve.HealthChecks.Azure.Tables --version 3.4.112                

                    
                

            
#r "nuget: NetEvolve.HealthChecks.Azure.Tables, 3.4.112"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
// Install NetEvolve.HealthChecks.Azure.Tables as a Cake Addin
#addin nuget:?package=NetEvolve.HealthChecks.Azure.Tables&version=3.4.112

// Install NetEvolve.HealthChecks.Azure.Tables as a Cake Tool
#tool nuget:?package=NetEvolve.HealthChecks.Azure.Tables&version=3.4.112

NetEvolve.HealthChecks.Azure.Tables

Nuget Nuget

This package provides a health check for Azure Tables, based on the Azure.Storage.Tables package. The main purpose is to check that the Azure Table Service is reachable and that the client can connect to it.

💡 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.Azure.Tables

Health Check - Azure Table Client Availability

The health check is a liveness check. It will check that the Azure Table Service is reachable and that the client can connect to it. If the service needs longer than the configured timeout to respond, the health check will return Degraded. If the service is not reachable, the health check will return Unhealthy.

Usage

After adding the package, yo need to import the namespace NetEvolve.HealthChecks.Azure.Tables and add the health check to the service collection.

using NetEvolve.HealthChecks.Azure.Tables;

Therefor 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 tags azure, storage and blob 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. Therefor you have to add the configuration section HealthChecks:AzureTableClient to your appsettings.json file.

var builder = services.AddHealthChecks();

builder.AddAzureTableClint("<name>");

The configuration looks like this:

{
  ..., // other configuration
  "HealthChecks": {
    "AzureTableClient": {
      "<name>": {
        "ConnectionString": "<connection-string>", // required
        "ContainerName": "<container-name>", // required
        ..., // other configuration
        "Timeout": "<timeout>" // optional, default is 100 milliseconds
      }
    }
  }
}

Variant 2: Options based

The second one is to use the options based approach. Therefor you have to create an instance of AzureTableClientOptions and provide the configuration.

var builder = services.AddHealthChecks();

builder.AddAzureTableClient("<name>", options =>
{
    options.ConnectionString = "<connection-string>";
    options.ContainerName = "<container-name>";
    ...
    options.Timeout = "<timeout>";
});

💡 You can always provide tags to all health checks, for grouping or filtering.

var builder = services.AddHealthChecks();
    builder.AddKafka("<name>", options => ..., "azure");
Product Compatible and additional computed target framework versions.
.NET net6.0 is compatible.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 is compatible.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  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. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

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.0.1 75 11/4/2024
4.0.0 74 11/3/2024
3.4.139 96 9/12/2024
3.4.112 102 8/26/2024
3.4.52 99 6/24/2024
3.4.20 99 6/4/2024
3.4.0 97 5/23/2024
3.3.0 108 5/22/2024

https://github.com/dailydevops/healthchecks/releases/