Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DOCS] Deprecate monitor settings #30004

Merged
merged 1 commit into from
Feb 5, 2019
Merged

[DOCS] Deprecate monitor settings #30004

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 9 additions & 2 deletions docs/settings/monitoring-settings.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
[role="xpack"]
[[monitoring-settings-kb]]
=== Monitoring Settings in Kibana
=== Monitoring settings in Kibana
++++
<titleabbrev>Monitoring Settings</titleabbrev>
<titleabbrev>Monitoring settings</titleabbrev>
++++

By default, the Monitoring application is enabled, but data collection
Expand Down Expand Up @@ -44,6 +44,13 @@ you to use a single {kib} instance to search and visualize data in your
production cluster as well as monitor data sent to a dedicated monitoring
cluster.

`xpack.monitoring.elasticsearch.url`::
Specifies the location of the {es} cluster where your monitoring data is stored.
By default, this is the same as the `elasticsearch.url`. This setting enables
you to use a single {kib} instance to search and visualize data in your
production cluster as well as monitor data sent to a dedicated monitoring
cluster. deprecated[6.6.0,Replaced by `xpack.monitoring.elasticsearch.hosts`]

`xpack.monitoring.elasticsearch.username`::
Specifies the user ID that {kib} uses for authentication when it retrieves data
from the monitoring cluster. If not set, {kib} uses the value of the
Expand Down