DX NetOps

 View Only

 Regular expressions in Spectrum Watches

Miroslav's profile image
Miroslav posted Jan 14, 2021 12:17 PM
Hello,
we are monitoring VeloCloud SD-WAN devices with Spectrum. We are trying to setup monitoring for Latency, Jitter and PacketLoss for specific vcePaths with the Spectrum Waches Editor. Since Spectrum 20.2.5/10.4.2.2, VeloCloud devices are certified for Spectrum, so the VeloCloud specific MIB objects containing the source metrics are available. The basic setup works as expected, but in our usage scenario, we have hit a logical filtering setup problem, because according to our understanding, the Spectrum Watches Editor does not support the usage of regular expressions in the Expression tab (there is no primitive defined, that enables you to perform a RegEx match).

Can anyone share an idea, how we can perform regular expression matching (how to form the expression) on a string value/list from the attribute vcePathPeerName?
Attribute details:
vcePathPeerName 0x6d9004c Text String[] R E

Example (instance and pathpeer names randomized to protect customer) vcePathPeerName values (list):
7.130.126.24.19.172.55.118.179.81.160.147.40.93.20.85.1.4.115.13.86.10 abc22-bca2
23.13.62.244.138.12.195.18.17.187.11.147.121.13.250.15.1.4.52.59.62.150 dcg350-jkl4
68.203.222.123.62.17.34.11.1.8.134.17.22.133.20.18.2.9.35.121.3.18 sk-tom-smthg-vch-01
99.123.241.36.84.171.134.161.14.9.187.172.221.13.208.12.7.19.135.11.3.14 de-dui-blk-vce-01
129.5.21.136.80.211.136.168.154.90.189.12.234.213.25.142.70.14.165.81.7.3 br-tkj-vch-01

The aim is to identify the instance(s), which contains the substring "-vch" (row 3 and 5 in this case) in the vcePathPeerName. The output type of the watch has to be boolean, because the specific instance(s) matching the condition will then be used in additional watches.

We are currently trying to setup a workaround for the missing regular expressions functionality in the watches, by matching against the field length of the vcePathPeerName attribute, but the length of the peer name cannot always be controlled, therefore using the regular expression filter would be a better approach.