[panw] Use high-res timestamp and ensure time zone config is applied - #10618
Merged
taylor-swanson merged 3 commits intoJul 29, 2024
Conversation
taylor-swanson
added
bug
🚀 Benchmarks reportTo see the full report comment with |
Contributor
Author
|
The fix is proving to be a bit more involved for the time zone configuration, and will require a bit more work before this PR is ready. |
- The high-res timestamp will now be copied to @timestamp, if available, since this is a more accurate timestamp of when the event occurred. - The high-res timestamp will be removed if it begins with 1969-12-31, since this indicates the time is a placeholder generated by PanOS 9.x or earlier. - The tz_offset config value was only propagated to the pipeline if the logfile input was used. It is now propagated for the TCP and UDP inputs as well. - event.timezone will be overwritten by _conf.tz_offset if the value is not 'local' (case insensitive)
taylor-swanson
marked this pull request as ready for review
July 29, 2024 16:55
|
Pinging @elastic/sec-deployment-and-devices (Team:Security-Deployment and Devices) |
💚 Build Succeeded
History
|
|
|
Package panw - 3.26.4 containing this change is available at https://epr.elastic.co/search?package=panw |
harnish-crest-data
pushed a commit
to chavdaharnish/integrations
that referenced
this pull request
Feb 4, 2025
…lastic#10618) - The high-res timestamp will now be copied to @timestamp, if available, since this is a more accurate timestamp of when the event occurred. - The high-res timestamp will be removed if it begins with 1969 or 1970, since this indicates the time is a placeholder generated by PanOS 9.1 or earlier. - The tz_offset config value was only propagated to the pipeline if the logfile input was used. It is now propagated for the TCP and UDP inputs as well. - event.timezone will be overwritten by _conf.tz_offset if the value is not 'local' (case insensitive)
harnish-crest-data
pushed a commit
to chavdaharnish/integrations
that referenced
this pull request
Feb 5, 2025
…lastic#10618) - The high-res timestamp will now be copied to @timestamp, if available, since this is a more accurate timestamp of when the event occurred. - The high-res timestamp will be removed if it begins with 1969 or 1970, since this indicates the time is a placeholder generated by PanOS 9.1 or earlier. - The tz_offset config value was only propagated to the pipeline if the logfile input was used. It is now propagated for the TCP and UDP inputs as well. - event.timezone will be overwritten by _conf.tz_offset if the value is not 'local' (case insensitive)
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
3 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
@timestamp, if available, since this is a more accurate timestamp of when the event occurred.add_localeprocessor.Checklist
changelog.ymlfile.How to test this PR locally
Related issues