Dashboard based on Port Description

Hi Community,

My aim is to be able to filter specific ports based on the port Description and show it on a dashboard.

We use specific ports with specific description for certain type of traffic. We want to be able to see this traffic.

These ports are across several devices so a filtering based on one of these : auto.interface.description ; auto.interface.alias ; auto.interface.name ; i think would help but I am not able to find a workaround.

An example would be to show ports that their description start with 'Transport'

I also tried dynamic grouping based on above instances but its not working.

Thank you!

Endrit Hasaj

eh-xiber

Posted 1 year ago·Last reply 1 year ago

5 comments

eh-xiber

OP1 year ago

Hello Ian,

Thank you for your reply.

That is what I did in fact and it works to some extent.

Lets say I want to have on a single dashboard different graphs based on different port descriptions.

For instance :

1st graph has to be filtered based on port description: Transport

2nd graph has to be filtered on port description: Peering

Is there a way to build such dashboard without having to switch between saved views?

Once again thank you for taking your time and replying to my thread.

Regards,

Endrit Hasaj

Devon Biancarelli-Milano

·1 year ago

Endrit,

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.

jake_nahm

·1 year ago

Hi 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.

Devon Biancarelli-Milano

·1 year ago

Hi 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.

Ian Marge

·1 year ago

Hi Endrit,

Thank you for your question.

Are you familiar with the new LogicMonitor Dashboard Property Filters? You can read more about that here: https://www.logicmonitor.com/support/modern-dashboards

For your question above, please follow these steps:

Make sure that you have specified the Resource Property on the dashboard that you are currently using.
- Example:
  - Property: system.categories
  - Value: interfaces
Then you can specify the Instance Property.
- Example:
  - Property: auto.interface.description
  - Value: Transport* - The asterisk (*) acts as a wildcard to match any interface whose description starts with 'Transport'

Please let use know if that answers your question.

Best,
Ian