NetEvolve.HealthChecks.Npgsql 3.4.52

.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.Npgsql --version 3.4.52                

                    
                

            
NuGet\Install-Package NetEvolve.HealthChecks.Npgsql -Version 3.4.52
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.Npgsql" Version="3.4.52" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
paket add NetEvolve.HealthChecks.Npgsql --version 3.4.52                

                    
                

            
#r "nuget: NetEvolve.HealthChecks.Npgsql, 3.4.52"
#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.Npgsql as a Cake Addin
#addin nuget:?package=NetEvolve.HealthChecks.Npgsql&version=3.4.52

// Install NetEvolve.HealthChecks.Npgsql as a Cake Tool
#tool nuget:?package=NetEvolve.HealthChecks.Npgsql&version=3.4.52

NetEvolve.HealthChecks.Npgsql

Nuget Nuget

This package provides a health check for Npgsql databases, based on the Npgsql package. The main purpose is to check if the Npgsql database is available and if the database is online.

💡 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.Npgsql

Health Check - Npgsql Liveness

The health check is a liveness check. It checks if the Npgsql database 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 NetEvolve.HealthChecks.Npgsql and add the health check to the service collection.

using NetEvolve.HealthChecks.Npgsql;

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 postgresql and database 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 SQL Server instances to check.

var builder = services.AddHealthChecks();

builder.AddPostgreSql("<name>");

The configuration looks like this:

{
  ..., // other configuration
  "HealthChecks": {
    "PostgreSql": {
      "<name>": {
        "ConnectionString": "<connection string>",
        "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 SQL Server instance to check or dynamic programmatic values.

var builder = services.AddHealthChecks();

builder.AddPostgreSql("<name>", options =>
{
    options.ConnectionString = "<connection string>";
    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.AddPostgreSql("<name>", options => ..., "postgresql", "database");
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.67 40 11/29/2024
4.0.1 84 11/4/2024
4.0.0 78 11/3/2024
3.4.139 105 9/12/2024
3.4.112 97 8/26/2024
3.4.52 98 6/24/2024
3.4.20 103 6/4/2024
3.4.0 100 5/23/2024
3.3.0 113 5/22/2024
3.2.52 108 5/22/2024
3.2.31 112 5/21/2024
3.2.9 121 4/8/2024
3.2.0 125 4/4/2024
3.1.10 119 2/18/2024
3.1.8 126 2/16/2024
3.1.0 119 2/15/2024
3.0.0 133 2/14/2024
2.1.42 188 1/4/2024
2.1.31 127 1/3/2024
2.1.10 150 12/29/2023
2.1.2 161 11/27/2023
2.0.65 139 11/23/2023
2.0.64 125 11/21/2023
2.0.52 143 11/21/2023
2.0.51 131 11/20/2023
2.0.42 135 11/17/2023
2.0.0 149 10/9/2023
1.1.2 140 9/11/2023
1.1.1 150 9/11/2023

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