Type to search.

System ntp metricset

Serverless Beta

Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud.

Availability

  • Beta

    This functionality is in beta and is not ready for production usage. For beta features, the design and code is less mature than official GA features and is being provided as-is with no warranties. Beta features are not subject to the support SLA of official GA features. Specific Support terms apply.

Serverless interfaces and procedures might differ from classic Elastic Stack deployments.

Stack Beta 9.2+

The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats.

Availability

  • Beta since 9.2

    This functionality is in beta and is not ready for production usage. For beta features, the design and code is less mature than official GA features and is being provided as-is with no warranties. Beta features are not subject to the support SLA of official GA features. Specific Support terms apply.

Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments.

This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.

The System ntp metricset provides Network Time Protocol (NTP) metrics.

This metricset is available on:

  • FreeBSD
  • Linux
  • macOS
  • OpenBSD
  • Windows

Configuration

ntp.servers
Remote NTP server addresses of the form "host", "host:port", "host%zone:port", "[host]:port" or "[host%zone]:port". The server may contain an IPv4, IPv6, or domain name address. When specifying both a port and an IPv6 address, one of the bracket formats must be used. If no port is included, NTP default port 123 is used. If multiple servers are specified, metrics are reported separately for each. Defaults to ["pool.ntp.org"].
ntp.timeout
Timeout determines how long the client waits for a response from the remote server before failing with a timeout error. Defaults to 5 seconds.
ntp.version
Version of the NTP protocol to use. Must be one of "3" or "4". Defaults to "4".
ntp.validate
Whether to validate the NTP response if it is suitable for time synchronization purposes. If not, the response will be skipped. Must be one of "true" or "false". Defaults to "true".

Fields

For a description of each field in the metricset, see the exported fields section.

Here is an example document generated by this metricset:

JSON 
{
    "@timestamp": "2017-10-12T08:05:34.853Z",
    "agent": {
        "hostname": "host.example.com",
        "name": "host.example.com"
    },
    "event": {
        "dataset": "system.ntp",
        "duration": 115000,
        "module": "system"
    },
    "metricset": {
        "name": "ntp"
    },
    "service": {
        "type": "system"
    },
    "system": {
        "ntp": {
            "host": "0.pool.ntp.org",
            "offset": 127140000
        }
    }
}