-
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
[Stack Monitoring] [Test Scenario] Out of the box alerting #104440
Comments
Pinging @elastic/logs-metrics-ui (Team:logs-metrics-ui) |
Tested "Create Rules" in 7.14 Cloud environment and works. I'll let someone else test the alerts :) |
@neptunian I will test the alerts |
@neptunian Can you clarify in which environment I need to do the testing? (staging vs cloud with this release version) |
@mgiota You can do it on staging cloud: https://staging.found.no/ |
@neptunian Thanks! For some reason staging was miserably failing, so I already did the testing on cloud with 7.14 and here are my findings: Apart from some small UI issues I found #105220, #105205, #105249, #105259 everything I tested so far from the list above worked fine. I am not sure about the labels I should add to the tickets I created, feel free to update if needed. Here are a few observations/comments:
|
@neptunian I tried to do the testing on staging, but staging is quite broken. I can not even enable Logs and Metrics, I keep getting Interval Server Error. I did one more time my testing on Cloud with 7.14 and I still didn't get the modal on the listing page (I had no default rules enabled and I had cleared my localStorage and sessionStorage before). Regarding the Could you double check above issues? |
Code is not available yet. According to the release schedule, BC2 was done on July 8, and the PR to add the modal on the listing page was merged on July 9. We need to wait for BC3, which is planned for July 14 to be able to test this. Code is not automatically updated, we need to create a new deployment with the last BC3. |
I tried this too. I was able to see the alert in the Kibana Server log, but not in Stack Monitoring UI or Stack Management. @neptunian did you manage to see the alert in the UI? |
Thanks for clarifying!
That was also my guess. |
@estermv @neptunian Thanks for testing! I was able to reproduce the Nodes Changed alert, but similarly it appeared in a very short window. So I think if was set to only check once a day or something you'd see the alert for longer, but then I'm not sure how long you'd have to wait to see the alert for the first time. I'll take another look at it. |
This is tricky to produce in Cloud for whatever reason but I was able to get cluster alerts working with BC3 of 7.14 pointed to observability release cluster. |
Summary
Stack Monitoring provides a set of out-of-the-box alerts, when choosing to create them from the menu. The default action for each alert is a server log and the action messaging is controlled by the Stack Monitoring UI code directly.
7.14 PRs
#102544
#101565
#103718
#101941
Testing
Create Rules
X
button rules shouldn't be created and the user should see the modal in a new page sessionSpecific rules trigger alerts
Setup and directions
screenshot
screenshot
Alert Per Node Rules
6tX5ghz7Q9uw330E6Zt6PQ
6tX5ghz7Q9uw330E6Zt6PQ
Alert Per Index Rules
clusterId:indexName
eg:NGIZVsfNS_aN4WgcM4v_iA:apm-7.14.0-error-000001
Alert Per Cluster Rules
NGIZVsfNS_aN4WgcM4v_iA
The text was updated successfully, but these errors were encountered: