[Check_mk (english)] correlated services

Bieber Philipp philipp.bieber at dmgmori.com
Mon Jul 6 08:52:40 CEST 2015

for such cases, I have started to use the trending feature in WATO -> Parameters for discovered services -> file systems (used space and growth):

-       Enable trend computation

-       Levels on the time left until the file system gets full
When there is not enough space left (in our case) for another 48 hours of continuous growth, the check goes in a warning state. This should work for cases like this...


GILDEMEISTER Beteiligungen GmbH
Sitz der Gesellschaft: Bielefeld - Amtsgericht Bielefeld, HRB 40806
Geschäftsführer: Dipl.-Kfm. André Danks; Dipl.-Kfm. Christian Thönes

From: checkmk-en-bounces at lists.mathias-kettner.de [mailto:checkmk-en-bounces at lists.mathias-kettner.de] On Behalf Of Lance Tost
Sent: Thursday, July 2, 2015 7:41 PM
To: checkmk-en
Subject: [Check_mk (english)] correlated services

I'm wondering if there's any way to correlate services?  For example, we found that often an out-of-control CBS.log file was the culprit to our C: drive filling up on many servers.  So I put a check in to monitor the file and notify if it exceeds what I determined to be a potentially problematic size (let's say 200MB).  Now on some servers where C: has plenty of space, we get notifications for this file being > 200MB, but it's not really anything we need to be concerned with because the C: drive still has a lot of free space (status is OK).

So what I'm wondering is how could I *only* notify (or even go warning/critical) about the CBS.log *if* the C: service is in a non-OK state...?  Is that possible right now?  If not, are there plans to allow for rules that would make this possible?

Thank you,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mathias-kettner.de/pipermail/checkmk-en/attachments/20150706/a32aec5a/attachment-0001.html>

More information about the checkmk-en mailing list