This post is older than a year. Consider some information might not be accurate anymore.
If you setup Elasticsearch to report to a dedicated monitoring cluster
PUT _cluster/settings
{
"persistent": {
"xpack.monitoring.exporters.cloud_monitoring.type": "http",
"xpack.monitoring.exporters.cloud_monitoring.host": "MONITORING_ELASTICSEARCH_URL",
"xpack.monitoring.exporters.cloud_monitoring.auth.username": "cloud_monitoring_agent",
"xpack.monitoring.exporters.cloud_monitoring.auth.password": "MONITORING_AGENT_PASSWORD"
}
}
you can unset or reset it with, passing null
.
PUT _cluster/settings
{
"persistent": {
"xpack.monitoring.exporters.cloud_monitoring.type": null,
"xpack.monitoring.exporters.cloud_monitoring.host": null,
"xpack.monitoring.exporters.cloud_monitoring.auth.username": null,
"xpack.monitoring.exporters.cloud_monitoring.auth.password": null
}
}
In the logs of the master node, following log message will appear
[2017-10-09T15:30:40,007][INFO ][o.e.c.s.ClusterSettings ] [master-one] updating [xpack.monitoring.exporters.] from [{"cloud_monitoring":{"host":"monitornode","type":"http","auth":{"password":"mapperking","username":"remote_monitor"}}}] to [{}]