To be able to answer this question we will divide it in two cases.
- Agent modules management.
For this, it is recommended the use of policies in the agent management (of the same S.O.) in which we want to introduce the same modules, plugins, alerts…
- Special parameters management of software agents.
For this case it will be necessary to have a better knowledge of the agents configuration file and it is recommended to do a previous backup of the /var/spool/pandora/data_in/conf and /var/spool/pandora/data_in/md5 folders.
To be able to make some changes, it would be necessary to execute a command in the /var/spool/pandora/data_in/conf folder (where the configuration files of the software agents with remote configuration are stored) of the style of
sed -i 's/xml_buffer 1/xml_buffer 0/g'
(with this command what we do is a change in the token xml_buffer), being the graphics of the command:
sed -i 's/text to search/text to change/g' directory
Once it has been done, it will be necessary to have a policy with all the agents involved where we apply a “dummy” module (that does not affect the monitoring, an echo 1 for example) so that Pandora FMS changes the .md5 of the agents and these ones know that they should collect their new configuration.
Once the change has been applied and seen that the agents have their new configuration, we can delete or undo or remove all the agents from the policy to remove the created module.