Bandwidth sensors don't automatically have triggers setup for usage. We have hundreds of interfaces that we would like to have alerts on. There are a few issues.

  1. After a bandwidth sensor is created, PRTG is no longer aware of the interface speed.
  2. There is no known way to bulk-add speed based triggers to bandwidth sensors.

I would like to see some combination of the following:

  1. Ability to set triggers on interfaces/bandwidth by percent usage, would not need to worry about interface speed this way.
  2. Ability to set triggers based on hierarchy and/or inheritance so that all bandwidth sensors can be more easily managed with the same triggers.
  3. A multi-edit option for triggers so that they can be filtered by tag and set as needed in bulk.
  4. At sensor creation for an interface, the speed/type is added as a tag.

Article Comments

It would help if you could share more detail on your network setup. But here are a few thoughts on what you've queried.

Have you tried setting triggers in the parent device/group and have them inherited to your sensors? Inherited triggers are enabled by default.

Setting triggers by percentage bandwidth would require specifying a bandwidth for a sensor and i think this may just increase the processing load. But if you are monitoring 100/1000Gbps interfaces on a switch, the inherited triggers should help you achieve the alert levels.

If you are using SNMP Traffic sensors the tags "bandwidthsensor", "snmptrafficsensor" are added by default. You would need to create a tag for speed as different equipment has different interface speeds.

Also, this kb article could be useful:

https://helpdesk.paessler.com/en/support/solutions/articles/87529-notification-only-for-device-with-tag-printer


Sep, 2022 - Permalink