github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-24 09:48:58 -04:00
Code Issues Projects Releases Packages Wiki Activity

[DOCS] Updates title for Stack Monitoring app (#39814)

Browse source
This commit is contained in:
Lisa Cawley 2019-06-28 10:31:10 -07:00 • committed by GitHub
parent d0f0315a20
commit b519f36333
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
8 changed files with 16 additions and 16 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/monitoring/beats-details.asciidoc
View file

@ -5,8 +5,8 @@
<titleabbrev>Beats Metrics</titleabbrev>
++++
If you are monitoring Beats, the *Monitoring* page in {kib} contains a panel for
Beats in the cluster overview. added[6.2.0]
If you are monitoring Beats, the *Stack Monitoring* page in {kib} contains a
panel for Beats in the cluster overview.
[role="screenshot"]
image::monitoring/images/monitoring-beats.jpg["Monitoring Beats",link="images/monitoring-beats.jpg"]

8
docs/monitoring/cluster-alerts.asciidoc
View file

@ -2,8 +2,8 @@
[[cluster-alerts]]
== Cluster Alerts
The *Monitoring > Clusters* page in {kib} summarizes the status of your Elastic
stack. You can drill down into the metrics to view more information about your
The *Stack Monitoring > Clusters* page in {kib} summarizes the status of your
{stack}. You can drill down into the metrics to view more information about your
cluster and specific nodes, instances, and indices.
The Top Cluster Alerts shown on the Clusters page notify you of
@ -36,7 +36,7 @@ soon the expiration date is:
The 60-day and 30-day thresholds are skipped for Trial licenses, which are only
valid for 30 days.
Monitoring checks the cluster alert conditions every minute. Cluster
The {monitor-features} check the cluster alert conditions every minute. Cluster
alerts are automatically dismissed when the condition is resolved.
include::cluster-alerts-license.asciidoc[]
@ -47,7 +47,7 @@ include::cluster-alerts-license.asciidoc[]
To receive email notifications for the Cluster Alerts:
1. Configure an email account as described in
{xpack-ref}/actions-email.html#configuring-email[Configuring Email Accounts].
{stack-ov}/actions-email.html#configuring-email[Configuring Email Accounts].
2. Configure the `xpack.monitoring.cluster_alerts.email_notifications.email_address` setting in `kibana.yml` with your email address.
Email notifications are sent only when Cluster Alerts are triggered and resolved.

2
docs/monitoring/index.asciidoc
View file

@ -1,6 +1,6 @@
[role="xpack"]
[[xpack-monitoring]]
= Monitoring
= Stack Monitoring
[partintro]
--

2
docs/monitoring/logstash-details.asciidoc
View file

@ -6,7 +6,7 @@
++++
If you are monitoring Logstash nodes, click **Overview** in the Logstash section
of the *Monitoring* page in {kib}. You can view the overall health of the
of the *Stack Monitoring* page in {kib}. You can view the overall health of the
Logstash nodes.
image::monitoring/images/monitoring-logstash-overview.jpg["Logstash Overview",link="images/monitoring-logstash-overview.jpg"]

4
docs/monitoring/monitoring-kibana.asciidoc
View file

@ -36,8 +36,8 @@ By default, if you are running {kib} locally, go to `http://localhost:5601/`.
If {es} {security-features} are enabled, log in.
--
... In the side navigation, click *Monitoring*. If data collection is disabled,
you are prompted to turn it on.
... In the side navigation, click *Stack Monitoring*. If data collection is
disabled, you are prompted to turn it on.
** From the Console or command line, set `xpack.monitoring.collection.enabled`
to `true` on the production cluster. +

4
docs/monitoring/monitoring-metricbeat.asciidoc
View file

@ -57,8 +57,8 @@ If you are running {kib} locally, go to `http://localhost:5601/`.
If the Elastic {security-features} are enabled, log in.
--
... In the side navigation, click *Monitoring*. If data collection is disabled,
you are prompted to turn it on.
... In the side navigation, click *Stack Monitoring*. If data collection is
disabled, you are prompted to turn it on.
** From the Console or command line, set `xpack.monitoring.collection.enabled`
to `true` on the production cluster. +

4
docs/monitoring/monitoring-troubleshooting.asciidoc
View file

@ -14,7 +14,7 @@ answers for frequently asked questions related to the {kib} {monitor-features}.
*Symptoms:*
The following error appears in a banner at the top of the screen in {kib} on the
*Monitoring > Clusters* page:
*Stack Monitoring > Clusters* page:
`You can't view the "<my_cluster>" cluster because the license information is invalid.`
*Resolution:*
@ -28,7 +28,7 @@ To resolve this issue, upgrade {kib} to 6.3 or later. See
*Symptoms:*
The *Monitoring* page in {kib} is empty.
The *Stack Monitoring* page in {kib} is empty.
*Resolution:*

4
docs/monitoring/viewing-metrics.asciidoc
View file

@ -7,7 +7,7 @@
After you collect monitoring data for one or more products in the {stack}, you
can configure {kib} to retrieve that information and display it in on the
*Monitoring* page.
*Stack Monitoring* page.
At a minimum, you must have monitoring data for the {es} production cluster.
Once that data exists, {kib} can display monitoring data for other products in
@ -74,7 +74,7 @@ By default, if you are running {kib} locally, go to `http://localhost:5601/`.
If the Elastic {security-features} are enabled, log in.
--
. In the side navigation, click *Monitoring*.
. In the side navigation, click *Stack Monitoring*.
+
--
If data collection is disabled, you are prompted to turn on data collection.