-
Notifications
You must be signed in to change notification settings - Fork 474
[cisco_ios] fix timezone with offset parsing #9890
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
3cf829f
to
3ed6d63
Compare
Pinging @elastic/sec-deployment-and-devices (Team:Security-Deployment and Devices) |
🚀 Benchmarks reportTo see the full report comment with |
💚 Build Succeeded
|
|
@@ -187,6 +187,48 @@ | |||
"preserve_original_event" | |||
] | |||
}, | |||
{ | |||
"@timestamp": "2024-05-06T16:13:09.123Z", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't get a chance to drop in a comment before this merged, but this produced the wrong time?
Shouldn't it be 15:13:09
since the original timestamp was 16:13:09
but had a timezone of UTC+1
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it should! nice catch, another PR is incoming 🥲
Proposed commit message
This PR fixes parsing issues with syslog messages that contain a timezone with offset in their timestamp
Checklist
changelog.yml
file.Author's Checklist
N/A
How to test this PR locally
elastic-package test pipeline -v
Related issues
Screenshots
N/A