NetEvolve.HealthChecks.OpenSearch 5.8.0

NetEvolve.HealthChecks.OpenSearch

This package provides a health check for OpenSearch services, based on the OpenSearch.Client package. The main purpose is to check if the server is available and the service is online.

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

Health Check - OpenSearch Liveness

The health check is a liveness check. It checks if the OpenSearch Server is available and if the service 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 and add the health check to the health check builder.

using NetEvolve.HealthChecks.OpenSearch;

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 tags opensearch and searchengine 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 OpenSearch instances to check.

var builder = services.AddHealthChecks();

builder.AddOpenSearch("<name>");

The configuration looks like this:

{
  ..., // other configuration
  "HealthChecks": {
    "OpenSearch": {
      "<name>": {
        "Mode": "<client_creation_mode>", // Optional, defaults to 'OpenSearchClientCreationMode.ServiceProvider'
        "KeyedService": "<key>", // Optional, used when Mode set to 'OpenSearchClientCreationMode.ServiceProvider'
        "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 only have one server instance to check or dynamic programmatic values.

var builder = services.AddHealthChecks();

builder.AddOpenSearch("<name>", options =>
{
    options.Mode = <client_creation_mode>; // Optional, defaults to 'OpenSearchClientCreationMode.ServiceProvider'
    options.KeyedService = "<key>"; // Optional, used when Mode set to 'OpenSearchClientCreationMode.ServiceProvider'
    options.Username = "<username>"; // Used when Mode set to 'OpenSearchClientCreationMode.UsernameAndPassword' and required when Password is set
    options.Password = "<password>"; // Used when Mode set to 'OpenSearchClientCreationMode.UsernameAndPassword' and required when Username is set
    options.Timeout = <timeout>; // Optional, defaults to 100 milliseconds
    
    foreach (var connectionString in connectionStrings) {
        options.ConnectionStrings.Add(connectionString); // Required when Mode set to 'OpenSearchClientCreationMode.UsernameAndPassword'
    }

    // Optional, defaults to NetEvolve.HealthChecks.OpenSearch.DefaultCommandAsync
    options.CommandAsync = async (client, cancellationToken) =>
    {
        // Your custom server pinging logic here.
        // Should return true if the command result is valid, false otherwise.
    };
});

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

var builder = services.AddHealthChecks();

builder.AddOpenSearch("<name>", options => ..., "OpenSearch", "opensearch");

License

This project is licensed under the MIT License - see the LICENSE file for details.