[Nagios-devel] Front End Development

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
Locked
Guest

[Nagios-devel] Front End Development

Post by Guest »

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8C595.66BC718F
Content-Type: text/plain;charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I have tried searched high and low for documentation regarding the way a
Front End should communicate with Nagios 3.x ( even 2.x ), but with no
avail. If anyone has a site or a quick run down on where to start I
would appreciate it.=20

=20

=20

A side note, I started by simply parsing the Nagios log files for the
information I wanted, but decided that it may not be the correct way to
do it and have halted at that point to research some better alternatives
and methods.=20


This message is intended solely for the person or entity to which it is a=
ddressed and may contain confidential and/or privileged information.

Electronic information transmitted herein is not a guarantee of commitmen=
t whatsoever or is legally binding unless explicitly noted otherwise. Any=
review, dissemination, copying, printing or other use of this message =
by persons or entities other than the addressee is prohibited.

If you have received this message in error, please contact the sender imm=
ediately and destroy the material immediately.

------_=_NextPart_001_01C8C595.66BC718F
Content-Type: text/html;charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
















I have tried searched high and low for documentation
regarding the way a Front End should communicate with Nagios 3.x  ( =
even 2.x ),
but with no avail. If anyone has a site or a quick run down on where to s=
tart I
would appreciate it.

 

 

A side note, I started by simply parsing the Nagios lo=
g files
for the information I wanted, but decided that it may not be the correct =
way to
do it and have halted at that point to research some better alternatives =
and
methods.




This message is intended solely for the person or entity to which it =
is addressed and may contain confidential and/or privileged information.

Electronic information transmitted herein is not a guarantee of commitmen=
t whatsoever or is legally binding unless explicitly noted otherwise. Any=
review, dissemination, copying, printing or other use of this message =
by persons or entities other than the addressee is prohibited.

If you have received this message in error, please contact the sender imm=
ediately and destroy the material immediately.




------_=_NextPart_001_01C8C595.66BC718F--






This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
Locked