LiteX.HealthChecks.AzureStorage.Queue
1.0.0
AzureQueueStorage health checks package used to check the status of a Azure Queue storage service in ASP.NET Core applications.
Based on new Microsoft Health Checks feature included in ASP.NET Core 2.2.
LiteXHealthChecks is very small yet powerful and high-performance library used to check the status of a component in the application, such as a backend service, database or some internal state.
See the version list below for details.
Install-Package LiteX.HealthChecks.AzureStorage.Queue -Version 1.0.0
dotnet add package LiteX.HealthChecks.AzureStorage.Queue --version 1.0.0
<PackageReference Include="LiteX.HealthChecks.AzureStorage.Queue" Version="1.0.0" />
paket add LiteX.HealthChecks.AzureStorage.Queue --version 1.0.0
LiteX HealthChecks Azure Queue storage
AzureQueueStorage health checks package used to check the status of a Azure Queue storage service in ASP.NET Core applications.
LiteXHealthChecks is very small yet powerful and high-performance library used to check the status of a component in the application, such as a backend service, database or some internal state.
Basic Usage
Install the package
Install via Nuget.
PM> Install-Package LiteX.HealthChecks.AzureStorage.Queue
AppSettings
{
"Data": {
"ConnectionStrings": {
"AzureQueueStorage": "--REPLACE WITH YOUR CONNECTION STRING--"
}
}
}
Configure Startup Class
public class Startup
{
public IConfiguration Configuration { get; }
public Startup(IConfiguration configuration)
{
Configuration = configuration;
}
public void ConfigureServices(IServiceCollection services)
{
// 1: Use default configuration
services.AddHealthChecks()
.AddAzureQueueStorage(Configuration["Data:ConnectionStrings:AzureQueueStorage"]);
// OR
// 2: With all optional configuration
services.AddHealthChecks()
.AddAzureQueueStorage(
connectionString: Configuration["Data:ConnectionStrings:AzureQueueStorage"],
name: "azure-queue-storage",
failureStatus: HealthStatus.Degraded,
tags: new string[] { "azure", "storage", "queue", "azure-queue-storage" });
}
public void Configure(IApplicationBuilder app, IHostingEnvironment env)
{
app.UseHealthChecks("/health");
}
}
Sample Usage Example
Sample for other services.
For more helpful information about LiteX HealthChecks, Please click here.
LiteX HealthChecks Azure Queue storage
AzureQueueStorage health checks package used to check the status of a Azure Queue storage service in ASP.NET Core applications.
LiteXHealthChecks is very small yet powerful and high-performance library used to check the status of a component in the application, such as a backend service, database or some internal state.
Basic Usage
Install the package
Install via Nuget.
PM> Install-Package LiteX.HealthChecks.AzureStorage.Queue
AppSettings
{
"Data": {
"ConnectionStrings": {
"AzureQueueStorage": "--REPLACE WITH YOUR CONNECTION STRING--"
}
}
}
Configure Startup Class
public class Startup
{
public IConfiguration Configuration { get; }
public Startup(IConfiguration configuration)
{
Configuration = configuration;
}
public void ConfigureServices(IServiceCollection services)
{
// 1: Use default configuration
services.AddHealthChecks()
.AddAzureQueueStorage(Configuration["Data:ConnectionStrings:AzureQueueStorage"]);
// OR
// 2: With all optional configuration
services.AddHealthChecks()
.AddAzureQueueStorage(
connectionString: Configuration["Data:ConnectionStrings:AzureQueueStorage"],
name: "azure-queue-storage",
failureStatus: HealthStatus.Degraded,
tags: new string[] { "azure", "storage", "queue", "azure-queue-storage" });
}
public void Configure(IApplicationBuilder app, IHostingEnvironment env)
{
app.UseHealthChecks("/health");
}
}
Sample Usage Example
Sample for other services.
For more helpful information about LiteX HealthChecks, Please click here.
Release Notes
AzureQueueStorage health check, which can be used to check the status of a Azure Queue storage service in the ASP.NET Core application.
Dependencies
-
.NETStandard 2.0
- Microsoft.Azure.Storage.Queue (>= 9.4.2)
- Microsoft.Extensions.Diagnostics.HealthChecks (>= 2.2.0)
GitHub Usage
This package is not used by any popular GitHub repositories.