[filebeat][fortinet] Use default add_locale for fortinet.firewall#26524
[filebeat][fortinet] Use default add_locale for fortinet.firewall#26524marc-gr merged 2 commits intoelastic:masterfrom
Conversation
|
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
|
Doesn't this cause issue if the firewall isn't in the same timezone as Filebeat?? |
|
/test |
If that is the case, the timezone can be deleted or overwritten. The docs have been updated with https://github.com/elastic/beats/blob/7df6d010f2cdfdeced76e335049ae0fe78e4d1ea/filebeat/docs/include/timezone-support.asciidoc as per @jsoriano suggestion in #20300 (comment). Hope that makes sense 👍 |
jsoriano
left a comment
There was a problem hiding this comment.
This pipeline has several date processors, I wonder if same timezone should be used in all of them.
P1llus
left a comment
There was a problem hiding this comment.
LGTM, seems the other reviews already catched the issues :)
|
This pull request is now in conflicts. Could you fix it? 🙏 |
937b8b4 to
5504dc2
Compare
* master: [MetricBeat] [AWS] Fix aws metric tags with resourcegroupstaggingapi paginator (elastic#26385) (elastic#26443) Move openmetrics module to oss (elastic#26561) Skip flaky test TestFilestreamMetadataUpdatedOnRename (elastic#26609) [filebeat][fortinet] Use default add_locale for fortinet.firewall (elastic#26524) Enroll proxy settings (elastic#26514)
…astic#26524) * Use default add_locale for fortinet.firewall * Use event.timezone in all date processors (cherry picked from commit 5d258c8)
…astic#26524) * Use default add_locale for fortinet.firewall * Use event.timezone in all date processors (cherry picked from commit 5d258c8)
…stage-failed-within-same-build * upstream/master: (36 commits) Revert "[CI] fight the flakiness with some retry option in the CI only for the Pull Requests (elastic#26617)" (elastic#26704) Packaging: linux/armv7 is not supported (elastic#26706) Cyberarkpas: Link to official docs on how to setup TLS (elastic#26614) Make network_direction, registered_domain and convert processors compatible with ES older than 7.13.0 (elastic#26676) Disable armv7 packaging (elastic#26679) [Heartbeat] use --params flag for synthetics (elastic#26674) Update dependent package to avoid downloading a suspicious file (elastic#26406) [mergify] set title and allow bp in any direction (elastic#26648) Fix memory leak in SQL helper when database is not available (elastic#26607) [CI] fight the flakiness with some retry option in the CI only for the Pull Requests (elastic#26617) [mergify] automate PRs that change the backport rules (elastic#26641) [Metricbeat] Add Airflow module in xpack (elastic#26220) chore: add-backport-next (elastic#26620) [metricbeat] Add state_job metricset (elastic#26479) CI: jenkins labels are less time consuming now (elastic#26613) [MetricBeat] [AWS] Fix aws metric tags with resourcegroupstaggingapi paginator (elastic#26385) (elastic#26443) Move openmetrics module to oss (elastic#26561) Skip flaky test TestFilestreamMetadataUpdatedOnRename (elastic#26609) [filebeat][fortinet] Use default add_locale for fortinet.firewall (elastic#26524) Enroll proxy settings (elastic#26514) ...
What does this PR do?
add_localedefault processor tofortinet.firewallevent.timezoneon the ingest pipelineWhy is it important?
It has been a recurrent request to be able to set a custom timezone to
fortinet.firewall.Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Related issues