This one is a bit touchy but I think we can do crazy stuff : Use case : - tpl-1 with service-1-a, service-1-b - tpl-2 with service-2-a, service-2-b - host-A uses tpl-1 and tpl-2 - host-B uses tpl-1 and tpl-2 It would be great if we can do this in the host-A definition "service-2-a".retry_interval 4 "service-1-b".business_impact 5 This would change services properties in Host-A wihtout changing ...more »
I suggest exposing some configuration items to be modified via the WebUI.
- Correlation rules
- WebUI session options
- Hosts and their properties
- Services and their properties
Any changes need to be checked for validity prior to commiting to the configuration.
Any changes done to the configuration need to be consigned to an audit log.
In the nagios configuration files all the password are in clear text. It would be great to secure it especially when you use it via a web interface.
SourceForge interface is far from being intuitive. This can limit the popularity of the project.
Fusion inventory bridge
It can be good to get hosts/service info from a real inventory tools. And raise "problems" in a real helpdesk tool too.
I suggest you store the Shinken configuration in a SQL/noSQL back-end database, instead of current flat-files. Any configuration stored in the database should be exportable/importable to and from a strongly typed format files that are still readable. (JSON, YAML, etc.)
The basic: frontend configuration and mysql database store.
centreon isn't a good thing.
Like the module for VMWare, it would be a good idea to generate the dependencies between hypervisors and virtual machines for Open Source solutions like Xen / KVM.
For reporting, it an be cool to have the category of the alert (network, system, etc). So just add a information tag on services for it.
https://sourceforge.net/apps/trac/shinken/ticket/67 For users, they cannot open a port from the Arbiter to the satellites, because they are in the customer site, and the customer do not want someone to take the control of it's process. So the satellites must know how to get conf from the Arbiter if configured like it. Implementation : Instead of put_conf to socket, the Arbiter "put the conf" in memory, in standby mode, ...more »