Neophyte
NeophyteEndrit,
I had a issue similar to yours, while filtering by resource property is the easiest way to do things if you want different resource properties on a single dashboard would be to have separate interface datasources that filter out interface descriptions by using the "auto.interface.alias" property and then specifying your port description by using regex or whatever works for you.
Only issue is that would mean there are 2 or more datasources using SNMP to hit your device to gather interface metrics, which if the total number of interfaces is large enough could slow things down.
Product ManagerHi dmb269,
If I am understanding your concern, the reason for the 2 SNMP datasources would be the first to collect SNMP data per usual, and the second datasource to filter out the interface descriptions, and assign the "auto.interface.alias", as a property, through the property source, and specify the port description format, which would could then be filterable on the global Dashboards page using the newly introduced Instance Property Filter. My guess is that would be helpful here would be if there as an "on the fly" way to group by the instance property description, thus eliminating the need to create a second datasource, to parse, and apply the instance "auto.interface.alias" instance property.
NeophyteHi jake_nahm
Exactly, similar to Ian we would create 2 datasources for gathering interfaces. One for port description = Transport & one for port description = Peering. This would just allow us to have 1 dashboard with 2 widgets (one showing transport and the other showing peering) and wouldn't require us to swap saved views and then we could see both in real time.
