Replies: 1 comment 1 reply
-
|
Hi, its recommended that Drain3 (and also Drain afaik) is ingested with only the unstructured part of the log message ("content"). So this addition seems a bit out of context. Also it may be not robust enough to handle some more complex log formats. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
https://github.com/IBM/Drain3/blob/7e340cd1eb8e27b480b0654c77e5a44a77f1331b/drain3/drain.py#L1
Hello,
is possible to add this function ?
This function is intriduced here : https://github.com/logpai/logparser/blob/master/logparser/Drain/Drain.py
Here is an exemple of logformat param:
log_format = '<Month> <Day> <Time> <Host> <ProcessName>: <Content>'Then you generate the regex:
headers, regex = generate_logformat_regex(log_format)and here is an exemple of log line:
line = 'Apr 29 06:12:56 node-elasticsearch-1 kernel: nvme nvme0: Abort status: 0x0'Based on this regex it will be easy to get any part of the message :
Kind regards,
Ali
Beta Was this translation helpful? Give feedback.
All reactions