[ML] Explain Log Rate Spikes: Wrap analysis in try/catch block. (#144400

)

This wraps the analysis part in a try/catch block. We had individual try/catch blocks already to handle ES queries. Because the analysis is run async, if another error happens it would trigger an unresolved promise error and could crash Kibana server. Adding this additional try/catch block avoids this.

(cherry picked from commit d556450)