You can have an import from a GLPI webinterface for your hosts.

For people that don’t know GLPI, it’s a web app to manage all IT equipment like servers, routers, printers or anything you want for that matter. It’s also a help-desk tool. You can fill using tools like FusionInventory for example.

You can still have flat files AND GLPI if you want. Such GLPI hosts will be treated as standard hosts from flat file (inheritance, groups, etc). In fact in this first version the module only take the host_name from it, but there should be more informations extracted like network connexions for parents relations in the future :)

In your shinken-specific.cfg file, just add (or uncomment) :

#You know GLPI? You can load all configuration from this app(
#with the webservices plugins for GLPI, in xmlrpc mode
#and with plugin monitoring for GLPI)
# =============== Work with Plugin Monitoring of GLPI ===============
#All configuration read from this will be added to the others of the
#standard flat file
define module{
     module_name      GLPI
     module_type      glpi
     uri              http://localhost/glpi/plugins/webservices/xmlrpc.php
     login_name       glpi
     login_password   glpi
}

And add it in your Arbiter object as a module.

define arbiter{
     arbiter_name     Arbiter-Master
#    host_name       node1       ;result of the hostname command under Unix
     address          localhost                   ;IP or DNS adress
     port             7770
     spare            0
     modules           GLPI
     }

It's done :)