How to: How to specify vlan in monitoring rule

Hi,
I have 50 switches and 100 cameras in my network.
I need to monitor the traffic on the camera ports so that it does not drop below 3Mbps.
But I need to set this only on ports that are in vlan10 - cam vlan.
How do I do this? I really don’t know how to do.

best regards

Michal

Edit rule: Network interfaces and switch ports
rule: Network interfaces and switch ports

Maybe it’s here? How to write the condition correctly?

Normally you don’t see the used vlan on the physical port.
That means, if you not use the description/alias of a port to identify the used vlan, you will have no chance to specify a rule for the monitoring of these ports.

However, CMK has this information:

That’s a shame. I also use Obserivum and this is easy to do there. :frowning:

If your device provides the correct values there (i have some switches where i don’t see all the vlans there), you can use a script like data2label to set service labels for the discovered ports. These labels than can be used for the rules as condition.

Unfortunately data2label only sets host labels, not service labels.

Oh i forgot - the service labels i used on the last project where set by an own written check :frowning:
That is one of the features that would be nice to have earlier or later - service labels defined with some type of API or rule.

You can add service labels within the ruleset “Network interface and switch port discovery”, but that does not seem very practical here.

It would be nice if attributes like the VLAN(s) are added automatically as labels.

1 Like

This would be the easiest way.

I don’t think so.
Or do you have any advice?

Maybe ideas.checkmk.com is the right place to propose a feature that might be missing here?
I found this, which seems to go into the general direction: https://ideas.checkmk.com/suggestions/312010/set-labels-based-on-software-inventory

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.