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

/^(?!.*(cbmt\/rest\/error\/logError|ORA-28000|Credit Bureau History Info.|ORA-00001: unique constraint (CBMT_abcdefg.UK_CONTROL_NO)|No history of bankruptcy|RECORD-NOT-FOUND|Object moved|NO HISTORY FOUND|NO DISASTER DATA|No entity found for query|No master exists for this loan)).*\sERROR\s.*

Matching Log(should not match)

CBMxxxxError - Matched Log Monitor In /opt/jboss-as/standalone/log/xxxxapp.log 2023-03-21 08:33:01,560 DEBUG com.xxx.cbmt.xxxxxx.rest.disputes.DisputeAccountRetrievalService -com.xxx.cbmt.xxxxxxx.rest.disputes.DisputeAccountRetrievalService- Exception occured due to No history of bankruptcy case filings found.

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).

Powered by Wolken Software