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

Keep bumping warning logs for reading process_agent_config.host_ips #5081

Open
athom opened this issue Mar 9, 2020 · 2 comments · May be fixed by #7694
Open

Keep bumping warning logs for reading process_agent_config.host_ips #5081

athom opened this issue Mar 9, 2020 · 2 comments · May be fixed by #7694
Labels
[deprecated] team/processes DEPRECATED: please use team/container-intake

Comments

@athom
Copy link

athom commented Mar 9, 2020

Output of the info page (if this is a bug)

2020-03-05 05:45:40 UTC | PROCESS | WARN | (pkg/config/viper.go:168 in GetStringSlice) | failed to get configuration value for key "process_agent_config.host_ips": unable to cast <nil> of type <nil> to []string

Describe what happened:
It keep bumping this message for a period of time.

Describe what you expected:
Do not be so noisy

Steps to reproduce the issue:
Run the agent, and observe the logs.

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

AWS ECS using datadog/agent:7-jmx

Additional infomation:
Search the word process_agent_config.host_ips, can find it only shows in the code,
don't see it in any config files. Maybe can clean up, or at least document it somewhere.

https://github.com/search?q=org%3ADataDog+process_agent_config&type=Code

@KSerrania KSerrania added the [deprecated] team/processes DEPRECATED: please use team/container-intake label Mar 12, 2020
@mgrecar
Copy link

mgrecar commented Jan 20, 2021

I'm seeing this, too. Running on AWS EKS, seems to occur once during Helm deployments. I assume this is just noise due to deployments disrupting things?

@grv231
Copy link

grv231 commented Feb 12, 2021

Same, I started noticing it as well when I redeployed the agent, similar to what @mgrecar mentioned. Although it's a warning, I was hoping if there is some config change needed on the DD agent deployment. For me, it's happening on EKS, not ECS.

Update - It's coming randomly now, it has been hours since I redeployed the agent on EKS cluster

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[deprecated] team/processes DEPRECATED: please use team/container-intake
Projects
None yet
4 participants