Conversation
| target_field: source.address | ||
| ignore_missing: true | ||
| ignore_failure: true | ||
| - rename: |
There was a problem hiding this comment.
this rename looks like a repeat of line 82's .. intentional? if so, why?
There was a problem hiding this comment.
Unintentional, thanks!
|
Pinging @elastic/sec-linux-platform (Team:Security-Linux Platform) |
nicholasberlin
left a comment
There was a problem hiding this comment.
LGTM once CI agrees
belimawr
left a comment
There was a problem hiding this comment.
LGTM. Once CI is green, request a re-review and I'll approve it.
| "input": { | ||
| "type": "log" | ||
| }, | ||
| "message": "pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=89.160.20.156 user=root", |
There was a problem hiding this comment.
Why is the message going away? The message should remain IMO to allow for searches on the string (it's indexed as a text-family data type).
It looks like this was already the behavior based on the some other samples, but I think deleting message is the wrong thing to do.
There was a problem hiding this comment.
I have opened a fix to address this and consolidate the processing logic for journald and logfile inputs. That will make incorporating these PAM parsing enhancements easier for you.
🚀 Benchmarks reportTo see the full report comment with |
926a2fe to
68cb0e5
Compare
|
|
Hi! We just realized that we haven't looked into this PR in a while. We're sorry! We're labeling this issue as |
The changelog was updated but not the manifest.
…erns are successfully parsed
68cb0e5 to
6a6bdce
Compare
💔 Build Failed
Failed CI StepsHistory
cc @Tacklebox |
| "address": "", | ||
| "domain": "" |
There was a problem hiding this comment.
Let's remove these if when the values are empty.
|
Hi! We just realized that we haven't looked into this PR in a while. We're sorry! We're labeling this issue as |
|
Hi! We just realized that we haven't looked into this PR in a while. We're sorry! We're labeling this issue as |
|
Hi! This PR has been stale for a while and we're going to close it as part of our cleanup procedure. We appreciate your contribution and would like to apologize if we have not been able to review it, due to the current heavy load of the team. Feel free to re-open this PR if you think it should stay open and is worth rebasing. Thank you for your contribution! |




Proposed commit message
This adds a grok pattern and a few replacements to handle previously unmatched fields in some auth log messages.
Checklist
changelog.ymlfile.