Reporting of elevated Search & Indexing Errors on Solr Deployments

A bug was found in SearchStax’s Managed Solr alerting capability that related to Search & Indexing errors, where the service looked at the average number of errors across the Solr collections to determine the total number of errors, instead of summing them up. On Thursday, 4th February 2021, at 1:32pm UTC, a bug fix was released for Search & Indexing Threshold alert that fixed this bug, and now correctly sums the errors across all collections. What is the impact on you? Since the bug fix, you could be receiving more alerts for Search & Indexing errors. However, these are valid alerts and reflect the actual number of errors on the deployment. How are the Search Errors impacting you? One of the most common reasons for search errors is a malformed query, or querying on a field that doesn't exist. The logs will contain the detail about the query that needs to be fixed. Based on how your application handles this, it could be showing either an error message to the client, or not showing any results for those queries. How are the Indexing Errors impacting you? Schema mismatches are the most common reason for indexing errors. Your application could be trying to index a document containing a field that is not defined in the schema. In this case, Solr would not be indexing this document. This impacts the search on your application as the new document, or the updated contents of the old document will not be present in the search results. * If you are receiving these alerts, and would like us to find the reason, please feel free to reach out to SearchStax support. * If you are receiving these alerts, and know the reason, but need time to resolve the issues, and would like to not get the triggers, again and again, you can pause the alerts from the SearchStax dashboard, or increase the threshold for the alert, or in case the alert is not closing, you can increase the alert "Repeat Every" value of the alert to retrigger notification after a longer time period.