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

[Monitoring] Account for SSL not being enabled before calling the alerting api #71798

Closed
igoristic opened this issue Jul 15, 2020 · 2 comments · Fixed by #71846
Closed

[Monitoring] Account for SSL not being enabled before calling the alerting api #71798

igoristic opened this issue Jul 15, 2020 · 2 comments · Fixed by #71846
Labels
blocker bug Fixes for quality problems that affect the customer experience Team:Monitoring Stack Monitoring team v7.9.0 v8.0.0

Comments

@igoristic
Copy link
Contributor

By default the SSL is not enabled, as a result we're getting a 500 error when calling the /alerts/enable route (after enabling Stack Monitoring)

@igoristic igoristic added bug Fixes for quality problems that affect the customer experience Team:Monitoring Stack Monitoring team v8.0.0 labels Jul 15, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/stack-monitoring (Team:Monitoring)

@liza-mae
Copy link
Contributor

Also seeing this, get POST https://localhost:5601/api/monitoring/v1/clusters 500 (Internal Server Error), when you don't specify xpack.encryptedSavedObjects.encryptionKey and then run self-monitoring.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocker bug Fixes for quality problems that affect the customer experience Team:Monitoring Stack Monitoring team v7.9.0 v8.0.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants