github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-23 17:28:26 -04:00
Code Issues Projects Releases Packages Wiki Activity

[APM] docs: explain unknown service health (#139672) (#139777)

Browse source 
* Update machine-learning.asciidoc

* Update docs/apm/machine-learning.asciidoc

Co-authored-by: Giorgos Bamparopoulos <georgios.bamparopoulos@elastic.co>

Co-authored-by: Giorgos Bamparopoulos <georgios.bamparopoulos@elastic.co>
(cherry picked from commit 4c281a8995)

Co-authored-by: Brandon Morelli <brandon.morelli@elastic.co>
This commit is contained in:
Kibana Machine 2022-08-30 19:02:23 -04:00 • committed by GitHub
parent d5c70d2723
commit cf5e7b3240
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 11 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

12
docs/apm/machine-learning.asciidoc
View file

@ -60,4 +60,14 @@ To make machine learning as easy as possible to set up,
the APM app will warn you when filtered to an environment without a machine learning job.
[role="screenshot"]
image::apm/images/apm-anomaly-alert.png[Example view of anomaly alert in the APM app]
image::apm/images/apm-anomaly-alert.png[Example view of anomaly alert in the APM app]
[float]
[[unkown-ml-integration]]
=== Unknown service health
After enabling anomaly detection, service health may display as "Unknown". There are three reasons why this can occur:
1. No machine learning job exists. See <<create-ml-integration>> 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.