You are not logged in.
By default, command names defined in flat-files (/etc/shinken) and in Monitoring (GLPI plugin) are in conflict.
To make both working together, I had to:
Edit nagios.cfg to comment "commands.cfg" and "packs", and add a new "commands-basic_for_glpi.cfg":
#GLPI#cfg_file=commands.cfg
cfg_file=commands-basic_for_glpi.cfg
[…]
#GLPI#cfg_dir=packs
Create commands-basic_for_glpi.cfg so that it simply contains a definition for "notify-service-by-email" (copied from "commands.cfg") because those shipped by Monitoring are named "notify-service-by-email-perl" and "notify-service-by-email-py" (as shown in "glpi_plugin_monitoring_notificationcommands" MySQL table; I don’t know if/where they are modifiable in GLPI)
Note: It would be simpler to rename the "notify-service-by-email-perl" to "notify-service-by-email" in notificationcommands! After all, "notify-host-by-email" is already named properly and it's a Perl script.
Versions used:
- GLPI 0.83.3
- Monitoring plugin 0.83+1.0
- shinken-arbiter : 1.0.1 with pyro : 3.12
Last edited by mathieu.md (2012-07-26 20:45:17)
Offline
You can change name in DB
I would like offer possibility to propose perl or python
Offline
You can change name in DB
Of course, but it's not my point
I would like offer possibility to propose perl or python
But you could still propose the perl as default (like Shinken does, ie. "notify-service-by-email") and offer the Python alternative through a custom command name ("notify-service-by-email-py").
That way, Shinken configuration from flat files is still compatible and usable with commands got from Monitoring.
Offline
You're right, I will fix that
Offline
Except if we prefer to have "glpi_" prefixed commands for those shipped by Monitoring ;-)
Offline