Pandora FMS Community

Configure Historical data parameter from configuration file or plugins

dstoian · 16 ene 2017, 21:44 · 4 mensajes · 63 visitas

  1. Inicio del debate

    Good evening, I have a hard time configuring "Historical data" parameter using the agent configuration file or custom plugins. This is very handy when thousand modules needs to be configured and just for a limited number of modules historical data it's needed. I know there are workaround with Policy and Bulk editing of modules but this is just additional work, especially for free version without Policy support. The API cand retrieve parameter module_history_data along with "get module_properties". It can also set this parameter when using "set create_plugin_module". But if configuration files are automatically generated with CHEF and then the agents are installed automatically module_history_data it's not working. You need an additional API call to disable this parameter. Examples not working: In configuration file module_begin module_name Docker_service module_group Application module_type generic_proc module_exec /etc/init.d/docker status | grep process | wc -l module_description Docker service status module_history_data 0 module_end In ruby plugins:   puts "n"   puts "n"   puts "n"   puts "n"   puts "n"   puts "n"   puts "n"   puts "n"   puts "n"   puts "n"   puts "n"   puts "n"   puts "n"   puts "n"   puts "n"   puts "n"   puts "n"   puts "n"   puts "n"   puts "n"   puts "n"   puts "n" Is this parameter usable in this way, or can only be configure via API, bulk editing, Policies? Thank you very much.

  2. No one trying to set up the history right from the config file ?

  3. Hello Antonio, It's clear now. Thank you very much.

Entra en tu cuenta para publicar.