Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

If dd-agent starts before cluster agent, cluster name returns empty #24406

Open
harold-kfuse opened this issue Apr 4, 2024 · 0 comments · May be fixed by #24544
Open

If dd-agent starts before cluster agent, cluster name returns empty #24406

harold-kfuse opened this issue Apr 4, 2024 · 0 comments · May be fixed by #24544

Comments

@harold-kfuse
Copy link

Agent Environment

I deployed datadog on an EKS cluster using Datadog 3.59.4 helm chart. It has agent/cluster version of 7.52.0

Describe what happened:

Cluster name returns empty

Describe what you expected:

kube_cluster_name should be detected

Steps to reproduce the issue:

Additional environment details (Operating System, Cloud provider, etc):

I did a little digging on the code base. I think it's due to this line:

It sets initDone to true, regardless if the clustername detection succeeded. Is it better to set it to true only after it has actually succeeded. I'm assuming that if initDone is not true, the Dd-agent will retry.

I enabled debug logging and I saw that the detection fails because the agent was not able to talk to the cluster agent. This can happen, since helm install deploys both the agent and cluster agent at the same time and cluster agent may not have started before the agent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant