Summary of problem
Hi,
We've upgraded some of our services to use dd-trace-py 1.8.0 recently and they all log the following warning:
Agent is down or Remote Config is not enabled in the Agent
Check your Agent version, you need an Agent running on 7.39.1 version or above.
Check Your Remote Config environment variables on your Agent:
DD_REMOTE_CONFIGURATION_ENABLED=true
DD_REMOTE_CONFIGURATION_KEY=
See: https://app.datadoghq.com/organization-settings/remote-config
We are running agent 7.40.1 and tried upgrading to 7.43.0 but that didn't help. We don't have the variables quoted set on the agent, but I could not find any reference to those or to remote configuration in the configuration template file, or the Helm chart variables.
I've read some blog posts and it appears remote configuration is a new future, possibly not globally available yet?
What are we suppose to do? How do we create a "remote configuration key"?
Alternatively, would setting DD_REMOTE_CONFIGURATION_ENABLED=false on pods remove the warning? (we would rather silence it without adding an extra environment variable on all pods, of course)
Which version of dd-trace-py are you using?
1.8.0
Which version of pip are you using?
Depends, but probably not relevant.
Which libraries and their versions are you using?
Idem.
How can we reproduce your problem?
It looks like a standard agent deployment using the Helm chart 3.3.1 (or 3.11.0) without any additional configuration related tor emote configuration + a standard dd-trace-py 1.8.0 will raise the warning.
What is the result that you get?
The warning is a bit cryptic as the variables mentioned are not document anywhere. Besides the process of enabling remote config on the agent isn't documented either - or I missed it. Maybe because it is still in beta? But then why would dd-trace raise a warning?
Thanks! :)
Summary of problem
Hi,
We've upgraded some of our services to use dd-trace-py 1.8.0 recently and they all log the following warning:
We are running agent 7.40.1 and tried upgrading to 7.43.0 but that didn't help. We don't have the variables quoted set on the agent, but I could not find any reference to those or to remote configuration in the configuration template file, or the Helm chart variables.
I've read some blog posts and it appears remote configuration is a new future, possibly not globally available yet?
What are we suppose to do? How do we create a "remote configuration key"?
Alternatively, would setting
DD_REMOTE_CONFIGURATION_ENABLED=falseon pods remove the warning? (we would rather silence it without adding an extra environment variable on all pods, of course)Which version of dd-trace-py are you using?
1.8.0
Which version of pip are you using?
Depends, but probably not relevant.
Which libraries and their versions are you using?
Idem.
How can we reproduce your problem?
It looks like a standard agent deployment using the Helm chart 3.3.1 (or 3.11.0) without any additional configuration related tor emote configuration + a standard dd-trace-py 1.8.0 will raise the warning.
What is the result that you get?
The warning is a bit cryptic as the variables mentioned are not document anywhere. Besides the process of enabling remote config on the agent isn't documented either - or I missed it. Maybe because it is still in beta? But then why would dd-trace raise a warning?
Thanks! :)