NetEvolve.HealthChecks.Azure.Blobs
3.4.139
See the version list below for details.
dotnet add package NetEvolve.HealthChecks.Azure.Blobs --version 3.4.139
NuGet\Install-Package NetEvolve.HealthChecks.Azure.Blobs -Version 3.4.139
<PackageReference Include="NetEvolve.HealthChecks.Azure.Blobs" Version="3.4.139" />
paket add NetEvolve.HealthChecks.Azure.Blobs --version 3.4.139
#r "nuget: NetEvolve.HealthChecks.Azure.Blobs, 3.4.139"
// Install NetEvolve.HealthChecks.Azure.Blobs as a Cake Addin #addin nuget:?package=NetEvolve.HealthChecks.Azure.Blobs&version=3.4.139 // Install NetEvolve.HealthChecks.Azure.Blobs as a Cake Tool #tool nuget:?package=NetEvolve.HealthChecks.Azure.Blobs&version=3.4.139
NetEvolve.HealthChecks.Azure.Blobs
This package provides a health check for Azure Blobs, based on the Azure.Storage.Blobs package. The main purpose is to check that the Azure Blob Service and the Storage Container 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.Blobs
Health Check - Azure Blob Container Availability
The health check is a liveness check. It will check that the Azure Blob Service and the Storage Container is reachable and that the client can connect to it. If the service or the container needs longer than the configured timeout to respond, the health check will return Degraded
. If the service or the container is not reachable, the health check will return Unhealthy
.
Usage
After adding the package, yo need to import the namespace NetEvolve.HealthChecks.Azure.Blobs
and add the health check to the service collection.
using NetEvolve.HealthChecks.Azure.Blobs;
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 tagsazure
,storage
andblob
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:AzureBlobContainer
to your appsettings.json
file.
var builder = services.AddHealthChecks();
builder.AddAzureBlobContainer("<name>");
The configuration looks like this:
{
..., // other configuration
"HealthChecks": {
"AzureBlobContainer": {
"<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 AzureBlobContainerOptions
and provide the configuration.
var builder = services.AddHealthChecks();
builder.AddAzureBlobContainer("<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 | Versions 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. |
-
net6.0
- Azure.Identity (>= 1.12.0)
- Azure.Storage.Blobs (>= 12.21.2)
- NetEvolve.Arguments (>= 1.2.100)
- NetEvolve.Extensions.Tasks (>= 1.2.98)
- NetEvolve.HealthChecks.Abstractions (>= 3.4.139)
-
net7.0
- Azure.Identity (>= 1.12.0)
- Azure.Storage.Blobs (>= 12.21.2)
- NetEvolve.Arguments (>= 1.2.100)
- NetEvolve.Extensions.Tasks (>= 1.2.98)
- NetEvolve.HealthChecks.Abstractions (>= 3.4.139)
-
net8.0
- Azure.Identity (>= 1.12.0)
- Azure.Storage.Blobs (>= 12.21.2)
- NetEvolve.Arguments (>= 1.2.100)
- NetEvolve.Extensions.Tasks (>= 1.2.98)
- NetEvolve.HealthChecks.Abstractions (>= 3.4.139)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.