Kibana: [Stack Monitoring] Unhelpful error message on Cloud

Created on 14 Aug 2019 · 6Comments · Source: elastic/kibana

Some background reading on this issue can be found here.

Note: I have labeled this as a feature since it's unclear that we understood what the intended behavior was in the first place. If people disagree and think it should be classified as a bug, I have no objection to relabling it.

At present, if a user configures a deployment in Elastic Cloud and ships monitoring data to it from a production cluster, visiting the Stack Monitoring link in the production cluster's Kibana instance will display the error below:

62648214-3369eb80-b907-11e9-8a3d-6c229f82b5c3

In the short term, the desired fix is (to quote @skearns64 in the original issue):

[To] have the Stack Monitoring UI check if the cluster is running in Cloud with a remote monitoring cluster, and show a message that monitoring is enabled, and to view the data they will need to go to the [monitoring] Kibana instance of the [production] monitoring cluster. Bonus points as a second step would be to link to that other [monitoring] Kibana.

It's possible that we will need somebody from the Cloud team to help us figure out how to have the Stack Monitoring UI check if the cluster is running in the cloud. (cc: @zanbel and @nachogiljaldo to help us find the right people to work with.)

Stack Monitoring Monitoring bug enhancement

Source

cachedout

All 6 comments

It's possible that we will need somebody from the Cloud team to help us figure out how to have the Stack Monitoring UI check if the cluster is running in the cloud.

When running in Cloud, there is a cloud plugin in Kibana that has a property isCloudEnabled that should reliably indicate that the cluster is running in Elastic Cloud. cc @zanbel and @agup006 to verify this is always true for current versions, and to double check that the same is true in ECK.