maxmustermann/kibana
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Change Configuration button to Settings tab (#47960) (#49459)

Browse source
This commit is contained in:
Marjorie Jones 2019-10-28 11:33:56 +00:00 committed by GitHub
parent 5a7f41e3de
commit 35c2fe6a8b
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
3 changed files with 37 additions and 35 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
docs/infrastructure/infra-ui.asciidoc
View file

@ -62,29 +62,30 @@ Select *Auto-refresh* to keep up-to-date metrics information coming in, or *Stop
[[infra-configure-source]]
=== Configure the data to use for your metrics
If your metrics have custom index patterns, or use non-default field settings, you can override the default configuration settings.
The default source configuration for metrics is specified in the {kibana-ref}/infrastructure-ui-settings-kb.html[Metrics app settings] in the {kibana-ref}/settings.html[Kibana configuration file].
The default configuration uses the `metricbeat-*` index pattern to query the data.
The default configuration also defines field settings for things like timestamps and container names.
If your metrics have custom index patterns, or use non-default field settings, you can override the default settings.
Click *Configuration* to change the settings.
This opens the *Configure source* fly-out dialog.
To change the configuration settings, click the *Settings* tab.
NOTE: These settings are shared with logs. Changes you make here may also affect the settings used by the *Logs* app.
In the *Configure source* dialog, you can change the following values:
In the *Settings* tab, you can change the values in these sections:
* *Name*: the name of the source configuration
* *Indices*: the index pattern or patterns in the Elasticsearch indices to read metrics data and log data
from
* *Indices*: the index pattern or patterns in the Elasticsearch indices to read metrics data and log data from
* *Fields*: the names of specific fields in the indices that are used to query and interpret the data correctly
When you have completed your changes, click *Apply*.
If the fields are greyed out and cannot be edited, you may not have sufficient privileges to change the source configuration.
For more information see <<xpack-security-authorization>>.
TIP: If <<xpack-spaces>> are enabled in your Kibana instance, any configuration changes you make here are specific to the current space.
You can make different subsets of data available by creating multiple spaces with different data source configurations.
TIP: If you don't see the *Configuration* option, you may not have sufficient privileges to change the source configuration.
For more information see <<xpack-security-authorization>>.
[float]
[[infra-metrics-explorer]]
=== Visualize multiple metrics in Metrics Explorer

44
docs/logs/configuring.asciidoc
View file

@ -1,50 +1,46 @@
[role="xpack"]
[[xpack-logs-configuring]]
:ecs-link: {ecs-ref}[Elastic Common Schema (ECS)]
:ecs-base-link: {ecs-ref}/ecs-base.html[base]
== Configuring the Logs data
The default source configuration for logs is specified in the {kibana-ref}/logs-ui-settings-kb.html[Logs app settings] in the {kibana-ref}/settings.html[Kibana configuration file].
The default configuration uses the `filebeat-*` index pattern to query the data.
The default configuration also defines field settings for things like timestamps and container names, and the default columns to show in the logs pane.
The default configuration also defines field settings for things like timestamps and container names, and the default columns to show in the logs stream.
If your logs have custom index patterns, or use non-default field settings, or contain parsed fields which you want to expose as individual columns, you can override the default settings.
Click *Configuration* to change the settings.
This opens the *Configure source* fly-out dialog.
If your logs have custom index patterns, use non-default field settings, or contain parsed fields which you want to expose as individual columns, you can override the default configuration settings.
To change the configuration settings, click the *Settings* tab.
NOTE: These settings are shared with metrics. Changes you make here may also affect the settings used by the *Metrics* app.
TIP: If <<xpack-spaces>> are enabled in your Kibana instance, any configuration changes you make here are specific to the current space.
You can make different subsets of data available by creating multiple spaces with different data source configurations.
TIP: If you don't see the *Configuration* option, you may not have sufficient privileges to change the source configuration.
For more information see <<xpack-security-authorization>>.
[float]
=== Indices and fields tab
In the *Indices and fields* tab, you can change the following values:
In the *Settings* tab, you can change the values in these sections:
* *Name*: the name of the source configuration
* *Indices*: the index pattern or patterns in the Elasticsearch indices to read metrics data and log data from
* *Fields*: the names of specific fields in the indices that are used to query and interpret the data correctly
* *Log columns*: the columns that are shown in the logs stream
[float]
==== Log columns configuration
In the *Log columns* tab you can change the columns that are displayed in the Logs app.
By default the following columns are shown:
By default the logs stream shows following columns:
* *Timestamp*: The timestamp of the log entry from the `timestamp` field.
* *Message*: The message extracted from the document.
The content of this field depends on the type of log message.
If no special log message type is detected, the {ecs-link} field `message` is used.
// ++ add a better link. The actual page location is ecs-base
If no special log message type is detected, the Elastic Common Schema (ECS) {ecs-base-link} field, `message`, is used.
To add a new column, click *Add column*.
To add a new column to the logs stream, in the *Settings* tab, click *Add column*.
In the list of available fields, select the field you want to add.
You can start typing a field name in the search box to filter the field list by that name.
To remove an existing column, click the *Remove this column* icon
image:logs/images/logs-configure-source-dialog-remove-column-button.png[Remove column].
image:logs/images/logs-configure-source-dialog-remove-column-button.png[Remove column].
When you have completed your changes, click *Apply*.
If the fields are greyed out and cannot be edited, you may not have sufficient privileges to change the source configuration.
For more information see <<xpack-security-authorization>>.
TIP: If <<xpack-spaces>> are enabled in your Kibana instance, any configuration changes you make here are specific to the current space.
You can make different subsets of data available by creating multiple spaces with different data source configurations.

9
docs/logs/using.asciidoc
View file

@ -43,6 +43,11 @@ To quickly jump to a nearby point in time, click the minimap timeline to the rig
Click *Customize* to customize the view.
Here, you can set the scale to use for the minimap timeline, choose whether to wrap long lines, and choose your preferred text size.
[float]
=== Configuring the data to use for your logs
If your logs have custom index patterns, use non-default field settings, or contain parsed fields which you want to expose as individual columns, you can <<xpack-logs-configuring, override the default configuration settings>>.
[float]
[[logs-stream]]
=== Stream or pause logs
@ -70,10 +75,10 @@ To highlight a word or phrase in the logs stream, click *Highlights* and enter y
To inspect a log event, hover over it, then click the *View details* icon image:logs/images/logs-view-event.png[View event icon] beside the event.
This opens the *Log event document details* fly-out that shows the fields associated with the log event.
To quickly filter the logs stream by one of the field values, click the *View event with filter* icon image:logs/images/logs-view-event-with-filter.png[View event icon] beside the field.
To quickly filter the logs stream by one of the field values, in the log event details, click the *View event with filter* icon image:logs/images/logs-view-event-with-filter.png[View event icon] beside the field.
This automatically adds a search filter to the logs stream to filter the entries by this field and value.
In the log event details, click *Actions* to see the other actions related to the event.
To see other actions related to the event, in the log event details, click *Actions*.
Depending on the event and the features you have installed and configured, you may also be able to:
* Select *View status in Uptime* to <<uptime-overview, view related uptime information>> in the *Uptime* app.