Is someone working on the nagat idea moving forward of changes being made=
=20
through the new front end ?
And overall I like the status screens of nagios now. especially since Eth=
an=20
added in the ability to change the colors for acknowledged alerts.
I will pony up to doing the auth session sections but I am also not a gre=
at gui=20
designer. I am more a database and backend type person.
Derrick
Quoting Mark Musone :
> Is there anybody willing to volunteer on making a front end for the new
> php based nagios?
>=20
> All I need is an html UI and I can do the programing around it. I just
> need somebody to do the general design, and I can fill In the rest..
> Any ideas? Other known products to copy their UI??..should it be tabbed
> on top, what catagories, ..etc..
>=20
> Thanks,
>=20
> Mark
>=20
>=20
> -----Original Message-----
> From: nagios-devel-admin@lists.sourceforge.net
> [mailto:nagios-devel-admin@lists.sourceforge.net] On Behalf Of Ethan
> Galstad
> Sent: Tuesday, April 15, 2003 12:21 AM
> To: nagios-devel@lists.sourceforge.net
> Subject: RE: [Nagios-devel] nagios php interface version 0.01
>=20
> You'll have to grab the code from CVS. Its not documented anywhere,=20
> but the format is fairly straightforward and its working. =20
>=20
> Once Nagios is running, take a look at the status file, along with=20
> the comment and downtime files. The status file I/O routines can be=20
> found in xdata/xsddefault.c and should be fairly clear. The comment=20
> and downtime routines are found in xdata/xcddefault.c and=20
> xdata/xdddefault.c, respectively. The status/comment/downtime data=20
> is now stored in a stanzad format, similar to object definitions. =20
>=20
> The cached object file contains standard object definitions in=20
> stanzad format. The only difference from the "raw" object config=20
> files is that they've already been resolved. Also, each possible=20
> directive/value for each definition type is included in the cached=20
> definitions.
>=20
> Note: You'll have to move contact_group directives from your=20
> hostgroup definition to host definitions before you can start Nagios -
> this was the only real change to the format of object definitions in=20
> 2.0.
>=20
>=20
> On 14 Apr 2003 at 22:12, Mark Musone wrote:
>=20
> > So basically all of the "flattening" I did in php is not needed :^P
> :^)
> >=20
> > Where can I get the details about the formats for 2.0 ???
> > Or is it non-existant currently? Should I just look at the CVS
> > Code to determine the formats?
> >=20
> >=20
> > -Mark
> >=20
> >=20
> > -----Original Message-----
> > From: nagios-devel-admin@lists.sourceforge.net
> > [mailto:nagios-devel-admin@lists.sourceforge.net] On Behalf Of Ethan
> > Galstad
> > Sent: Monday, April 14, 2003 9:22 PM
> > To: nagios-devel@lists.sourceforge.net
> > Subject: Re: [Nagios-devel] nagios php interface version 0.01
> >=20
> > Since you've taken the leap on a big project, I'll throw in a few=20
> > comments.
> >=20
> > I would plan on developing this to work with 2.0, rather than 1.0. =20
> > The format of the status, comment, and downtime files have changed in=
=20
> > 2.0.=20
> >=20
> > Also, 2.0 has a cached object file (var/objects.cache by default)=20
> > that is created after Nagios starts. It contains a "flattened" view=20
> > of all object definitions that were present when Nagios started. All=
=20
> > definitions have already been resolved, replicated, and all the fancy=
=20
> > tricks are applied before this file gets created. This makes it very=
=20
> > easy for external apps (like the PHP interface) to parse the config=20
> > without having to worry about changes in how Nagios parses the raw=20
> > object definition files.
> >=20
> > Lastly, I personally believe that many of the current CGIs are=20
> > horrendous, so I wouldn't be too worried about replicating their look=
=20
> > and feel exactly. I think moving to a PHP interface would be a good=20
> > time to evaluate some different interface designs before anything is=20
> > nailed
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: code@novageeks.org