Re: [Nagios-devel] XML Output
Posted: Fri Nov 15, 2002 6:20 am
Honestly, all I care about in the XML file is that I can read the data in a
consistent format. I'd even be happier if:
1) The CGI can take a parameter to show only information from a particular
hostgroup. (Which would allow NTray to be setup to monitor only particular
hostgroups for a user)
2) The CGI would be really cool if there was a flag to specify that we only
want to request host information for hosts/services that are in a non-okay
status. Saves me work
Making the CGI take the option makes it easy to
make it more multi-purpose for other neat things (like, maybe a script that
sits on another machine that is hooked up to a big readerboard in a call
center )
Frankly, my script will be ignoring all the XML header information and the
nuances of XML anyway. All I care about is something in a format that I can
read. Here's a simple example, but we've got lots of flexibility here. I
would suggest looking a little at the XML spec as 'sg' suggests
Critical
Scheduled
It's broken. We'll fix it later
Critical
ack'ed
We know about it
Critical
Scheduled,ProblemHost
Isn't exchange always down?
Critical
unscheduled
Warning
That is something simple that the XML::Simple perl module would suck
right into variables for me.
Rob
PS - Remember, I'm not a programmer by trade... I like easy shortcuts
Subhendu Ghosh
.org> cc: [email protected],
Subject: Re: [Nagios-devel] XML Output
11/14/2002
03:28 PM
Might want to take a quick look at how Ganglia.sf.net does XML -
relatively simple setup using XML to multicast host state information for
a cluster.
I'll try and write up a draft of the XML structure for discussion - It
might also be handy for for a few other things in v2/v3
-sg
On Wed, 13 Nov 2002, Ethan Galstad wrote:
> It has been mentioned by several people in the past that it would be
> helpful if there was a way of getting status information in XML
> format. NTray is one program that would benefit from this.
>
> The easiest solution at the moment would be to write a CGI that does
> this. However, I know very little about XML at the moment, so I need
> assistance from people in the know. Specifically, what should the
> output look like to make it easy to interpret?
>
> There are 3 types of entities that have status data:
>
> - Process status (1 entry)
> - Host status (Multiple entries)
> - Service status (Multiple entries)
>
> I suppose it would be nice to be able to get access to comment and
> downtime data in XML format as well, although that is less of a
> priority that status data.
>
> Comments? Suggestions?
>
>
>
> Ethan Galstad,
> Nagios Developer
> ---
> Email: [email protected]
> Website: http://www.nagios.org
>
--
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
consistent format. I'd even be happier if:
1) The CGI can take a parameter to show only information from a particular
hostgroup. (Which would allow NTray to be setup to monitor only particular
hostgroups for a user)
2) The CGI would be really cool if there was a flag to specify that we only
want to request host information for hosts/services that are in a non-okay
status. Saves me work
Making the CGI take the option makes it easy tomake it more multi-purpose for other neat things (like, maybe a script that
sits on another machine that is hooked up to a big readerboard in a call
center )
Frankly, my script will be ignoring all the XML header information and the
nuances of XML anyway. All I care about is something in a format that I can
read. Here's a simple example, but we've got lots of flexibility here. I
would suggest looking a little at the XML spec as 'sg' suggests
Critical
Scheduled
It's broken. We'll fix it later
Critical
ack'ed
We know about it
Critical
Scheduled,ProblemHost
Isn't exchange always down?
Critical
unscheduled
Warning
That is something simple that the XML::Simple perl module would suck
right into variables for me.
Rob
PS - Remember, I'm not a programmer by trade... I like easy shortcuts
Subhendu Ghosh
.org> cc: [email protected],
Subject: Re: [Nagios-devel] XML Output
11/14/2002
03:28 PM
Might want to take a quick look at how Ganglia.sf.net does XML -
relatively simple setup using XML to multicast host state information for
a cluster.
I'll try and write up a draft of the XML structure for discussion - It
might also be handy for for a few other things in v2/v3
-sg
On Wed, 13 Nov 2002, Ethan Galstad wrote:
> It has been mentioned by several people in the past that it would be
> helpful if there was a way of getting status information in XML
> format. NTray is one program that would benefit from this.
>
> The easiest solution at the moment would be to write a CGI that does
> this. However, I know very little about XML at the moment, so I need
> assistance from people in the know. Specifically, what should the
> output look like to make it easy to interpret?
>
> There are 3 types of entities that have status data:
>
> - Process status (1 entry)
> - Host status (Multiple entries)
> - Service status (Multiple entries)
>
> I suppose it would be nice to be able to get access to comment and
> downtime data in XML format as well, although that is less of a
> priority that status data.
>
> Comments? Suggestions?
>
>
>
> Ethan Galstad,
> Nagios Developer
> ---
> Email: [email protected]
> Website: http://www.nagios.org
>
--
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]