• English日本語한국어
  • ログイン今すぐ開始

Infrastructure agent configuration settings

The infrastructure agent has a large set of configuration settings to fine-tune its behavior. Here we:

  • List all the configuration options (in both their YAML and the environment variable names).
  • Explain what the settings do and when to use them.
  • Give the variable type and default value (if any).
  • List the minimum required agent version as applicable.

重要

With secrets management, you can configure the agent on-host integrations with infrastructure to use sensitive data (such as passwords) without having to write them as plain text into the integration's configuration file. For more information, see Secrets management.

まだNewRelicアカウントがありませんか?永久に無料でサインアップ します。

スタートガイド

You'll be able to configure our infrastructure agent to suit your environnment after you create a New Relic account (it's free, forever) and install the infrastructure agent.

The license_key is the only required setting.

For an example of how all these variables can be used, see our sample configuration template in GitHub.

Agent variables

Cloud variables

If the agent is running in a cloud instance, the agent will try to detect the cloud type and fetch basic metadata. Metrics can also be enriched with extended cloud metadata (including custom resource tags) when connecting the cloud provider account with New Relic.

Docker variables

File system variables

Hostname variables

Installation variables

Integrations variables

Inventory variables

Linux variables

変数のロギング

ヒント

Infrastructure agent version 1.28.0 introduced backward-compatible improvements in logging configuration. See our github documentation to understand the legacy settings and how to map them to the new structure.

Metrics variables

Plugins variables

ヒント

You can quickly disable all the variables by setting DisableAllPlugins to true, and turn on only those options you need.

Proxy variables

For infrastructure agent version 1.3.1 or higher, the precedence of the proxy configuration settings is:

  • NRIA_PROXY
  • proxy
  • HTTP_PROXY
  • HTTPS_PROXY

If you are having problems with proxy configuration, see Proxy troubleshooting.

Samples variables

NTP Offset variables

ntp_metrics is a key-value map used to configure the time offset metric. When enabled and an NTP Hosts list is provided, the agent will provide the host's ntp offset metric (in seconds). This value is checked against the provided NTP hosts pool every interval minutes (the default and the minumum value is 15 minutes). Between intervals, the last known offset is reported. If the reported offset is greater than few seconds it can cause issues with alert conditions, NRQL queries and data gaps in dashboards.

Example as a YAML attribute:

ntp_metrics:
enabled: true
pool:
- time.cloudflare.com
- time.google.com
interval: 15
timeout: 10

Example as an environment variable:

NRIA_NTP_METRICS_POOL='time.cloudflare.com,time.google.com'
NRIA_NTP_METRICS_ENABLED='true'
NRIA_NTP_METRICS_INTERVAL='15'
NRIA_NTP_METRICS_TIMEOUT='10'

Security variables

Status endpoint variables

Windows variables

HttpClient

Configure the HTTP client used for backend communication.

次のステップ

You can also:

Copyright © 2024 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.