Skip to content
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

Merged
merged 3 commits into from
Apr 23, 2021

Conversation

mikecote
Copy link
Contributor

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.

@kibanamachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id before after diff
alerting 61.4KB 61.4KB +14.0B

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @mikecote

@mikecote mikecote marked this pull request as ready for review April 22, 2021 15:35
@mikecote mikecote requested a review from a team as a code owner April 22, 2021 15:35
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

Copy link
Contributor

@YulNaumenko YulNaumenko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

@ymao1 ymao1 left a 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.

@mikecote mikecote added the auto-backport Deprecated - use backport:version if exact versions are needed label Apr 23, 2021
@mikecote mikecote merged commit 7598f57 into elastic:master Apr 23, 2021
@kibanamachine
Copy link
Contributor

💔 Backport failed

Status Branch Result
7.x Commit could not be cherrypicked due to conflicts

To backport manually run:
node scripts/backport --pr 98005

mikecote added a commit to mikecote/kibana that referenced this pull request Apr 23, 2021
…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
mikecote added a commit that referenced this pull request Apr 23, 2021
…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
madirey pushed a commit to madirey/kibana that referenced this pull request May 11, 2021
…98005)

* Log instead of throwing error when alert type doesn't exist

* Cleanup i18n

* Update error messages
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-backport Deprecated - use backport:version if exact versions are needed Feature:Alerting release_note:skip Skip the PR/issue when compiling release notes Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) v7.14.0 v8.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants