[DOCS] Adds known monitoring issue to release notes (#34391)

This commit is contained in:
Lisa Cawley 2019-04-03 09:57:44 -07:00 committed by GitHub
parent 6468911fa4
commit 9bee0f3a70
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 17 additions and 1 deletions

View file

@ -18,6 +18,18 @@ This section summarizes the changes in each release.
--
[[release-notes-7.0.0-rc2]]
== {kib} 7.0.0-rc2
coming[7.0.0]
[float]
=== Known issues
Monitoring::
* If you have a version 7.0 monitoring cluster, a version 6.7 production
cluster and {kib} version 6.7.0 or 6.7.1, you cannot see the monitoring data in
{kib}. {issue}34357[#34357]
[[release-notes-7.0.0-rc2]]
@ -544,7 +556,6 @@ if the field is switched, and then switched back to the previous field {pull}251
[[release-notes-7.0.0-rc1]]
== {kib} 7.0.0-rc1
[float]
[[breaking-7.0.0-rc1]]
=== Breaking changes

View file

@ -32,6 +32,11 @@ The *Monitoring* page in {kib} is empty.
*Resolution:*
. Confirm that you are not using {kib} 6.7.0 or 6.7.1. If you have a version 7.0
monitoring cluster, a version 6.7 production cluster and {kib} version 6.7.0 or
6.7.1, you cannot see the monitoring data in {kib}. For more information, see
https://github.com/elastic/kibana/issues/34357
. Confirm that {kib} is seeking monitoring data from the appropriate {es} URL.
By default, data is retrieved from the cluster specified in the
`elasticsearch.hosts` setting in the `kibana.yml` file. If you want to retrieve it