Clean up raw-migrated-files

.github/CODEOWNERS

@@ -74,9 +74,6 @@
 /troubleshoot/observability/                @elastic/ski-docs
 /troubleshoot/security/                     @elastic/ski-docs
 
-# Raw migrated files
-/raw-migrated-files/                        @elastic/admin-docs
-
 # Legacy serverless docs
 /serverless/                                @elastic/admin-docs
 /serverless/serverless-changelog.asciidoc   @elastic/docs

deploy-manage/monitor/monitoring-data/configure-stack-monitoring-alerts.md

@@ -32,7 +32,10 @@ When you open **{{stack-monitor-app}}** for the first time, you will be asked to
 
 If you denied creation of the default rules initially, or to recreate any deleted rules, then you can trigger {{kib}} to create the rules by going to **Alerts and rules** > **Create default rules**.
 
-To receive external notifications for these alerts, you need to [configure a connector](/deploy-manage/manage-connectors.md) and modify the relevant rule to use the connector. If you're using {{ech}}, then you can use the default `Elastic-Cloud-SMTP` email connector or configure your own.
+To receive external notifications for these alerts, you need to set up a connector and attach it to one or more rules:
+
+1. [Configure a connector](/deploy-manage/manage-connectors.md) for the notification channel you want to use, such as [Slack](kibana://reference/connectors-kibana/slack-action-type.md), [email](kibana://reference/connectors-kibana/email-action-type.md), [PagerDuty](kibana://reference/connectors-kibana/pagerduty-action-type.md), or any of the other [supported connectors](kibana://reference/connectors-kibana.md). On {{ech}} deployments, the default `Elastic-Cloud-SMTP` email connector is available without additional setup.
+2. [Modify a Stack Monitoring rule](#modify-rules) and select the connector under the **Actions** section.
 
 ::::{note}
 Some action types are subscription features, while others are free. For a comparison of the Elastic subscription levels, see the alerting section of the [Subscriptions page](https://www.elastic.co/subscriptions).

deploy-manage/monitor/monitoring-data/visualizing-monitoring-data.md

@@ -27,6 +27,11 @@ Review the following topics to learn more about the metrics and visualizations a
 
 From the **Stack Monitoring** section, you can also configure [{{kib}} alerts](/deploy-manage/monitor/monitoring-data/configure-stack-monitoring-alerts.md) for stack monitoring metrics.
 
+To investigate logs alongside the metrics shown in Stack Monitoring, open your shipped logs in [Discover](/explore-analyze/discover.md) and filter by log level and time range to identify failures or anomalies that correlate with the metrics. {{kib}} provides a [dedicated logs experience in Discover](/solutions/observability/logs/discover-logs.md) for data that matches `logs-*` indices. The data view you query depends on how you ship logs:
+
+* On {{ech}} and {{ece}}, use the `elastic-cloud-logs-*` data view, which is set up automatically when you [enable logging and monitoring](/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md).
+* On {{eck}} and self-managed deployments, use the data view that matches your log shipping setup, such as the {{filebeat}} or {{agent}} output indices. For details, refer to [](/deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md) or [](/deploy-manage/monitor/stack-monitoring/elasticsearch-monitoring-self-managed.md).
+
 If you're having trouble accessing your monitoring data within the **Stack Monitoring** section, then refer to [](/deploy-manage/monitor/monitoring-data/monitor-troubleshooting.md).
 
 If you enable monitoring across the {{stack}}, each monitored component is considered unique based on its persistent UUID, which is written to the [`path.data`](kibana://reference/configuration-reference/general-settings.md#path-data) directory when the node or instance starts.

deploy-manage/monitor/stack-monitoring/_snippets/consumption-next-steps.md

@@ -0,0 +1,4 @@
+After your monitoring data is flowing, learn more about what you can do with it:
+
+* [Visualize monitoring data](/deploy-manage/monitor/monitoring-data/visualizing-monitoring-data.md): view {{es}}, {{ls}}, {{kib}}, and {{beats}} health and performance metrics in the **{{stack-monitor-app}}** application in {{kib}}, and investigate shipped logs alongside those metrics in Discover.
+* [Configure stack monitoring alerts](/deploy-manage/monitor/monitoring-data/configure-stack-monitoring-alerts.md): set up notifications for cluster health, resource utilization, and error conditions through connectors such as Slack, email, or PagerDuty.

deploy-manage/monitor/stack-monitoring/collecting-log-data-with-filebeat.md

@@ -125,3 +125,8 @@ If you’re using {{agent}}, do not deploy {{filebeat}} for log collection. Inst
 
 10. [View the monitoring data in {{kib}}](kibana-monitoring-data.md).
 
+## Next steps
+
+:::{include} /deploy-manage/monitor/stack-monitoring/_snippets/consumption-next-steps.md
+:::
+

deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-elastic-agent.md

@@ -53,3 +53,8 @@ To collect {{es}} monitoring data, add an {{es}} integration to an {{agent}} and
 
 9. Wait a minute or two until incoming data is confirmed.
 10. [View the monitoring data in {{kib}}](kibana-monitoring-data.md).
+
+## Next steps
+
+:::{include} /deploy-manage/monitor/stack-monitoring/_snippets/consumption-next-steps.md
+:::

deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-metricbeat.md

@@ -121,3 +121,8 @@ Want to use {{agent}} instead? Refer to [Collecting monitoring data with {{agent
 6. [Start {{metricbeat}}](beats://reference/metricbeat/metricbeat-starting.md) on each node.
 7. [View the monitoring data in {{kib}}](kibana-monitoring-data.md).
 
+## Next steps
+
+:::{include} /deploy-manage/monitor/stack-monitoring/_snippets/consumption-next-steps.md
+:::
+

deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md

@@ -155,3 +155,8 @@ Check the respective product documentation for more information about the loggin
 * $$$cross-region-monitor$$$ Monitoring across regions is not supported. If you need to move your existing monitoring to the same region, you can do a reindex or create a new deployment and select the snapshot from the old deployment.
 * The logs shipped to a monitoring cluster use an ILM managed data stream (`elastic-cloud-logs-<version>`). If you need to delete indices due to space, do not delete the current `is_write_enabled: true` index.
 * When sending metrics to a dedicated monitoring deployment, the graph for IO Operations Rate(/s) is blank. This is due to the fact that this graph actually contains metrics from of all of the virtualized resources from the provider.
+
+## Next steps [next-steps]
+
+:::{include} /deploy-manage/monitor/stack-monitoring/_snippets/consumption-next-steps.md
+:::

deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md

@@ -197,3 +197,8 @@ spec:
           env:
           - foo: bar
 ```
+
+## Next steps
+
+:::{include} /deploy-manage/monitor/stack-monitoring/_snippets/consumption-next-steps.md
+:::

deploy-manage/monitor/stack-monitoring/es-legacy-collection-methods.md

@@ -157,7 +157,3 @@ To learn about monitoring in general, see [Monitor a cluster](../../monitor.md).
 7. [View the monitoring data in {{kib}}](kibana-monitoring-data.md).
 
 
-
-
-
-

deploy-manage/monitor/stack-monitoring/kibana-monitoring-elastic-agent.md

@@ -56,3 +56,8 @@ To collect {{kib}} monitoring data, add a {{kib}} integration to an {{agent}} an
 
 9. Wait a minute or two until incoming data is confirmed.
 10. [View the monitoring data in {{kib}}](/deploy-manage/monitor/stack-monitoring/kibana-monitoring-data.md).
+
+## Next steps
+
+:::{include} /deploy-manage/monitor/stack-monitoring/_snippets/consumption-next-steps.md
+:::

deploy-manage/monitor/stack-monitoring/kibana-monitoring-metricbeat.md

@@ -155,3 +155,8 @@ To learn about monitoring in general, refer to [](/deploy-manage/monitor/stack-m
 9. [Start {{metricbeat}}](beats://reference/metricbeat/metricbeat-starting.md).
 10. [View the monitoring data in {{kib}}](/deploy-manage/monitor/stack-monitoring/kibana-monitoring-data.md).
 
+## Next steps
+
+:::{include} /deploy-manage/monitor/stack-monitoring/_snippets/consumption-next-steps.md
+:::
+

docset.yml

@@ -6,7 +6,6 @@ features:
 
 exclude:
   - 'README.md'
-  - 'raw-migrated-files/**'
   - 'changelog/**'
   - 'releases/**'