Chrony receiver π
The Chrony receiver is a pure Go implementation of the command chronyc tracking
which allows portability across systems and platforms. The receiver produces all of the metrics that would typically be captured by the tracking command.
For more information about Chrony, see Red Hatβs Chrony suite documentation .
Get started π
Follow these steps to configure and activate the component:
Deploy the Splunk Distribution of the OpenTelemetry Collector to your host or container platform:
Configure the Chrony receiver as described in the next section.
Restart the Collector.
Default configuration π
To activate the receiver, add chrony
to the receivers
section of your configuration file:
receivers:
chrony/defaults:
endpoint: unix:///var/run/chrony/chronyd.sock # The default port by chronyd to allow cmd access
timeout: 10s # Allowing at least 10s for chronyd to respond before giving up
Next, include the receiver in the metrics
pipeline of the service
section of your configuration file:
service:
pipelines:
metrics:
receivers:
- chrony
Advanced configuration π
You can use the following settings:
endpoint
. Required. The address wherechrony
communicates to. Allowed formats are:udp://hostname:port
unixgram:///path/to/chrony/sock
unix:///path/to/chrony.sock - Note the triple slash. Unix is converted to unixgram.
timeout
. Optional. The total amount of time allowed to read and process the data from chronyd. Use at least 1 second.collection_interval
. Optional. Determines how often to query Chrony.initial_delay
. Optional.1s
by default. Defines how long this receiver waits before starting. See more in Red Hatβs Chrony suite documentation .metrics
. Optional. Metrics to export. See the metric documentation in GitHub .
Configuration example π
See the following configuration example:
receivers:
chrony:
endpoint: unix:///var/run/chrony/chronyd.sock
timeout: 10s
collection_interval: 30s
metrics:
ntp.skew:
enabled: true
ntp.stratum:
enabled: true
Settings π
The following table shows the configuration options for the Chrony receiver:
Metrics π
The following metrics, resource attributes, and attributes, are available.
See also the metric documentation in GitHub .
Activate or deactivate specific metrics π
You can activate or deactivate specific metrics by setting the enabled
field in the metrics
section for each metric. For example:
receivers:
samplereceiver:
metrics:
metric-one:
enabled: true
metric-two:
enabled: false
The following is an example of host metrics receiver configuration with activated metrics:
receivers:
hostmetrics:
scrapers:
process:
metrics:
process.cpu.utilization:
enabled: true
Note
Deactivated metrics arenβt sent to Splunk Observability Cloud.
Billing π
If youβre in a MTS-based subscription, all metrics count towards metrics usage.
If youβre in a host-based plan, metrics listed as active (Active: Yes) on this document are considered default and are included free of charge.
Learn more at Infrastructure Monitoring subscription usage (Host and metric plans).
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 .
Contact Splunk 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.