Fix Graylog error message OEC content pack configuration @YuryHrytsuk @mrnicegyu11

[pcrespov]

• Adjust gralog Grok pattern extractor to include log_oec and log_level (broken) and anything within this # Graylog Grok pattern extractor:

log_level=%{WORD:log_level} \| log_timestamp=%{TIMESTAMP_ISO8601:log_timestamp} \| log_source=%{DATA:log_source} \| (log_uid=%{WORD:log_uid} \| (log_oec=%{WORD:log_oec} \| )?log_msg=%{GREEDYDATA:log_msg}

[GitHK]

please mote that ideally when you capture the oec it should not report on the part that is randomy generated. only the first part of the error should be captured

[pcrespov]

please mote that ideally when you capture the oec it should not report on the part that is randomy generated. only the first part of the error should be captured

@GitHK what if you want to find out the exact incident? Note that the fingerprint reflects the traceback but not the context. For instance, you can have the same exception KeyError but for two different keys. Another reason is that you might want to check the logs around that specific incident

[GitHK]

please mote that ideally when you capture the oec it should not report on the part that is randomy generated. only the first part of the error should be captured

@GitHK what if you want to find out the exact incident? Note that the fingerprint reflects the traceback but not the context. For instance, you can have the same exception KeyError but for two different keys. Another reason is that you might want to check the logs around that specific incident

If this is just the filter to capture these errors it's OK.

[mrnicegyu11]

I try to address this in ITISFoundation/osparc-ops-environments#1004