You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's already possible to specify interfaces that should be scraped. This is required for routers that have a huge number of virtual interfaces, like BNGs.
We should extend the feature to allow the use of regexes in the interface list.
Additionally we should allow to exclude specific interfaces based on a list of regexes.
To implement this we first need to fetch the list of all interfaces (show interface summary), filter based on our selectors and then fetch the individual interfaces.
When both interfaces and interfaces_excluded are empty we should continue to use the simple implementation where show interfaces is collected without further arguments, for performance reasons.
The text was updated successfully, but these errors were encountered:
vidister
changed the title
Allow regex in interface selector
Extend interface selector
May 13, 2024
It's already possible to specify interfaces that should be scraped. This is required for routers that have a huge number of virtual interfaces, like BNGs.
We should extend the feature to allow the use of regexes in the interface list.
Additionally we should allow to exclude specific interfaces based on a list of regexes.
The config interface would look like this:
To implement this we first need to fetch the list of all interfaces (
show interface summary
), filter based on our selectors and then fetch the individual interfaces.When both
interfaces
andinterfaces_excluded
are empty we should continue to use the simple implementation whereshow interfaces
is collected without further arguments, for performance reasons.The text was updated successfully, but these errors were encountered: