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
In the same vein as #20577, Kibana should provide an HTTP API that exposes Kibana settings currently used by Kibana X-Pack Monitoring. I believe the only such setting today is the admin email address.
Use case
Metricbeat — concretely the settings metricset in the kibana module — will call this API periodically and ship the results in the right format to .kibana-monitoring-6-* indices. This will help make progress towards completing the larger feature of using Metricbeat to monitoring Kibana (and eventually the rest of the Elastic stack).
Important note
This API is likely a temporary solution until the Kibana Alerting feature is built. Once that is shipped and driving the Cluster Alerts feature in Monitoring, we will no longer need to index kibana_settings documents into .kibana-monitoring-6* indices. At that point this API (and the corresponding metricset in metricbeat) can be removed. As such it is probably best to not document this API for external/public use.
The text was updated successfully, but these errors were encountered:
In the same vein as #20577, Kibana should provide an HTTP API that exposes Kibana settings currently used by Kibana X-Pack Monitoring. I believe the only such setting today is the admin email address.
Use case
Metricbeat — concretely the
settings
metricset in thekibana
module — will call this API periodically and ship the results in the right format to.kibana-monitoring-6-*
indices. This will help make progress towards completing the larger feature of using Metricbeat to monitoring Kibana (and eventually the rest of the Elastic stack).Important note
This API is likely a temporary solution until the Kibana Alerting feature is built. Once that is shipped and driving the Cluster Alerts feature in Monitoring, we will no longer need to index
kibana_settings
documents into.kibana-monitoring-6*
indices. At that point this API (and the corresponding metricset in metricbeat) can be removed. As such it is probably best to not document this API for external/public use.The text was updated successfully, but these errors were encountered: