system/data_stream/syslog: Message Parsing issue and exclusion of files in syslog datastream#8621
Conversation
🌐 Coverage report
|
|
@ishleenk17 Quick question: if we are trying to make sure that the message field doesn't already exist, could we just check for |
++ In the rename processor, if we add the |
efd6
left a comment
There was a problem hiding this comment.
In looking for context, I can see that the literal .gz$ is used everywhere for this pattern. Probably there should be an issue for this.
That won;t suffice as we want to remove the message field |
Yes, that would work as well. We are following this remove practice. See elastic/package-spec#583. |
| show_user: false | ||
| description: The files to be excluded by the Agent. See [exclude_files](https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-input-log.html#filebeat-input-log-exclude-files) for details. | ||
| default: | ||
| - \.gz$ |
There was a problem hiding this comment.
In the original issue,.bz2 is also highlighted. Do you want to consider bz2 also in the default exclusion list?
There was a problem hiding this comment.
No, that would be left to the user. As mostly users exclude .gz files
| if: 'ctx.event?.original != null' | ||
| field: message | ||
| ignore_missing: true | ||
| description: 'The `message` field is no longer required if the document has an `event.original` field.' |
There was a problem hiding this comment.
Just wanted to know, in instances where event.original is already present, such as when it comes from Logstash, we wouldn't alter the event.original field, and it wouldn't be replaced(as per expected state description here). Is there a chance in these situations for the data in the message and event.original fields to be different? If so, I believe we should refrain from removing the message field in those cases and consider adding a check to account for this scenario.
There was a problem hiding this comment.
Once it enters the pipeline event.original and message would be same. Hence we would like to avoid having duplicates. Thats why deletion is important immediately after the rename of event original to message field.
There can be a case where message field it used after the removal as seen in syslog datastream. So that also gets handled by the removal of message field before this.
Co-authored-by: subham sarkar <sarkar.subhams2@gmail.com>
Co-authored-by: muthu-mps <101238137+muthu-mps@users.noreply.github.com>
|
Package system - 1.50.0 containing this change is available at https://epr.elastic.co/search?package=system |
1 similar comment
|
Package system - 1.50.0 containing this change is available at https://epr.elastic.co/search?package=system |
Proposed commit message
There are 2 changes as part of the PR.
1. Making the exclude_files configurable for the user asd user might want to exclude different type of files.
2. Resolving the message parsing issue in Syslog
Checklist
changelog.ymlfile.Related issues