Alarm Template filter for Baseline

Solved427 viewsalarm template smart baseline
0
0 Comments

I want to apply Smart Baseline only for logical interfaces that also matches a certain description.

I tried using a filter with the next rule ["Description" "Bundle-Ether"] but the Smart Baseline stopped alarming.

Does the filter only works for descriptions that we already use or is there any way to use that filter as well as the search box?

Jesus Perez [DevOps Advocate] Selected answer as best 27th October 2023

1 Answer

0
7.72K 3 Comments

Hi,

  1. Is the description that you're trying to filter on part of the table display key? In other words, when the alarm is active, do you see this value present in the "Parameter Description" column in the alarm console? Such parameters typically have the [IDX] indication.
  2. The Filter that you're trying to specify, is this in the "Filter" column of the alarm template?

If both above assumptions are correct then you should probably fill in a value with a wildcard (*) in the filter value. For example: *Bundle-Ether*

More info about the filter can be found here . Usage of the wildcards can be found here

Regards,

Jesus Perez [DevOps Advocate] Selected answer as best 27th October 2023
Jesus Perez [DevOps Advocate] commented

Thank you for the answer.

But also I need to filter the “Bundles” for an specific description, so as far as I tried, I can’t use more than 2 wildcard characters.

For example, if I have:
Bundle-Ether1:SIP-data-CACHES-Node
Bundle-Ether2:SIP-SVR-CACHE3-UPLINK
Bundle-Ether3:Use-for-IXN
Ethernet0/1:Use-for-CACHES
Ethernet0/2:SIP-Node-CACHE 2

I can’t use the filter: Bundle-Ether*CACHE*

So the thing is that I need to filter the interface to only allow the logical interfaces and then filter the logical interfaces for an specific description.
Laurens Moutton [SLC] [DevOps Enabler] commented

I see, so you cannot use “Bundle-Ether*” because then it would include “Bundle-Ether3…”. You also cannot use “*CACHE*” because it’s then again two wildcards and would include “Ethernet0/…”.
Not an ideal solution but what could potentially be done is specify multiple filters for the keys that you want to monitor (right-click on the row and chose “Duplicate”), of course when there are a lot of keys then I understand it is not desired to do so.
Another possibility could be to add a condition where the display key could then be validated against one wildcard expression and a second condition where it is validated against another wildcard expression. But I’m not sure if that will work as you might encounter again the *CACHE* situation…
Jesus Perez [DevOps Advocate] commented

Thank you Laurens.
I will try using the conditions. Hopefully that will works.

Appreciate your comments.
You are viewing 1 out of 1 answers, click here to view all answers.