-
Type:
Change Request
-
Resolution: Unresolved
-
Priority:
Minor
-
None
-
Affects Version/s: None
-
Component/s: Agent (G)
log / logrt items do not support multi-line regexps (or at least I was not able to get any working) and when determining severity / cause of an error it would be nice to see what happened prior to the error, i.e. to see a few lines in the log before
the error entry. Something like "grep -B 10 -A 10 error" ![]()