-
Notifications
You must be signed in to change notification settings - Fork 488
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
[Rule Tuning] Remove timestamp_override for endgame-* promotion rules #951
[Rule Tuning] Remove timestamp_override for endgame-* promotion rules #951
Conversation
"sha256": "d4b0108faa80fc35468cc5cfbbaf48b4db4dad7d1373cf48388752568eb83c98", | ||
"version": 5 | ||
"sha256": "adcd895329cc4d1c41bc4bf8b75404c838823731713fa11f3d3b671dd24cc31d", | ||
"version": 4 |
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.
so this one went backwards to 4 because the rule was un-changed, because it was endgame.
this took me a second but makes sense
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.
also @paulewing should this rule be renamed to - Elastic Endgame
?
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.
versions look right.
at some point (maybe for the next release), we can rename those rules to - Elastic Endgame
to match the products most accurately
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.
thanks for fixing the years, LGTM 🚢
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! Thanks for the cleanup here @brokensound77! 🙂
* lock versions for rule changes in v7.11.0 (#947) * [Rule Tuning] 7.11.2: Add timestamp_override to all query and non-sequence EQL rules (#948) * [Rule Tuning] Add timestamp_override field to 7.11.0 rules * Lock versions for 7.11.2 rules * [Rule Tuning] Remove timestamp_override for endgame-* promotion rules (#951)
#91771) ## Summary Pulls updates from elastic/detection-rules#951. This basically reverts the changes made in #91553 for _only_ the endgame promotion rules ### Checklist - [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/master/packages/kbn-i18n/README.md)
elastic#91771) ## Summary Pulls updates from elastic/detection-rules#951. This basically reverts the changes made in elastic#91553 for _only_ the endgame promotion rules ### Checklist - [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/master/packages/kbn-i18n/README.md)
#91771) (#91784) ## Summary Pulls updates from elastic/detection-rules#951. This basically reverts the changes made in #91553 for _only_ the endgame promotion rules ### Checklist - [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/master/packages/kbn-i18n/README.md) Co-authored-by: Justin Ibarra <brokensound77@users.noreply.github.com>
Issues
related to elastic/kibana#91597
Summary
Removed the
timestamp_override
field from allendgame-*
promotion rules, because the field is not mapped.I also very carefully reset the hashes and versions of these files to their previous state, so as not to double bump (since these have not yet been released). The more eyes on this the merrier (a good reference point - the last lock before the previous changes)
The
updated_date
was also fixed with the correct year (but this is inconsequential to the rules in Kibana as that field is used only locally at this point)