When using the built in syslog page within NPM there is a bug (or feature if you're solarwinds ) that when using the 'message pattern' field to attempt to filter syslog messages to find a particular string you HAVE to put a wildcard * both IN FRONT OF and AFTER the string or else you will return zero results.
This is just crazy.
We're running NPM 11.5 just FYI but the problem was there with 11.0.1 and apparently previous versions as well.
I have an open case (case number 766990) with solarwinds to try and get this fixed but they claim that because this is how it's supposed to work. Really? What else would I possibly type into the message pattern other than the fact I'm trying to search for a particular string within a syslog message.
Support says that because this is how it worked in previous versions of NPM they don't consider it a bug. I say that just means it's been a bug that they haven't fixed in multiple versions of orion.
Anyway, I've been doing my own digging and I've identified that the message pattern field is contained directly within the Syslog.aspx file. It calls a function that is located within the Syslog.aspx.cs file (lines 143-144) that reads the string.
I'm wondering if anyone knows some method for me to modify the function to just add the wildcard characters in front of and after the string without asking a user to remember to type the wildcards for the search to work properly. Does anyone have any experience with this?
Line 80 of syslog.aspx
<td><asp:TextBox runat="server" ID="messagePattern"></asp:TextBox></td>
Lines 143-144 of syslog.aspx.cs
if (Request["Message"] != null || Request["MessagePattern"] != null)
messagePattern.Text = Request["Message"] ?? Request["MessagePattern"];