Health Check extension 🔗

The health_check extension allows you to enable an HTTP URL that can be probed to check the status of the OpenTelemetry Collector. This extension can be used as a liveness or readiness probe on Kubernetes.

Get started 🔗

The following settings are required to configure the extension:

endpoint. Address to publish the health check status. 0.0.0.0:13133 by default.
path. Path to be configured for the health check server. "/" by default.
response_body. The static body that overrides the default response returned by the health check service. "" by default.
enabled. Whether to enable the Collector pipeline check or not. false by default.
interval. Time interval to check the number of failures. 5m by default.
exporter_failure_threshold. The failure number threshold to mark containers as healthy. 5 by default.

Check the Collector’s pipeline 🔗

Optionally, you can use the configuration parameter check_collector_pipeline to enable Health Check for the Collector pipelines. If activated, you can monitor the number of times that components failed to send data to their destination.

Note that it only supports exporter failures, but not receivers or processors.

Sample configuration 🔗

This is a sample configuration for the extension:

extensions:
  health_check:
  health_check/1:
    endpoint: "localhost:13"
    tls:
      ca_file: "/path/to/ca.crt"
      cert_file: "/path/to/cert.crt"
      key_file: "/path/to/key.key"
    path: "/health/status"
    check_collector_pipeline:
      enabled: true
      interval: "5m"
      exporter_failure_threshold: 5

Detailed sample configuration 🔗

This is a detailed configuration example:

health_check:
health_check/1:
  endpoint: "localhost:13"
  tls:
    ca_file: "/path/to/ca"
    key_file: "/path/to/key"
    cert_file: "/path/to/cert"
  check_collector_pipeline:
    enabled: false
    interval: "5m"
    exporter_failure_threshold: 5
health_check/missingendpoint:
  endpoint: ""
  check_collector_pipeline:
    enabled: false
    interval: "5m"
    exporter_failure_threshold: 5
health_check/invalidthreshold:
  endpoint: "localhost:13"
  check_collector_pipeline:
    enabled: false
    interval: "5m"
    exporter_failure_threshold: -1
health_check/invalidpath:
  endpoint: "localhost:13"
  path: "invalid"
  check_collector_pipeline:
    enabled: false
    interval: "5m"
    exporter_failure_threshold: 5

Settings 🔗

The following table shows the configuration options for the health_check extension:

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

Submit a case in the Splunk Support Portal .
Call Splunk Customer Support .

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 .

Related Topics