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

api/alerting/rule/{id} responding with "Internal Server Error" #106829

Closed
anmironov opened this issue Jul 27, 2021 · 2 comments
Closed

api/alerting/rule/{id} responding with "Internal Server Error" #106829

anmironov opened this issue Jul 27, 2021 · 2 comments
Labels
bug Fixes for quality problems that affect the customer experience estimate:small Small Estimated Level of Effort Feature:Alerting/RulesFramework Issues related to the Alerting Rules Framework Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@anmironov
Copy link

anmironov commented Jul 27, 2021

Kibana version: 7.13.3

Elasticsearch version: 7.13.3

Server OS version:

Browser version:

Browser OS version:

Original install method (e.g. download page, yum, from source, etc.): ESS
Describe the bug:
If you use APIKey and update the rule API (which supports Token-based authentication only) you will get a status code 500 statusCode: 500,
error: 'Internal Server Error',
message: 'An internal server error occurred.'
So it's hard to find the initial error in such request (I mean authentication method).
In case of using APIKey with wrong/fake key - 401 error

Steps to reproduce:

  1. Update rule API using APIKey using valid Key - 500 error
  2. Update rule API using APIKey using invalid Key - 401 error

Expected behavior:
Not sure, but a non-500 error, but more informative
Screenshots (if relevant):
Valid key
Inked2_LI

Invalid key
1

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

Any additional context:

@anmironov anmironov added the bug Fixes for quality problems that affect the customer experience label Jul 27, 2021
@botelastic botelastic bot added the needs-team Issues missing a team label label Jul 27, 2021
@gmmorris gmmorris added Feature:Alerting Feature:Alerting/RulesFramework Issues related to the Alerting Rules Framework Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Jul 27, 2021
@elasticmachine
Copy link
Contributor

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

@botelastic botelastic bot removed the needs-team Issues missing a team label label Jul 27, 2021
@gmmorris gmmorris added the loe:medium Medium Level of Effort label Jul 27, 2021
@gmmorris
Copy link
Contributor

Seems this is a duplicate and a PR addressing it has been merged: #96683

Closing as it will hopefully be included in the upcoming release.

@gmmorris gmmorris added estimate:small Small Estimated Level of Effort and removed loe:medium Medium Level of Effort labels Sep 2, 2021
@kobelb kobelb added the needs-team Issues missing a team label label Jan 31, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience estimate:small Small Estimated Level of Effort Feature:Alerting/RulesFramework Issues related to the Alerting Rules Framework Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Development

No branches or pull requests

4 participants