Skip to content

Conversation

steveny91
Copy link
Contributor

Hostnames that start with ip or domu are automatically skipped in favor of other hostnames even if they're set in the datadog.yaml or DD_HOSTNAME environment variable.

https://github.com/DataDog/datadog-agent/blob/master/docs/agent/hostname_force_config_as_canonical.md

What does this PR do?

Add a small caveat to the logic that the agent uses to decide on a canonical hostname

Motivation

An escalation pointed that the logic was flawed and that names with ip-* was getting passed over even though they were manually set.

Preview

https://docs.datadoghq.com/agent/faq/how-datadog-agent-determines-the-hostname/?tab=agentv6v7#potential-host-names

Reviewer checklist

  • Review the changed files.
  • Review the URLs listed in the Preview section.
  • Review any mentions of "Contact Datadog support" for internal support documentation.

Hostnames that start with ip or domu are automatically skipped in favor of other hostnames even if they're set in the datadog.yaml or DD_HOSTNAME environment variable.  

https://github.com/DataDog/datadog-agent/blob/master/docs/agent/hostname_force_config_as_canonical.md
@steveny91 steveny91 requested a review from a team as a code owner March 8, 2021 23:57
@github-actions github-actions bot added agent Content changed in the Agent folder FAQ Content impacting a FAQ labels Mar 8, 2021
@apigirl apigirl merged commit 2334c43 into master Mar 9, 2021
@apigirl apigirl deleted the steveny91-hostname-logic branch March 9, 2021 13:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
agent Content changed in the Agent folder FAQ Content impacting a FAQ
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants