-
Notifications
You must be signed in to change notification settings - Fork 260
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
[trace-agent] Leave the default enabled/disabled behavior to the agent #433
[trace-agent] Leave the default enabled/disabled behavior to the agent #433
Conversation
Since agent 5.13.0, the trace agent is enabled by default. This cookbook should allow explicitly enabling or disabling the trace agent, however, when the attribute that controls this is not set, the cookbook should leave it to the agent to decide whether to run the trace agent. This change modifies the default value of an attribute. Technically this is a breaking change that requires a major version bump of the cookbook, however I think this change actually improves backward compatibility and can go with a minor version of the cookbook.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense.
Makes sense. <% if node['datadog']['enable_trace_agent'].is_a?(TrueClass) || node['datadog']['enable_trace_agent'].is_a?(FalseClass) -%>
apm_enabled: <%= node['datadog']['enable_trace_agent'] ? 'true' : 'false' %>
<% end -%> |
Unless specified by the user, all the conf values of the trace-agent should be left to their defaults and the trace-agent should choose its own defaults, not the present cookbook. Custom settings will be applied even if the trace agent is not explicitly enabled.
@ed-flanagan Thanks for your feedback! The one thing I disliked about setting the I've pushed a commit that changes that behavior and implements what you suggested, let me know what you think |
Totally agree. If |
Thanks @ed-flanagan, merging this then! |
Since agent 5.13.0, the trace agent is enabled by default.
This cookbook should allow explicitly enabling or disabling the trace
agent, however, when the attribute that controls this is not set, the
cookbook should leave it to the agent to decide whether to run the
trace agent.
This change modifies the default value of an attribute. Technically
this is a breaking change that requires a major version bump of the
cookbook, however I think this change actually improves backward
compatibility and can go with a minor version of the cookbook.
Follow-up to #428, cc @ed-flanagan