Settings and activity
4 results found
-
1 vote
AdminHelbert Salas
(Admin, Paessler)
shared this idea
·
-
25 votes
Hi everyone,
Thank you all for voting on this idea.
Before we can commit to developing this idea, we need more input from the community.
We want to clarify: filtering/controlling which interfaces are monitored by the SNMP Traffic sensor during Auto-Discovery has actually been possible in PRTG for quite some time, by editing the ODT file: https://helpdesk.paessler.com/en/support/solutions/articles/76000041645-how-can-i-include-and-exclude-sensors-from-device-templates-
Since version PRTG .118, it has also been feasible with the SNMP Traffic v2 sensors.
That said, we understand that manually editing ODT files is not the most intuitive experience, and we suspect that's exactly the pain point many of you are hitting.
To help us prioritize the right improvements, we'd love to hear from you:
- What is your specific use case? (e.g., filtering by interface name, speed, type, etc.)
- What makes the current ODT-based approach difficult or impractical for you?
- Would a graphical UI for managing these filters solve your problem?
Thanks…
An error occurred while saving the comment AdminHelbert Salas
(Admin, Paessler)
supported this idea
·
-
1 voteAdminHelbert Salas
(Admin, Paessler)
supported this idea
·
AdminHelbert Salas
(Admin, Paessler)
shared this idea
·
-
1 voteAdminHelbert Salas
(Admin, Paessler)
shared this idea
·
Discovery can’t select SNMP Traffic interfaces by ifType, ifName, or ifAlias, so unwanted interfaces get sensors and the intended ones need manual creation. Please add allowlist/denylist filtering on these attributes in templates or discovery settings.