Skip to content
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

[8.x] [DE Team][8.16] Case system action being added for rules (backport #5703) #5845

Merged
merged 2 commits into from
Sep 17, 2024

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Sep 17, 2024

NOTE TO SELF: DO NOT MERGE UNTIL 8.16 FF

Contributes to #5457

This PR contains the following changes:

  • Within the ESS and Serverless docs, I removed screenshots of the rule action connectors and response actions. These screenshots don't add significant value to the instructions for selecting an action and need to be frequently maintained.
  • Made the following changes to the Create a detection rule page:
    • Revised step 5 at the start of the page so it reflects that users can set up actions for the rule
    • Changed the title of the alert notifications section from "Set up alert notifications (optional)" to "Set up rule actions (optional)"
    • Added a blurb about the case connector and linked to the connector docs
    • Moved the response actions section one more level down so it's under the "Set up rule actions (optional)" section. This seemed appropriate, seeing that response actions are considered a sub-type of rule actions.

Corresponding Serverless PR: #5615


This is an automatic backport of pull request #5703 done by Mergify.

* First draft

* Fixed header level

(cherry picked from commit 13530ea)
@mergify mergify bot requested a review from a team as a code owner September 17, 2024 17:28
@mergify mergify bot added the backport label Sep 17, 2024
Copy link

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.

@nastasha-solomon nastasha-solomon enabled auto-merge (squash) September 17, 2024 19:54
@nastasha-solomon
Copy link
Contributor

run docs-build

1 similar comment
@lcawl
Copy link
Contributor

lcawl commented Sep 17, 2024

run docs-build

@nastasha-solomon nastasha-solomon merged commit 219e7ae into 8.x Sep 17, 2024
3 checks passed
@mergify mergify bot deleted the mergify/bp/8.x/pr-5703 branch September 17, 2024 23:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants