I am following this discussion with lot of interest. I don't really know how the python module that convert the config files in the dictionary internal representation, but I currently have some though about plugin Shinken with other tools. The more obvious use case I see (and I'm interested in) is to be able to plug Shinken with a CMDB like tool to automatically generate probe definition from what is configured in architecture referential. Change the definition in the central database, and monitoring tools (and even other tools) automatically adapt to it.
I know such kind of thing is already done with GLPI with the help of a module but there is currently no way to "easily" plug to another tool. I see 3 ways it can be done :
1/ One develop a module that will plug into shinken and will after startup add all necessary host/services extracted from the given external tool. It may be the more robust, but need developing skills and knowing Shinken's internal to add even a simple connexion
2/ Completely externally to shinken (a bit like centreon works), the external tools generate a nagios like config file that is then read by Shinken. More standard format like json or xml may help in this direction
3/ Introducting python code directly into config file may be a mid point between those two ones : in the config file, a small fonction is written that query the external tool and merge the adequate config into the config file
My own point is that I don't sufficiently know Shinken's internal (for now) to develop a module even for very simple case and is sticked to solution 2 that I don't really like because of all the hassle with file generation when multiples sources are required.
I planned to learn in a few month how Shinken load config files and work an a module for my particular needs, but if it can be used in the standard Shinken release it's even better ! I will be glad to help if there is no hurry to implement this feature.