Tolerate existing event.timezone in fortimail and fortiproxy - #11606
Merged
taylor-swanson merged 2 commits intoOct 31, 2024
Conversation
- Change rename to set processor when setting event.timezone - In certain situations, an add_locale processor may have run on the agent and this will set event.timezone.
taylor-swanson
added
bugfix
|
💚 Build Succeeded
|
taylor-swanson
marked this pull request as ready for review
October 31, 2024 16:59
|
Pinging @elastic/sec-deployment-and-devices (Team:Security-Deployment and Devices) |
aleksmaus
approved these changes
Oct 31, 2024
Contributor
|
Package fortinet_fortimail - 2.13.1 containing this change is available at https://epr.elastic.co/search?package=fortinet_fortimail |
Contributor
|
Package fortinet_fortiproxy - 1.0.1 containing this change is available at https://epr.elastic.co/search?package=fortinet_fortiproxy |
harnish-crest-data
pushed a commit
to chavdaharnish/integrations
that referenced
this pull request
Feb 4, 2025
…#11606) - Change rename to set processor when setting event.timezone - In certain situations, an add_locale processor may have run on the agent and this will set event.timezone.
harnish-crest-data
pushed a commit
to chavdaharnish/integrations
that referenced
this pull request
Feb 5, 2025
…#11606) - Change rename to set processor when setting event.timezone - In certain situations, an add_locale processor may have run on the agent and this will set event.timezone.
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
Checklist
changelog.ymlfile.[ ] I have verified that any added dashboard complies with Kibana's Dashboard good practicesHow to test this PR locally