add APM integrate with ML

Author: mdbirnstiehl

raw-migrated-files/observability-docs/observability/apm-anomaly-rule.md

@@ -6,7 +6,7 @@ navigation_title: "APM Anomaly"
 
 
 ::::{important}
-To use the APM Anomaly rule, you have to enable [machine learning](../../../solutions/observability/apps/integrate-with-machine-learning.md#create-ml-integration), which requires an [appropriate license](https://www.elastic.co/subscriptions).
+To use the APM Anomaly rule, you have to enable [machine learning](../../../solutions/observability/apps/integrate-with-machine-learning.md#observability-apm-integrate-with-machine-learning-enable-anomaly-detection), which requires an [appropriate license](https://www.elastic.co/subscriptions).
 
 ::::
 

raw-migrated-files/observability-docs/observability/apm-machine-learning-integration.md

@@ -66,6 +66,6 @@ To make machine learning as easy as possible to set up, the Applications UI will
 
 After enabling anomaly detection, service health may display as "Unknown". Here are some reasons why this can occur:
 
-1. No machine learning job exists. See [Enable anomaly detection](../../../solutions/observability/apps/integrate-with-machine-learning.md#create-ml-integration) to enable anomaly detection and create a machine learning job.
+1. No machine learning job exists. See [Enable anomaly detection](../../../solutions/observability/apps/integrate-with-machine-learning.md#observability-apm-integrate-with-machine-learning-enable-anomaly-detection) to enable anomaly detection and create a machine learning job.
 2. There is no machine learning data for the job. If you just created the machine learning job you’ll need to wait a few minutes for data to be available. Alternatively, if the service or its enviroment are new, you’ll need to wait for more trace data.
 3. No "request" or "page-load" transaction type exists for this service; service health is only available for these transaction types.

solutions/observability/apps/integrate-with-machine-learning.md

@@ -4,17 +4,51 @@ mapped_urls:
   - https://www.elastic.co/guide/en/serverless/current/observability-apm-integrate-with-machine-learning.html
 ---
 
-# Integrate with machine learning
+# Integrate with machine learning [observability-apm-integrate-with-machine-learning]
 
-% What needs to be done: Align serverless/stateful
+::::{important}
+Using machine learning requires an [appropriate license](https://www.elastic.co/subscriptions).
 
-% Use migrated content from existing pages that map to this page:
+::::
 
-% - [ ] ./raw-migrated-files/observability-docs/observability/apm-machine-learning-integration.md
-% - [ ] ./raw-migrated-files/docs-content/serverless/observability-apm-integrate-with-machine-learning.md
+The Machine learning integration initiates a new job predefined to calculate anomaly scores on APM transaction durations. With this integration, you can quickly pinpoint anomalous transactions and see the health of any upstream and downstream services.
 
-% Internal links rely on the following IDs being on this page (e.g. as a heading ID, paragraph ID, etc):
+Machine learning jobs are created per environment and are based on a service’s average response time. Because jobs are created at the environment level, you can add new services to your existing environments without the need for additional machine learning jobs.
 
-$$$create-ml-integration$$$
+Results from machine learning jobs are shown in multiple places throughout the Applications UI:
 
-$$$observability-apm-integrate-with-machine-learning-enable-anomaly-detection$$$
+* The **Services overview** provides a quick-glance view of the general health of all of your services.
+* The transaction duration chart will show the expected bounds and add an annotation when the anomaly score is 75 or above.
+* Service Maps will display a color-coded anomaly indicator based on the detected anomaly score.
+
+    :::{image} ../../../images/observability-apm-service-map-anomaly.png
+    :alt: Example view of anomaly scores on service maps in the Applications UI
+    :class: screenshot
+    :::
+
+
+## Enable anomaly detection [observability-apm-integrate-with-machine-learning-enable-anomaly-detection]
+
+To enable machine learning anomaly detection:
+
+1. In your {{obs-serverless}} project or {{kib}}, go to any **Applications** page.
+2. Click **Anomaly detection**.
+3. Click **Create Job**.
+4. Machine learning jobs are created at the environment level. Select all of the service environments that you want to enable anomaly detection in. Anomalies will surface for all services and transaction types within the selected environments.
+5. Click **Create Jobs**.
+
+That’s it! After a few minutes, the job will begin calculating results; it might take additional time for results to appear on your service maps. To manage existing jobs, click **Manage jobs** (or go to **Machine learning** → **Jobs**).
+
+
+## Anomaly detection warning [observability-apm-integrate-with-machine-learning-anomaly-detection-warning]
+
+To make machine learning as easy as possible to set up, Elastic will warn you when filtered to an environment without a machine learning job.
+
+
+## Unknown service health [observability-apm-integrate-with-machine-learning-unknown-service-health]
+
+After enabling anomaly detection, service health may display as "Unknown". Here are some reasons why this can occur:
+
+1. No machine learning job exists. See [Enable anomaly detection](../../../solutions/observability/apps/integrate-with-machine-learning.md#observability-apm-integrate-with-machine-learning-enable-anomaly-detection) to enable anomaly detection and create a machine learning job.
+2. There is no machine learning data for the job. If you just created the machine learning job you’ll need to wait a few minutes for data to be available. Alternatively, if the service or its environment are new, you’ll need to wait for more trace data.
+3. No "request" or "page-load" transaction type exists for this service; service health is only available for these transaction types.