Docs » Available host and application monitors » Configure application receivers for hosts and servers » Chrony NTP

Chrony NTP 🔗

The Splunk Distribution of 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:

  • View metrics. You can create your own custom dashboards, and most monitors provide built-in dashboards as well. For information about dashboards, see View dashboards in Observability Cloud.

  • View a data-driven visualization of the physical servers, virtual machines, AWS instances, and other resources in your environment that are visible to Infrastructure Monitoring. For information about navigators, see Splunk Infrastructure Monitoring navigators.

  • Access the Metric Finder and search for metrics sent by the monitor. For information, see Use the Metric Finder.

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:

    type: collectd/chrony
    ...  # Additional config

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

     receivers: [smartagent/chrony]

Configuration options 🔗

The following table shows the configuration options for this integration:








The hostname of the chronyd instance.




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



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 not able to see your data in Splunk Observability Cloud, try these tips:

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