Docs » Supported integrations in Splunk Observability Cloud » Configure application receivers for hosts and servers » Health Checker

Health Checker πŸ”—

The Splunk Distribution of OpenTelemetry Collector uses the Smart Agent receiver with the Health Checker monitor type to check whether the configured JSON value is returned in the response body.

Benefits πŸ”—

After you configure the integration, you can access these features:

Installation πŸ”—

Follow these steps to deploy this integration:

  1. Deploy the Splunk Distribution of OpenTelemetry Collector to your host or container platform:

  2. Configure the monitor, as described in the Configuration section.

  3. Restart the Splunk Distribution of OpenTelemetry Collector.

Configuration πŸ”—

To use this integration of a Smart Agent monitor with the Collector:

  1. Include the Smart Agent receiver in your configuration file.

  2. Add the monitor type to the Collector configuration, both in the receiver and pipelines sections.

### Example

To activate this integration, add the following to your Collector configuration:

receivers:
  smartagent/health-checker:
    type: collectd/health-checker
    ...  # Additional config

Next, add the monitor to the service.pipelines.metrics.receivers section of your configuration file:

service:
 pipelines:
   metrics:
     receivers: [smartagent/health-checker]

Configuration settings πŸ”—

The following table shows the configuration options for the Health Checker monitor:

Option

Required

Type

Description

pythonBinary

no

string

Path to a python binary that should be used to execute the

Python code. If not set, a built-in runtime will be used. Can include arguments to the binary as well.

host

yes

string

port

yes

integer

name

no

string

path

no

string

The HTTP path that contains a JSON document to verify

(default: /)

jsonKey

no

string

If jsonKey and jsonVal are given, the given endpoint

will be interpreted as a JSON document and will be expected to contain the given key and value for the service to be considered healthy.

jsonVal

no

any

This can be either a string or numeric type

useHTTPS

no

bool

If true, the endpoint will be connected to on HTTPS instead

of plain HTTP. It is invalid to specify this if tcpCheck is true. (default: false)

skipSecurity

no

bool

If true, and useHTTPS is true, the server’s SSL/TLS

cert will not be verified. (default: false)

tcpCheck

no

bool

If true, the plugin will verify that it can connect to the

given host/port value. JSON checking is not supported. (default: false)

Metrics πŸ”—

The following metrics are available for this integration:

Name

Description

Sample value

Category

gauge.service.health.status

The HTTP response status code for the request made to the

application being monitored. A 200 value means an HTTP 200 OK success status response was returned, so the application is healthy.

200

Default

gauge.service.health.value

0 means an unhealthy state, and 1 means a healthy state.

0 or 1

Default

Notes πŸ”—

  • To learn more about the available in Observability Cloud see Metric types

  • In host-based subscription plans, default metrics are those metrics included in host-based subscriptions in Observability Cloud, such as host, container, or bundled metrics. Custom metrics are not provided by default and might be subject to charges. See Metric categories for more information.

  • In MTS-based subscription plans, all metrics are custom.

  • To add additional metrics, see how to configure extraMetrics in Add additional metrics

Troubleshooting πŸ”—

If you are a Splunk Observability Cloud customer and are not able to see your data in Splunk Observability Cloud, you can get help in the following ways.

Available to Splunk Observability Cloud customers

Available to prospective customers and free trial users

  • Ask a question and get answers through community support at Splunk Answers .

  • Join the Splunk #observability user group Slack channel to communicate with customers, partners, and Splunk employees worldwide. To join, see Chat groups in the Get Started with Splunk Community manual.

To learn about even more support options, see Splunk Customer Success .