Rule to disable discovery interface services of virtual tunnels with counter

General
,
1

Since an update from server running VPN checkmk suddenly discovers virtual tunnel interfaces that have a short live span and get replaced by a new one with interface nr +1.

image

I had a rule at first that disables the new ones, but that is not dynamic so I have to keep changing it.

image

Since all the real interface start with 0, silly me thought, lets negate it instead:

image
image697×48 4.34 KB

But this results at disabling all services not just the interface nrs not starting with 0. :laughing:

I can make a rule that disables services starting with Interface 1, Interface 2 up to Interface 9 for this server, but is there another way?

Can you perhaps disable services based on status detail output so I can filter out services with [tun1000]? If so, how?

I am using raw 2.1.0p5 …

2

You should make the interface name part of the service name and then disable all services that start with “Interface tun”.

Read Network Monitoring with Checkmk: 3 rules to rule them all | Checkmk

3

Ofcourse!

I have that running actually, but just for the switches, not for servers.
Guess I should change that first. (-:

1 Like
4

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.