Has no one figured this out yet? Filtering would be great but it doesn't seem to actually work for me.
2 of 2 people found this helpful
Had to open a support ticket a while back to find out how to get this done. What worked for me was
- Delimiter was the vertical bar. On my keyboard, it's above the Enter key.
- Second, instead of filtering on Interface Name, I had to use Interface Description
- Instead of using keywords, I had to use regular expressions. Therefore I had to use one of the last two options from the dropdown menu.
Like the OP, when I went back to check the filter, it replaces the delimiter with its HTML character code equivalent, in hex. I just cancelled out of that window and moved on. Seems to be working so far. Hope this helps.
My goodness. Thanks for the info, but that seems like a terrible way to implement the feature by SW and not put any clues or examples for the user! A pipe as a deliminator?!? I'll give it a try...
I use this feature all the time with no delimiter at all, the "any" options seem to natively use spaces as their delimiter, and the all would be the one you select if you want to exclude a string that includes spaces.
I'll typically do something like interface description does not contain any keywords: loopback -0000 null miniport async voip phone workstation
and that works just fine. My actual settings tend to be more elaborate than that but in any case I never use a delimiter of any type and have used similar filters successfully on dozens of client sites.
Awesome, thank you for the info!
3 of 3 people found this helpful
So I realize I am 2 1/2 years late to this post, but I ran into this yesterday. Your picture helped me so I would like to help you.
The "%20" is the HTML code for a space. When you save the discovery and open it back up again the website is translating that space into "%20". Then when you run the discovery with the %20 the filter will no longer match. If you save the discovery again then open it back up you will see that "25" has been added in front of "20". "%25" is the HTML code for "%". The website will then keep adding "25" to the front each time you save and reopen the discovery.
The workaround is to open up the discovery and remove the "%20" and "25" from the lines then save it. The discovery then function as normal until you open it up again. Each time you open the discovery for editing you will need to remove the "%20".
A Solarwinds engineer is aware of this and he is filing the bug report.
I hope this helps.
If this works for you please mark your issue as solved.