[DOCS] Response ops 8.19 updates (#229547)

## Summary

Updates the documentation for responseOps dashboards to reflect two new
features. 9.1 version of these docs updates are in
elastic/docs-content#2165 and
elastic/docs-content#2139


### Checklist

Check the PR satisfies following conditions. 

Reviewers should verify this PR satisfies this list as well.

- [ ] 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/main/src/platform/packages/shared/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [ ] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
- [ ] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.

---------

Co-authored-by: Nastasha Solomon <[email protected]>

Author: benironside

docs/user/dashboard/alerts-panel.asciidoc

@@ -0,0 +1,36 @@
+[[alert-panels]]
+= Alert panels
+
+To view alerts in a dashboard, add *Alerts* panels that show selected alerts. Each panel can display either *Observability* or *Security* alerts, filtered by the rule tags and rule types you select.
+
+[[create-alerts-panel]]
+[discrete]
+== Create an alerts panel
+
+. From your dashboard, select *Add panel*.
+. In the *Add panel* flyout, select *Alerts*. The configuration flyout appears.
+. ({stack} deployments only) Under *Solution*, select either *Observability* or *Security* to specify the type of alerts you want to display.
+. Under *Filter by*, select either *Rule tags* or *Rule types*.
+. (Optional) To use both types of filters, first define one filter, then use the boolean *+ OR* or *+ AND* options that appear to define the second filter.
+. Click *Save*. Your panel appears on the dashboard.
+
+[[alert-panel-actions]]
+[discrete]
+== Take action on alerts
+
+There are several actions you can take on alerts in the alerts panel. Under *Actions*, click the three dots next to an alert to open a menu with the following options:
+
+* *View rule details*: Open the details page for the rule that created the alert.
+* *View alert details*: Open the alert details flyout.
+* (*Active* rules only) *Mark as untracked*: Change the alert's status from *Active* to *Untracked*.
+* (*Active* rules only) *Mute*: Mute alerts from the associated rule.
+
+[[edit-alerts-panel]]
+[discrete]
+== Edit an alerts panel
+
+To edit an existing alerts panel, hover over the panel. Three buttons appear:
+
+* *Edit* (pencil): Update which alerts appear in the panel.
+* *Settings* (gear): Update the panel's title or description, or add a custom time range.
+* *More actions* (three boxes): Duplicate, maximize, copy to another dashboard, or remove the panel.

docs/user/dashboard/create-visualizations.asciidoc

@@ -20,6 +20,9 @@ Use one of the editors to create visualizations of your data. Each editor offers
 | <<maps,Maps>>
 | Create beautiful displays of your geographical data
 
+| <<alert-panels,Alerts>> 
+| View Observability or Security alerts in your dashboard
+
 | <<field-statistics-dashboard,Field statistics>>
 | Add a field statistics view of your data to your dashboards
 
@@ -240,6 +243,29 @@ image::images/esql-visualization-customization-options.png[Appearance customizat
 
 . Return to the previous menu, then **Apply and close** the configuration to save your changes.
 
+[[create-alert-from-esql-viz]]
+[float]
+== Create an alert from your {esql} visualization
+
+Once you've created an {esql} panel, you can create an {es} threshold rule directly from the visualization panel based on the data it displays. When you do this, the rule query is automatically generated and either describes the data and sets a specific threshold, or describes the data without setting a specific threshold.
+
+[NOTE]
+====
+{elastic-sec} rule types are not supported.
+====
+
+To create a rule with the threshold pre-specified:
+
+* Right-click a data point in the visualization and click *Add alert rule*. This opens the *Create rule* flyout. The generated query will define a threshold that corresponds to the data point you selected.
+* {kib-ref}/rule-type-es-query.html[Configure] your {es} rule.
+
+To create a rule without the threshold pre-specified:
+
+* Open the *More actions* (three dots) menu in the upper right of the panel and select *Add alert rule*. This opens the *Create rule* flyout. The generated query will define a threshold that corresponds to the data point you selected.
+* {kib-ref}/rule-type-es-query.html[Configure] your {es} rule.
+
+include::alerts-panel.asciidoc[][leveloffset=-1]
+
 [[maps-visualizations]]
 == Maps
 
@@ -328,6 +354,7 @@ When importing a dashboard with an image panel, and the image file is unavailabl
 
 include::links-panel.asciidoc[leveloffset=-1]
 
+
 [[legacy-editors]]
 == Legacy editors