-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Palo Alto | include "strict_date_optional_time_nanos" format for date fields #26033
Comments
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
6 tasks
legoguy1000
added a commit
to legoguy1000/beats
that referenced
this issue
Jun 24, 2021
mergify bot
pushed a commit
that referenced
this issue
Jun 24, 2021
…odule (#26158) * #26033: add strict_date_optional_time_nanos format * update changelog * added new sample log, need to check CSV parsing * update sample data Co-authored-by: Marius Iversen <marius.iversen@elastic.co> (cherry picked from commit 7742fda) # Conflicts: # x-pack/filebeat/module/panw/panos/ingest/pipeline.yml # x-pack/filebeat/module/panw/panos/test/global_protect.log-expected.json # x-pack/filebeat/module/panw/panos/test/hipmatch.log-expected.json
6 tasks
marc-gr
pushed a commit
to marc-gr/beats
that referenced
this issue
Jun 28, 2021
…odule (elastic#26158) * elastic#26033: add strict_date_optional_time_nanos format * update changelog * added new sample log, need to check CSV parsing * update sample data Co-authored-by: Marius Iversen <marius.iversen@elastic.co>
marc-gr
added a commit
that referenced
this issue
Jun 29, 2021
…odule (#26158) (#26525) * #26033: add strict_date_optional_time_nanos format * update changelog * added new sample log, need to check CSV parsing * update sample data Co-authored-by: Marius Iversen <marius.iversen@elastic.co> Co-authored-by: Alex Resnick <adr8292@gmail.com> Co-authored-by: Marius Iversen <marius.iversen@elastic.co>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Logs that are generated from Palo Alto's Cortex Data Lake default to using the date format strict_date_optional_time_nanos, while the panw-panos-pipeline currently defaults to using the following date format:
Adding 'strict_date_optional_time_nanos' as a default date format for the filebeat panw-panos-pipeline will also users to ingest data from Palo Alto's Cortex Data Lake without manually modifying the pipeline. This format has been tested by a user:
The text was updated successfully, but these errors were encountered: