|
1 | 1 | [role="xpack"] |
2 | 2 | [[machine-learning-integration]] |
3 | | -=== integration |
| 3 | +=== Machine learning integration |
4 | 4 |
|
5 | 5 | ++++ |
6 | 6 | <titleabbrev>Integrate with machine learning</titleabbrev> |
7 | 7 | ++++ |
8 | 8 |
|
9 | | -The Machine Learning integration initiates a new job predefined to calculate anomaly scores on APM transaction durations. |
10 | | -Jobs can be created per transaction type, and are based on the service's average response time. |
| 9 | +The Machine learning integration initiates a new job predefined to calculate anomaly scores on APM transaction durations. |
| 10 | +With this integration, you can quickly pinpoint anomalous transactions and see the health of |
| 11 | +any upstream and downstream services. |
11 | 12 |
|
12 | | -After a machine learning job is created, results are shown in two places: |
| 13 | +Machine learning jobs are created per environment, and are based on a service's average response time. |
| 14 | +Because jobs are created at the environment level, |
| 15 | +you can add new services to your existing environments without the need for additional machine learning jobs. |
13 | 16 |
|
14 | | -The transaction duration graph will show the expected bounds and add an annotation when the anomaly score is 75 or above. |
| 17 | +After a machine learning job is created, results are shown in two places: |
15 | 18 |
|
| 19 | +* The transaction duration chart will show the expected bounds and add an annotation when the anomaly score is 75 or above. |
| 20 | ++ |
16 | 21 | [role="screenshot"] |
17 | 22 | image::apm/images/apm-ml-integration.png[Example view of anomaly scores on response times in the APM app] |
18 | 23 |
|
19 | | -Service maps will display a color-coded anomaly indicator based on the detected anomaly score. |
20 | | - |
| 24 | +* Service maps will display a color-coded anomaly indicator based on the detected anomaly score. |
| 25 | ++ |
21 | 26 | [role="screenshot"] |
22 | 27 | image::apm/images/apm-service-map-anomaly.png[Example view of anomaly scores on service maps in the APM app] |
23 | 28 |
|
24 | 29 | [float] |
25 | 30 | [[create-ml-integration]] |
26 | | -=== Create a new machine learning job |
| 31 | +=== Enable anomaly detection |
| 32 | + |
| 33 | +To enable machine learning anomaly detection: |
| 34 | + |
| 35 | +. From the Services overview, Traces overview, or Service Map tab, |
| 36 | +select **Anomaly detection**. |
| 37 | + |
| 38 | +. Click **Create ML Job**. |
27 | 39 |
|
28 | | -To enable machine learning anomaly detection, first choose a service to monitor. |
29 | | -Then, select **Integrations** > **Enable ML anomaly detection** and click **Create job**. |
| 40 | +. Machine learning jobs are created at the environment level. |
| 41 | +Select all of the service environments that you want to enable anomaly detection in. |
| 42 | +Anomalies will surface for all services and transaction types within the selected environments. |
| 43 | + |
| 44 | +. Click **Create Jobs**. |
30 | 45 |
|
31 | 46 | That's it! After a few minutes, the job will begin calculating results; |
32 | | -it might take additional time for results to appear on your graph. |
33 | | -Jobs can be managed in *Machine Learning jobs management*. |
| 47 | +it might take additional time for results to appear on your service maps. |
| 48 | +Existing jobs can be managed in *Machine Learning jobs management*. |
34 | 49 |
|
35 | 50 | APM specific anomaly detection wizards are also available for certain Agents. |
36 | 51 | See the machine learning {ml-docs}/ootb-ml-jobs-apm.html[APM anomaly detection configurations] for more information. |
| 52 | + |
| 53 | +[float] |
| 54 | +[[warning-ml-integration]] |
| 55 | +=== Anomaly detection warning |
| 56 | + |
| 57 | +To make machine learning as easy as possible to set up, |
| 58 | +the APM app will warn you when filtered to an environment without a machine learning job. |
| 59 | + |
| 60 | +[role="screenshot"] |
| 61 | +image::apm/images/apm-anomaly-alert.png[Example view of anomaly alert in the APM app] |
0 commit comments