This is a multi-part message in MIME format.
------=_NextPart_000_0000_01C7447A.C4826FD0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf
> Of Hendrik Baecker
> Sent: January 30, 2007 14:12
> To: Nagios Developers List
> Subject: [Nagios-devel] Latencies with process-perfdata command
>
> Hi List,
>
> I figured out, that I run into some latency problems if I use a
> process-perfdata command to handle plugin performance data
> with external
> scripts.
>
> So I am asking myself, what would be the best way (in thought of not
> getting into latency troube) to handle the perfdata.
>
> My external processing scripts (perl) are running quiet fast, but I
> think, that every process that nagios has to fork is pure
> balast for the
> performance.
>
> For testing I've wrote a small c programm, that only checks the right
> calling of the programm itself (right settings for command line
> options), forks itself and after successfully fork kills the father
> (mother?) process. The forked child process then does its job.
>
> I thought it would be better for nagios if it gets the fact that, the
> external command exits as fast as possible. This little (and yes - a
> little bit dirty) programm is doing the job quiet fine and my
> latencies
> are blown nearly away.
> But not in that way that I was thinking of.
>
> So I am now at a point to say that the execution time of external
> scripts and the nagios check latencies are in some kind of coherence.
>
> No kind of processing perfdata => no latency
> directly run an external perl script => up to horrible latency
> faking a fast exit to nagios through forking => nicer latency
>
> Actual I am thinking about solving this issue in some way like this:
>
> Don't using an external command but let nagios write the
> perfdata files
> as described in nagios documentation and nagios.cfg and write a small
> daemon to read the file and process the perfdata as "usual" (writing
> rrdfiles).
>
> So, what I want to discuss is the best way to do the job of processing
> performance data from compatible plugins, and I want to understand why
> it seems to be bad for nagios to execute external commands with an
> execution time of a few seconds.
We're doing exactly that, but instead of writing a file and running scripts
to read that data we're using a daemon (written in Perl) that reads a fifo
(where Nagios writes performance data) and store data into memory for a
short amount of time.
We use Cacti to graph all data, so for thing coming from Nagios there's a
cacti script that connects to the daemon and fetch the data.
If you're interested we'll release that soon... I'll probably make an
anouncement in Nagiosplug-devel...
Thomas
------=_NextPart_000_0000_01C7447A.C4826FD0
Content-Type: application/x-pkcs7-signature;
name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="smime.p7s"
MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIIzjCCAlYw
ggG/oAMCAQICEF6WlTyD2iR9R4J/yf+4yw4wDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkEx
JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQ
ZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA2MTAxNjE1MTgxNVoXDTA3MTAxNjE1MTgx
NVowQjEfMB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEfMB0GCSqGSIb3DQEJARYQdGhv
bWFzQHphbmdvLmNvbTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAtkCTbSUT0qmJN70ik/vg
3cNmuRbfC18Mz7T6CNqwyb/URZ5n3PQlA0Tel2aY73QfCa4Ws1eQ+b19KJb/9IbgcRM198OZx+jY
3R+Y2/lVSsUoQaFpHYnZp9voKG+ugi3MiPChy9q/OuNfRL7IiKxjpsYKVRHrqFLWvnX9qIoxkjcC
AwEAAaMtMCswGwYDVR0RBBQwEoEQdGhvbWFzQHphbmdvLmNvbTAMBgNVHRMBAf8EAjAAMA0GCSqG
SIb3DQEBBQUAA4GBAMNB9/ulaYWECjEiG5hlAtN/ZXiaWSOOBRp4LJSfXX60VgmwQUfYHmWycMAv
yHaGz06DrMonrCHiHcpkEkntgU7NK6G95Hg7CpHyd98+zRDxBe/TTeGrePqFxQ+MbGZ4+orUPAtq
8PNFGCogpyCElTzkSP8KkYJ3cKIAaBAa2NrxMIIDLTCCApagAwIBAgIBADANBgkqhkiG9w0BAQQF
ADCB0TELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBU
b3duMRowGAYDVQQKExFUaGF3dGUgQ29uc3Vsd
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]