devops:monitoring:datadog:canonical_hostnames
Differences
This shows you the differences between two versions of the page.
| devops:monitoring:datadog:canonical_hostnames [2025/02/14 10:25] – created 85.219.17.206 | devops:monitoring:datadog:canonical_hostnames [2025/02/14 10:26] (current) – 85.219.17.206 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | How does Datadog determine the Agent hostname? | + | ====== |
| - | Docs > Agent > Agent FAQ > How does Datadog determine the Agent hostname? | + | |
| - | Potential host names | + | |
| + | ===== Potential host names ===== | ||
| The Datadog Agent collects potential host names from many different sources. Run the Agent’s status subcommand to see all names the Agent is detecting. | The Datadog Agent collects potential host names from many different sources. Run the Agent’s status subcommand to see all names the Agent is detecting. | ||
| - | ... | ||
| Hostnames | Hostnames | ||
| ========= | ========= | ||
| Line 15: | Line 16: | ||
| socket-hostname: | socket-hostname: | ||
| socket-fqdn: | socket-fqdn: | ||
| - | ... | + | |
| From these names, a canonical name is chosen for the host. The Agent uses this name to identify itself to Datadog. The other names are submitted as well, but only as candidates for aliasing. | From these names, a canonical name is chosen for the host. The Agent uses this name to identify itself to Datadog. The other names are submitted as well, but only as candidates for aliasing. | ||
devops/monitoring/datadog/canonical_hostnames.1739528740.txt.gz · Last modified: 2025/02/14 10:25 by 85.219.17.206