-
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
Change the type of threatintel.indicator.first_seen to date #26765
Conversation
The `threatintel` module field was incorrectly mapped as keyword instead of date.
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 🧪
|
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.
LGTM
I've tested this ingesting data from all threatintel datasets using the older (wrong) datatype and then with a newer Filebeat using the fixed datatype. Didn't observe any ingestion errors nor query errors in Kibana dashboards. |
The `threatintel` module field was incorrectly mapped as keyword instead of date. (cherry picked from commit b6ee587)
The `threatintel` module field was incorrectly mapped as keyword instead of date. (cherry picked from commit b6ee587)
What does this PR do?
This fixing the field mapping for
threatintel.indicator.first_seen
, which was usingkeyword
datatype, instead ofdate
.Why is it important?
To prevent issues with visualizations and aggregations.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.