-
Notifications
You must be signed in to change notification settings - Fork 224
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
[Linux] Fix system-probe enablement conditions #336
Conversation
e040d77
to
da83266
Compare
Once modification is complete, follow the steps below: | ||
**Note**: This configuration works with Agent 6.24.1+ and 7.24.1+. For older Agent versions, refer to [the public documentation][8] on how to enable system-probe. | ||
|
||
On Linux, once this modification is complete, follow the steps below if you installed an Agent version older than 6.18.0 or 7.18.0: |
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.
Added this because on later versions, this should not be needed since the datadog-agent-sysprobe
service is tied to the datadog-agent
service.
Another option would be to automate these steps, but I'm not sure it's worth spending time on it given that this only affects a small number of old versions.
What does this PR do?
Fixes the logic around starting / stopping the system-probe service, with different paths depending on the Agent version:
datadog-agent-sysprobe
service is independent from thedatadog-agent
service and is started / stopped / restarted by the role, depending on thesystem_probe_config.enabled
variabledatadog-agent-sysprobe
service depends ondatadog-agent
, therefore only the datadog-agent service needs to be restarted on configuration changes. Thesystem_probe_config.enabled
variable still defines that behavior.network_config.enabled
variable defines if the service should be started or not. Thesystem_probe_config.enabled
variable is still supported for backwards compatibility, but is not recommended in the documentation anymore.Makes sure the role doesn't crash when
system_probe_config
has aNone
or empty value.Additional notes
TODO: update documentation on how to enable system-probe modules depending on the Agent version (link to the public docs).