Actions
action #129745
closedcoordination #110833: [saga][epic] Scale up: openQA can handle a schedule of 100k jobs with 1k worker instances
coordination #108209: [epic] Reduce load on OSD
Enable apache response time alert and apache log alert again after we think it's good now size:M
Start date:
2023-05-23
Due date:
% Done:
0%
Estimated time:
Tags:
Description
Motivation¶
In #128789 we identified the root cause for the apache response time alerts and also improvements for alert panels. We kept the apache response time alert silenced as we plan to implement features to mitigate. After those features implemented we should check our apache response times carefully and enable the alert after we think it's good again
Acceptance criteria¶
- AC1: alert with uid zZAh5mf4k and "alertname=Apache log data" on https://stats.openqa-monitor.qa.suse.de/alerting/silences is active again
Suggestions¶
- Wait for related features in the same parent epic
- Monitor apache response times
- As necessary adapt the alert(s)
- Unsilence alert with uid zZAh5mf4k on https://stats.openqa-monitor.qa.suse.de/alerting/silences
- Same for "alertname=Apache log data"
Updated by okurz over 1 year ago
- Subject changed from Enable apache response time alert again after we think it's good now to Enable apache response time alert and apache log alert again after we think it's good now
- Description updated (diff)
Updated by okurz over 1 year ago
- Due date set to 2023-08-11
- Status changed from Blocked to Feedback
unsilenced "apache" related alerts. Maybe that was premature, monitoring over the next days.
Updated by mkittler about 1 year ago
- Subject changed from Enable apache response time alert and apache log alert again after we think it's good now to Enable apache response time alert and apache log alert again after we think it's good now size:M
Updated by okurz about 1 year ago
- Due date deleted (
2023-08-11) - Status changed from Feedback to Resolved
I have not seen a related alert recently so maybe we are good to go :)
Actions