On Tuesday, 15 November 2011 19:24:44 Olivier AUDRY wrote:
Yes, I also want to biuld a sexy customer web 2.0 portal. Why should
everyone have to build their own ones, when we could at least cooperate
on the components, even if we don't cooperate on the actual portal.
Because we need to implement this regarding what is already existing in the
compagny.
For my exemple I need to link the portal with the cmdb, the KB, the
ticketing and the monitoring.
For exemple here is a few fonction I will use :
those are working :
get_group_by_host() to get the name of the group compress for an host
like database or application server etc. get_hosts_by_plids() to get
the hosts for a given plateform id
get_plids_by_customer() to get all the plateform id for one customer
get_hosts_by_customer() to get all the hosts for a customer. Should be
useless.
those will work :
get the country for an host
get the datacenter for an host
So this is specific to your CMDB.
get the test list for an host
This one still needs to be written, but I don't really want to duplicate configuration parsing code (and I believe Xymon should consider supporting multiple configuration backends, so a perl module here should really be an XS module for a library interfact).
get the status for a test for an hosts
My Xymon::Client should already give you this.
get the type and os for a device.
with this I think I can do something great.
Of course there will be information regarding a host outside Xymon, but the point is to have standard modules that support the Xymon aspects, that can be re-used by multiple projects.
Regards,
Buchan