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

[DOCS] Clarify Data Visualizer limitation (#37143)

Browse source
This commit is contained in:
Lisa Cawley 2019-06-03 08:41:33 -07:00 • committed by lcawl
parent 53d7cf1e20
commit 0fb1f37102
2 changed files with 6 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

7
docs/ml/creating-jobs.asciidoc
View file

@ -44,13 +44,12 @@ These wizards create {ml} jobs, dashboards, searches, and visualizations that
are customized to help you analyze your {auditbeat} and {filebeat} data.
If you are not certain which type of job to create, you can use the
*Data Visualizer* to learn more about your data and to identify possible fields
for {ml} analysis.
*Data Visualizer* to learn more about your data. If your index pattern contains
a time field, it can identify possible fields for {ml} analysis.
[NOTE]
===============================
* If your index pattern does not contain a time field, you cannot use the *Data Visualizer*.
* If your data is located outside of {es}, you cannot use {kib} to create
If your data is located outside of {es}, you cannot use {kib} to create
your jobs and you cannot use {dfeeds} to retrieve your data in real time.
Machine learning analysis is still possible, however, by using APIs to
create and manage jobs and post data to them. For more information, see

5
docs/ml/index.asciidoc
View file

@ -16,8 +16,9 @@ The {ml-features} run in and scale with {es}, and include an
intuitive UI on the {kib} *Machine Learning* page for creating anomaly detection
jobs and understanding results.
If you have a basic license, you can use the *Data Visualizer* to learn more
about the data that you've stored in {es} and to identify possible fields for
If you have a basic license, you can use the *Data Visualizer* to learn more
about your data. In particular, if your data is stored in {es} and contains a
time field, you can use the *Data Visualizer* to identify possible fields for
{ml} analysis:
[role="screenshot"]