Project

General

Profile

Actions

action #96807

closed

Web UI is slow and Apache Response Time alert got triggered

Added by livdywan over 3 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
-
Target version:
Start date:
2021-08-12
Due date:
2021-10-01
% Done:

0%

Estimated time:

Description

Observation

I was already investigating #96795 wondering if that could be causing the slowness of the web UI and then I saw this alert:

[Alerting] Apache Response Time alert
The apache response time exceeded the alert threshold. * Check the load of the web UI host * Consider restarting the openQA web UI service and/or apache Also see #73633

Although it went back to OK after 2 minutes I decided to file it in case it comes back.


Related issues 4 (0 open4 closed)

Related to openQA Infrastructure - action #96554: Mitigate on-going disk I/O alerts size:MResolvedmkittler2021-08-04

Actions
Related to openQA Infrastructure - action #96795: CPU Load alert and telegraf going between 41%, 98.5% and 115% CPUResolvedlivdywan2021-08-122021-08-28

Actions
Related to openQA Infrastructure - action #96713: Slow grep in openqa-label-known-issues leads to high CPU usageResolvedokurz

Actions
Related to openQA Infrastructure - action #107875: [alert][osd] Apache Response Time alert size:MResolvedtinita2022-03-04

Actions
Actions #1

Updated by tinita over 3 years ago

  • Priority changed from Normal to High
  • Target version set to Ready
Actions #2

Updated by livdywan over 3 years ago

  • Related to action #96554: Mitigate on-going disk I/O alerts size:M added
Actions #3

Updated by livdywan over 3 years ago

  • Related to action #96795: CPU Load alert and telegraf going between 41%, 98.5% and 115% CPU added
Actions #4

Updated by livdywan over 3 years ago

  • Related to action #96713: Slow grep in openqa-label-known-issues leads to high CPU usage added
Actions #5

Updated by livdywan over 3 years ago

  • Status changed from New to Feedback

The alert hasn't fired anymore so far. Putting it in Feedback as we need to confirm if it's gonna happen with the related tickets sorted.

Actions #6

Updated by okurz over 3 years ago

  • Due date set to 2021-10-01
  • Status changed from Feedback to Blocked
  • Assignee set to okurz

There should be no "Feedback" without assignee as we commonly overlook them. I can look again after the related tasks are resolved.

Actions #7

Updated by okurz about 3 years ago

  • Status changed from Blocked to Resolved

After all the related tasks are resolved I checked the webUI performance and it's okay-ish and the apache response time graphs also look ok.

Actions #8

Updated by okurz over 2 years ago

  • Related to action #107875: [alert][osd] Apache Response Time alert size:M added
Actions

Also available in: Atom PDF