-
Bug
-
Resolution: Done
-
Medium
-
Beijing Release
-
None
-
None
There are Beijing oom component log messages that do not appear in Elasticsearch. The following issues exist:
- the log source field is missing for log4j log events
- the oom component logs are not parsed by logstash because many logback log patterns exist
- some oom component split MDC fields with "," in addition to the existing "\t"
- is blocked by
-
LOG-101 OOM Logging fixes tracking Epic
- Closed