No Watches found on which to modify settings – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 8.8-8.9

Briefly, this error occurs when you try to modify settings on Elasticsearch watches that do not exist. Watches are used for alerting in Elasticsearch. The error indicates that the system couldn’t find any watches to apply the modifications to. To resolve this issue, you can either create new watches or ensure that the existing watches are correctly identified and accessible. Also, check your permissions to ensure you have the necessary rights to modify the settings of the watches.

This guide will help you check for common problems that cause the log ” no Watches found on which to modify settings ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: settings, plugin.

Log Context

Log “no Watches found on which to modify settings” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 ActionListener listener
 ) {
 final IndexMetadata watcherIndexMd = state.metadata().index(WATCHER_INDEX_NAME);
 if (watcherIndexMd == null) {
 // Index does not exist; so fail fast
 listener.onFailure(new ResourceNotFoundException("no Watches found on which to modify settings"));
 final Settings newSettings = Settings.builder().loadFromMap(request.settings()).build();
 final UpdateSettingsClusterStateUpdateRequest clusterStateUpdateRequest = new UpdateSettingsClusterStateUpdateRequest().indices(
 new Index[] { watcherIndexMd.getIndex() }