Is there a way to inhibit alerts from saved searches that had errors? Saved searches will sometimes fail with errors like the one below:
-- Search generated the following messages -- Message Level: WARN 1. Unable to distribute to peer named <index-server> at uri https://<index-server>:11004 because replication was unsuccessful. replicationStatus Failed
We are aware of the causes for this and other fairly common errors that cause searches to fail or deliver incomplete search results. This is typically tolerable if the search failures are fairly infrequent, especially for saved searches where partial search results are sometimes good enough. However, some of our saved searches do not tolerate search errors. For example, we have a saved search that is configured to alert for the condition "if number of hosts is less than N", where N is the number of hosts from which we expect to get search results. Search errors will result in numbers less than N, causing alerts for this saved search.
Any suggestions for handling search errors for saved searches? I'm thinking that a scripted alert solution may be required, though I haven't found any documentation that indicates how a script would check for any search errors that might occur. Any suggestions or examples would be appreciated. Thanks.