logmon matching Regular Expressions when they shouldn't
search cancel

logmon matching Regular Expressions when they shouldn't

book

Article ID: 263145

calendar_today

Updated On:

Products

CA Unified Infrastructure Management On-Premise (Nimsoft / UIM) CA Unified Infrastructure Management SaaS (Nimsoft / UIM) DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Regular Expression

/^(?!.*(xxxx\/rest\/error\/logError|<OracleError#>|ExampleInfo.|<OracleError#>|: unique constraint (XXXX_<string>.XX_XXXXXXX_##)|XXXXXXX|ExampleString|ExampleString|XX ExampleString|ExampleString|ExampleString|ExampleString)).*\sERROR\s.*

Matching Log (should not match)

XXXxxxxError - <Matched Log Monitor In> </example/log>.log <date string> <time>,### DEBUG <example.com><.<string>.<string>.<string>XXXXXXXXXX -xxx.xxxx.xxxxxxx.xxxx.xxxxxxx.<ExampleString>- <ExampleString>.

Environment

  • Release: 20.4
  • logmon 4.11, 4.20

Cause

  • Regex needed a forward slash added at the end of the expression

Resolution

  • Added a forward slash (/) at the end of the REGEX and it did NOT match (as desired).