-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Log instead of throwing error when alert type doesn't exist #98005
Log instead of throwing error when alert type doesn't exist #98005
Conversation
💚 Build SucceededMetrics [docs]Page load bundle
History
To update your PR or re-run it, just comment with: cc @mikecote |
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Commented out an alert type on the server and verified it was console logged with no error thrown.
💔 Backport failed
To backport manually run: |
…98005) * Log instead of throwing error when alert type doesn't exist * Cleanup i18n * Update error messages # Conflicts: # x-pack/plugins/translations/translations/ja-JP.json # x-pack/plugins/translations/translations/zh-CN.json
…98121) * Log instead of throwing error when alert type doesn't exist * Cleanup i18n * Update error messages # Conflicts: # x-pack/plugins/translations/translations/ja-JP.json # x-pack/plugins/translations/translations/zh-CN.json
There have been reports (#59229 (comment)) that our alerting public plugin throws unhandled errors. This PR removes the throwing and replaces it with a console log.