search

elastic / kibana

Your window into the Elastic Stack
https://www.elastic.co/products/kibana
Other
19.65k stars 8.23k forks source link

empty page with stack monitoring under basic license with multiple clusters #80647

Open tuckson opened 4 years ago

tuckson commented 4 years ago

**Kibana version: 7.9.1

Elasticsearch version:

**Server OS version: CentOS 7.8

**Browser version: Version 1.15.72 Chromium: 86.0.4240.75 (Official Build) (64-bit)

**Browser OS version: Win10

**Original install method (e.g. download page, yum, from source, etc.): package via yum

Describe the bug: Under a basic license, the stack monitoring page stays empty/white when 2 clusters are connected with stack monitoring set up. Steps to reproduce:

  1. deploy 2 seperate elastic clusters (under basic license) with at least 1 remote cluster node. Do not connect them
  2. On one cluster, set up stack monitoring (in my case elastic nodes are done without metricbeat).
  3. verify it works and data is shown.
  4. connect the clusters to eachother on the repective remote nodes via stack management/remote clusters.
  5. verify the data is still visible on the first cluster and see on the other cluster that the data of that first cluster also is visible.
  6. disconnect the clusters again (otherwise you cannot set up monitoring sine only 1 cluster can be monitored under basic license)
  7. setup monitoring on the second stack as well and verify it is available
  8. connect the clusters again to eachother.
  9. Goto stack monitoring again and experience a plain white page on both clusters.

Expected behavior: I think 9. just happens because under basic license just 1 cluster is allowed. One could argue if, under 5. , the data of that remote cluster should be shown. However I figure there could be use cases for that. But then under 9. When kibana discovers more clusters are monitored and only a basic license is running, it should just revert to the local stack monitoring I think.

Screenshots (if relevant):

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

Any additional context:

elasticmachine commented 4 years ago

Pinging @elastic/stack-monitoring (Team:Monitoring)

chrisronline commented 4 years ago

Thanks for the report @tuckson !

Do you happen to know if there are any errors in any of these places during this testing:

1) Elasticsearch server log 2) Kibana server log 3) Browser developer tools