Configuration in PandoraFMS
The executor is one-shot: it runs the template once and exits. Scheduling is external.
| Scenario | How |
|---|---|
| As an agent plugin | Template uses transfer.mode: agent_plugin; agent config: module_plugin /usr/bin/pandora-plugin_exec -t /etc/pandora/templates/df_used.yml |
| From cron / server side | Template uses tentacle or local mode; crontab: */5 * * * * pandora-plugin_exec -t /etc/pandora/templates/myapp.yml |
| Running on the Pandora FMS server itself | local mode pointed at the incoming data directory (/var/spool/pandora/data_in) |
| Debugging a template | pandora-plugin_exec -t template.yml --dry-run -v |
There is no wizard or .disco package for this plugin: installation means placing the binary (and templates) where the agent/cron can reach them, then wiring the module_plugin line or crontab entry shown above.