[Check_mk (english)] Different switch port error thresholds based on attached device

[Arno Wijnhoven]

Dear list,

Our switches are monitored by Check_MK (1.4.0p36 Raw). I was wondering if it's possible to use different error thresholds for different ->attached<- devices.

Example: I want to allow for more errors on a switch port that has an UPS connected and less for a port with an ESXi host connected.
Unfortunately, Check_MK doesn't know what kind of device is connected. I query this extra info in my notification script, so this is AFTER a rule is hit.

I could put some threshold logic in my output script (hard coded), but this is something I'd rather not do.
I prefer to have a rule at 'Network interfaces and switch ports' so I have all settings in one place (else I'd be the only one able to adjust the thresholds).

A thought:
Is it possible to query Check_MK for rules and settings?
This way I could create a rule that won't be hit, but it would only hold the threshold setting. Then I could get that info from my notification script and make a decision based on that info.
Not an elegant solution, but at least all threshold settings would be in one place.

Any (other) thoughts are very welcome.

Met vriendelijke groeten / Kind regards / Mit freundlichen Grüßen,

Arno Wijnhoven

[Andreas Döhler]

Hi Arno,

One suggestion, use the port description in a good way to determine what
type of device is connected.
I do this in a way like the following - Uplink / Access / AP and so on.
Then you can use the description as port names and bind the rules to the
port names.

At the moment i work on one extension of the network and switch port
inventory rule to make it possible to use a combination of classic port
names and description/alias as an name for the service.

Best regards
Andreas

Am Fr., 30. Nov. 2018 um 11:17 Uhr schrieb Arno Wijnhoven <

Post by Arno Wijnhoven
Dear list,
Our switches are monitored by Check_MK (1.4.0p36 Raw). I was wondering if
it’s possible to use different error thresholds for different –>attached<-
devices.
Example: I want to allow for more errors on a switch port that has an UPS
connected and less for a port with an ESXi host connected.
Unfortunately, Check_MK doesn’t know what kind of device is connected. I
query this extra info in my notification script, so this is AFTER a rule is
hit.
I could put some threshold logic in my output script (hard coded), but
this is something I’d rather not do.
I prefer to have a rule at ‘Network interfaces and switch ports’ so I have
all settings in one place (else I’d be the only one able to adjust the
thresholds).
Is it possible to query Check_MK for rules and settings?
This way I could create a rule that won’t be hit, but it would only hold
the threshold setting. Then I could get that info from my notification
script and make a decision based on that info.
Not an elegant solution, but at least all threshold settings would be in one place.
Any (other) thoughts are very welcome.
Met vriendelijke groeten / Kind regards / Mit freundlichen GrÌßen,
Arno Wijnhoven
_______________________________________________
checkmk-en mailing list
Manage your subscription or unsubscribe
https://lists.mathias-kettner.de/cgi-bin/mailman/listinfo/checkmk-en

[Arno Wijnhoven]

Thanks Andreas,

Thanks for your suggestion – this will work for sure. Unfortunately I have a central DB with all connections.
Your suggestion means that I need to configure all ports in two places: our current central DB + the description on the switch.

Not sure if I’m going down this road, I’ll keep it in mind for now, thanks.

Arno Wijnhoven

From: Andreas Döhler [mailto:***@gmail.com]
Sent: vrijdag 30 november 2018 14:07
To: Arno Wijnhoven <***@vsnsystemen.nl>
Cc: <checkmk-***@lists.mathias-kettner.de> <checkmk-***@lists.mathias-kettner.de>
Subject: Re: [Check_mk (english)] Different switch port error thresholds based on attached device

Hi Arno,

One suggestion, use the port description in a good way to determine what type of device is connected.
I do this in a way like the following - Uplink / Access / AP and so on.
Then you can use the description as port names and bind the rules to the port names.

At the moment i work on one extension of the network and switch port inventory rule to make it possible to use a combination of classic port names and description/alias as an name for the service.

Best regards
Andreas

Am Fr., 30. Nov. 2018 um 11:17 Uhr schrieb Arno Wijnhoven <***@vsnsystemen.nl<mailto:***@vsnsystemen.nl>>:
Dear list,

Our switches are monitored by Check_MK (1.4.0p36 Raw). I was wondering if it’s possible to use different error thresholds for different –>attached<- devices.

Example: I want to allow for more errors on a switch port that has an UPS connected and less for a port with an ESXi host connected.
Unfortunately, Check_MK doesn’t know what kind of device is connected. I query this extra info in my notification script, so this is AFTER a rule is hit.

I could put some threshold logic in my output script (hard coded), but this is something I’d rather not do.
I prefer to have a rule at ‘Network interfaces and switch ports’ so I have all settings in one place (else I’d be the only one able to adjust the thresholds).

A thought:
Is it possible to query Check_MK for rules and settings?
This way I could create a rule that won’t be hit, but it would only hold the threshold setting. Then I could get that info from my notification script and make a decision based on that info.
Not an elegant solution, but at least all threshold settings would be in one place.

Any (other) thoughts are very welcome.

Met vriendelijke groeten / Kind regards / Mit freundlichen GrÌßen,

Arno Wijnhoven

_______________________________________________
checkmk-en mailing list
checkmk-***@lists.mathias-kettner.de<mailto:checkmk-***@lists.mathias-kettner.de>
Manage your subscription or unsubscribe
https://lists.mathias-kettner.de/cgi-bin/mailman/listinfo/checkmk-en