Merged
Conversation
…the timestamp of the auth log
|
Pinging @elastic/sec-linux-platform (Team:Security-Linux Platform) |
|
Contributor
|
I think the version number has to be again incremented because the latest version for this integration is now 2.5.4 |
🚀 Benchmarks reportTo see the full report comment with |
nfritts
approved these changes
Sep 23, 2025
💚 Build Succeeded
History
cc @Tacklebox |
|
|
Package system - 2.6.1 containing this change is available at https://epr.elastic.co/package/system/2.6.1/ |
tehbooom
pushed a commit
to tehbooom/integrations
that referenced
this pull request
Nov 19, 2025
* Allow overriding existing timestamp in the system-auth pipeline with the timestamp of the auth log * bumped version * add extra check for timestamp
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed commit message
Removed timestamp null check as it's always false and prevents timezone adjusted timestamp from being parsed.
Checklist
changelog.ymlfile.Related issues