-
Notifications
You must be signed in to change notification settings - Fork 197
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
Provide more details on how to start ML job to avoid ML detection rule execution failure #1160
Conversation
* Adds to both rule creation and troubleshooting topics * Adds new screenshots to highlight the correct feature to use
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
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!
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.
One super small nit/comment. Let's backport this to 7.16, 7.15, 7.14
.
Co-authored-by: Janeen Mikell-Straughn <57149392+jmikell821@users.noreply.github.com>
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 these clarifying additions @joepeeples.
Long-term it would be nice to make some UX enhancements to the Rule Creation/Details UI to allow for one-click enabling of the disabled jobs. I know we were hoping to add a shortcut link to auto-open the ML Job Settings UI with it filtered to the appropriate jobs, but we didn't get to that in initial dev. This is probably something we can track now as part of any changes around the ML Job Settings UI/Workflows here (https://github.com/elastic/security-team/issues/1912) -- till then though these doc updates will really help out, thanks! 🙂
@cybersecdiva we're waiting on your review so we can close this PR out. Thanks. |
…e execution failure (#1160) * First draft * Adds to both rule creation and troubleshooting topics * Adds new screenshots to highlight the correct feature to use * Update rule-start-ml-job.png * Corrects name of custom query rule * Update docs/troubleshooting/detections/detection-rules.asciidoc Co-authored-by: Janeen Mikell-Straughn <57149392+jmikell821@users.noreply.github.com> Co-authored-by: Janeen Mikell-Straughn <57149392+jmikell821@users.noreply.github.com> (cherry picked from commit b91a2a0)
…e execution failure (#1160) * First draft * Adds to both rule creation and troubleshooting topics * Adds new screenshots to highlight the correct feature to use * Update rule-start-ml-job.png * Corrects name of custom query rule * Update docs/troubleshooting/detections/detection-rules.asciidoc Co-authored-by: Janeen Mikell-Straughn <57149392+jmikell821@users.noreply.github.com> Co-authored-by: Janeen Mikell-Straughn <57149392+jmikell821@users.noreply.github.com> (cherry picked from commit b91a2a0)
…e execution failure (#1160) * First draft * Adds to both rule creation and troubleshooting topics * Adds new screenshots to highlight the correct feature to use * Update rule-start-ml-job.png * Corrects name of custom query rule * Update docs/troubleshooting/detections/detection-rules.asciidoc Co-authored-by: Janeen Mikell-Straughn <57149392+jmikell821@users.noreply.github.com> Co-authored-by: Janeen Mikell-Straughn <57149392+jmikell821@users.noreply.github.com> (cherry picked from commit b91a2a0)
…e execution failure (#1160) * First draft * Adds to both rule creation and troubleshooting topics * Adds new screenshots to highlight the correct feature to use * Update rule-start-ml-job.png * Corrects name of custom query rule * Update docs/troubleshooting/detections/detection-rules.asciidoc Co-authored-by: Janeen Mikell-Straughn <57149392+jmikell821@users.noreply.github.com> Co-authored-by: Janeen Mikell-Straughn <57149392+jmikell821@users.noreply.github.com> (cherry picked from commit b91a2a0) # Conflicts: # docs/troubleshooting/detections/detection-rules.asciidoc
…detection rule execution failure (#1160) (#1218) * First draft * Adds to both rule creation and troubleshooting topics * Adds new screenshots to highlight the correct feature to use * Update rule-start-ml-job.png * Corrects name of custom query rule * Update docs/troubleshooting/detections/detection-rules.asciidoc Co-authored-by: Janeen Mikell-Straughn <57149392+jmikell821@users.noreply.github.com> Co-authored-by: Janeen Mikell-Straughn <57149392+jmikell821@users.noreply.github.com> (cherry picked from commit b91a2a0) Co-authored-by: Joe Peeples <joe.peeples@elastic.co>
… detection rule execution failure (#1160) (#1219) * First draft * Adds to both rule creation and troubleshooting topics * Adds new screenshots to highlight the correct feature to use * Update rule-start-ml-job.png * Corrects name of custom query rule * Update docs/troubleshooting/detections/detection-rules.asciidoc Co-authored-by: Janeen Mikell-Straughn <57149392+jmikell821@users.noreply.github.com> Co-authored-by: Janeen Mikell-Straughn <57149392+jmikell821@users.noreply.github.com> (cherry picked from commit b91a2a0) Co-authored-by: Joe Peeples <joe.peeples@elastic.co>
… detection rule execution failure (#1160) (#1220) * First draft * Adds to both rule creation and troubleshooting topics * Adds new screenshots to highlight the correct feature to use * Update rule-start-ml-job.png * Corrects name of custom query rule * Update docs/troubleshooting/detections/detection-rules.asciidoc Co-authored-by: Janeen Mikell-Straughn <57149392+jmikell821@users.noreply.github.com> Co-authored-by: Janeen Mikell-Straughn <57149392+jmikell821@users.noreply.github.com> (cherry picked from commit b91a2a0) Co-authored-by: Joe Peeples <joe.peeples@elastic.co>
…e execution failure (elastic#1160) * First draft * Adds to both rule creation and troubleshooting topics * Adds new screenshots to highlight the correct feature to use * Update rule-start-ml-job.png * Corrects name of custom query rule * Update docs/troubleshooting/detections/detection-rules.asciidoc Co-authored-by: Janeen Mikell-Straughn <57149392+jmikell821@users.noreply.github.com> Co-authored-by: Janeen Mikell-Straughn <57149392+jmikell821@users.noreply.github.com> # Conflicts: # docs/troubleshooting/detections/detection-rules.asciidoc
… detection rule execution failure (#1160) (#1222) * Provide more details on how to start ML job to avoid ML detection rule execution failure (#1160) * First draft * Adds to both rule creation and troubleshooting topics * Adds new screenshots to highlight the correct feature to use * Update rule-start-ml-job.png * Corrects name of custom query rule * Update docs/troubleshooting/detections/detection-rules.asciidoc Co-authored-by: Janeen Mikell-Straughn <57149392+jmikell821@users.noreply.github.com> Co-authored-by: Janeen Mikell-Straughn <57149392+jmikell821@users.noreply.github.com> # Conflicts: # docs/troubleshooting/detections/detection-rules.asciidoc * Rearrange template-script and troubleshooting-intro
@jmikell821 I provided feedback to @joepeeples and one addition I would make is to add a section if this does not resolve the user's issue to reach out to our community discuss.elastic.co or Elastic Community Slack channel (elasticstack.slack.com) |
Addresses #1137.
Preview pages: