Docs » Supported integrations in Splunk Observability Cloud » Configure application receivers for hosts and servers » Chrony NTP (deprecated)

Chrony NTP (deprecated) πŸ”—

Caution

This integration is deprecated. If you’re using the Splunk Distribution of the OpenTelemetry Collector and want to monitor Chrony use the native OpenTelemetry component Chrony receiver instead.

The Splunk Distribution of the OpenTelemetry Collector uses the Smart Agent receiver with the Chrony NTP monitor type to monitor NTP data from a chrony server, such as clock skew and per-peer stratum. To talk to chronyd, this integration mimics what the chronyc control program does on the wire.

This integration is only available on Kubernetes and Linux.

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/chrony:
    type: collectd/chrony
    ...  # Additional config

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

service:
 pipelines:
   metrics:
     receivers: [smartagent/chrony]

Configuration options πŸ”—

The following table shows the configuration options for this integration:

Option

Required

Type

Description

host

yes

string

The hostname of the chronyd instance.

port

no

integer

The UDP port number of the chronyd instance. Defaults to 323 in

collectd if unspecified.

timeout

no

unsigned integer

How long to wait for a response from chronyd before considering

it down. Defaults to 2 seconds in the collectd plugin if not specified.

Metrics πŸ”—

The Splunk Distribution of OpenTelemetry Collector does not do any built-in filtering of metrics coming out of this integration. ## 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.

This page was last updated on Oct 23, 2024.