You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow the parameter xpack.reporting.queue.pollEnabled: false to be set in the cloud Kibana configuration.
Describe a specific use case for the feature:
We have a hosted Elasticsearch cluster on Elastic cloud. There is a free Kibana version there, with fewer resources. We host a separate Kibana instance on a virtual machine, and it's connected to the cluster. Both have the same xpack.reporting.encryptionKey, and work with the cluster, but we use the VM Kibana. Some of the dashboards are bigger, and starting a reporting job on the VM Kibana can get claimed by the cloud Kibana, and the reporting job fails.
Disabling the cloud Kibana with xpack.reporting.enabled: false leads to the reporting dropdown not appearing on the VM Kibana for the non-admin user roles.
Is there a way for the cloud Kibana to be disabled from claiming the reporting jobs?
The text was updated successfully, but these errors were encountered:
Describe the feature:
Allow the parameter
xpack.reporting.queue.pollEnabled: false
to be set in the cloud Kibana configuration.Describe a specific use case for the feature:
We have a hosted Elasticsearch cluster on Elastic cloud. There is a free Kibana version there, with fewer resources. We host a separate Kibana instance on a virtual machine, and it's connected to the cluster. Both have the same
xpack.reporting.encryptionKey
, and work with the cluster, but we use the VM Kibana. Some of the dashboards are bigger, and starting a reporting job on the VM Kibana can get claimed by the cloud Kibana, and the reporting job fails.Disabling the cloud Kibana with
xpack.reporting.enabled: false
leads to the reporting dropdown not appearing on the VM Kibana for the non-admin user roles.Is there a way for the cloud Kibana to be disabled from claiming the reporting jobs?
The text was updated successfully, but these errors were encountered: