mirror of
https://github.com/elastic/kibana.git
synced 2025-04-24 09:48:58 -04:00
[DOCS] Add file size setting for Data Visualizer (#64006)
This commit is contained in:
parent
b7f2a010c8
commit
1a6338a314
3 changed files with 19 additions and 12 deletions
|
@ -8,7 +8,6 @@
|
|||
You do not need to configure any settings to use {kib} {ml-features}. They are
|
||||
enabled by default.
|
||||
|
||||
[float]
|
||||
[[general-ml-settings-kb]]
|
||||
==== General {ml} settings
|
||||
|
||||
|
@ -19,3 +18,11 @@ If set to `false` in `kibana.yml`, the {ml} icon is hidden in this {kib}
|
|||
instance. If `xpack.ml.enabled` is set to `true` in `elasticsearch.yml`, however,
|
||||
you can still use the {ml} APIs. To disable {ml} entirely, see the
|
||||
{ref}/ml-settings.html[{es} {ml} settings].
|
||||
|
||||
[[data-visualizer-settings]]
|
||||
==== {data-viz} settings
|
||||
|
||||
`xpack.ml.file_data_visualizer.max_file_size`::
|
||||
Sets the file size limit when importing data in the {data-viz}. The default
|
||||
value is `100MB`. The highest supported value for this setting is `1GB`.
|
||||
|
||||
|
|
Binary file not shown.
Before Width: | Height: | Size: 566 KiB After Width: | Height: | Size: 347 KiB |
|
@ -4,31 +4,31 @@
|
|||
|
||||
[partintro]
|
||||
--
|
||||
As datasets increase in size and complexity, the human effort required to
|
||||
As data sets increase in size and complexity, the human effort required to
|
||||
inspect dashboards or maintain rules for spotting infrastructure problems,
|
||||
cyber attacks, or business issues becomes impractical. Elastic {ml-features}
|
||||
such as {anomaly-detect} and {oldetection} make it easier to notice suspicious
|
||||
activities with minimal human interference.
|
||||
|
||||
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
|
||||
{anomaly-detect}:
|
||||
{kib} includes a free *{data-viz}* 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-viz}* to identify possible fields for {anomaly-detect}:
|
||||
|
||||
[role="screenshot"]
|
||||
image::user/ml/images/ml-data-visualizer-sample.jpg[Data Visualizer for sample flight data]
|
||||
image::user/ml/images/ml-data-visualizer-sample.jpg[{data-viz} for sample flight data]
|
||||
|
||||
experimental[] You can also upload a CSV, NDJSON, or log file (up to 100 MB in
|
||||
size). The *Data Visualizer* identifies the file format and field mappings. You
|
||||
can then optionally import that data into an {es} index.
|
||||
experimental[] You can also upload a CSV, NDJSON, or log file. The *{data-viz}*
|
||||
identifies the file format and field mappings. You can then optionally import
|
||||
that data into an {es} index. To change the default file size limit, see
|
||||
<<data-visualizer-settings>>.
|
||||
|
||||
You need the following permissions to use the Data Visualizer with file upload:
|
||||
You need the following permissions to use the {data-viz} with file upload:
|
||||
|
||||
* cluster privileges: `monitor`, `manage_ingest_pipelines`
|
||||
* index privileges: `read`, `manage`, `index`
|
||||
|
||||
For more information, see {ref}/security-privileges.html[Security privileges]
|
||||
and {ref}/built-in-roles.html[Built-in roles].
|
||||
and {ml-docs}/setup.html[Set up {ml-features}].
|
||||
|
||||
--
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue