This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C275EA.CE1AB8D0
Content-Type: text/plain;
charset="iso-8859-1"
> As I've mentioned before, I would like to kill off the DB support (as
> it current stands) in Nagios 2.0. This includes MySQL/PostgresQL
> support for the following data types:
>
> - status data
> - retention data
> - comments
> - downtime
> - extended info
I've actually been hoping to see *more* stuff go into the database. I
haven't brought it up on this list yet because I don't have anything to
show, but I would like to tie the work I'm doing with GNU Radar somehow into
nagios, and having it in a DB seems like the easiest way to do that.
Radar originally had two purposes:
1) Replace HP Openview =)
2) Create an automated documentation tool for plain-English documentation.
The goal was to clean-room all of it, so that copyright could be assigned to
the FSF. I've come to realise that I hate ASN.1, and also Nagios seems to
now have all of the monitoring / display features I wanted to write. So
I've modified my attack plan slightly:
I'd like to add Layer 2 display/analysis to Nagios (such that can come up
with a physical description of the network, with how switches are connected
to one another, etc...), and I'd like to add the automated documentation
features. In many cases, it would be appropriate to have some of these
functions sit on remote nodes, connected by a management vlan/network/etc
which would require remote access to the information.
Incidentally, I have several hours a day to spend on this, as it's one of my
tasks for work.
I feel like I'm back in a debate class where I should now say "I now stand
open for cross-examination" =)
Tks,
Jeff Bailey
------_=_NextPart_001_01C275EA.CE1AB8D0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
RE: [Nagios-devel] Database Support in Nagios 2.0
> As I've mentioned before, I would like to kill =
off the DB support (as
> it current stands) in Nagios 2.0. This =
includes MySQL/PostgresQL
> support for the following data types:
>
> - status =
data
> - retention =
data
> - =
comments
> - =
downtime
> - extended =
info
I've actually been hoping to see *more* stuff go into =
the database. I haven't brought it up on this list yet because I =
don't have anything to show, but I would like to tie the work I'm doing =
with GNU Radar somehow into nagios, and having it in a DB seems like =
the easiest way to do that.
Radar originally had two purposes:
1) Replace HP Openview =3D)
2) Create an automated documentation tool for =
plain-English documentation.
The goal was to clean-room all of it, so that =
copyright could be assigned to the FSF. I've come to realise that =
I hate ASN.1, and also Nagios seems to now have all of the monitoring / =
display features I wanted to write. So I've modified my attack =
plan slightly:
I'd like to add Layer 2 display/analysis to Nagios =
(such that can come up with a physical description of the network, =
with how switches are connected to one another, etc...), and I'd =
like to add the automated documentation fe
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: Jeff.Bailey@fundserv.com