Open rarodriguez94 opened 5 months ago
Hey @rarodriguez94 thanks for reaching out and apologies for taking this long to answer!
So this error happens because the datadog agent deployed on your setup is either outdated (and thus it did not have the remote configuration feature) or has remote configuration explicitly disabled.
If it's the former (an outdated agent), we do recommend looking into updating it :)
You can make ddtrace not even try to hit this endpoint by setting the DD_REMOTE_CONFIGURATION_ENABLED=false
environment variable, or via code
Datadog.configure do |c|
# ... other config ...
c.remote.enabled = false
end
Let us know if this helps or if we can help in any other way!
Current behaviour
Expected behaviour
dd-trace should not throw an error when a instance is deployed. Will this cause an issue when gathering logs? Currently I see data is getting to datadog, but can't confirm if something is missing
Steps to reproduce
How does
datadog
help you?Environment
Datadog.configure ...
):