Project

General

Profile

Actions
Copy link

action #163595

closed

[alert] (Web proxy Response Time alert Salt IeChie2He)

Added by tinita 17 days ago. Updated 2 days ago.

Status:
Resolved
Priority:
High
Assignee:
okurz
Category:
Regressions/Crashes
Target version:
openQA Project - Ready
Start date:
2024-07-10
Due date:
% Done:

0%

Estimated time:
Tags:
alert, infra, web proxy response

Description

Observation

We saw several alerts this morning:
http://stats.openqa-monitor.qa.suse.de/alerting/grafana/IeChie2He/view?orgId=1

Date: Wed, 10 Jul 2024 06:17:00 +0200                                                                                                                                                                         
From: Grafana <osd-admins@suse.de>                                                                                                                                                                            
To: osd-admins@suse.de                                                                                                                                                                                        
Subject: [FIRING:1] (Web proxy Response Time alert Salt IeChie2He)                                                                                                                                            

1 firing alert instance
[IMAGE]

  🔥 1 firing instances

Firing [stats.openqa-monitor.qa.suse.de]
Web proxy Response Time alert
View alert [stats.openqa-monitor.qa.suse.de]
Values
A0=60.627 
Labels
alertname
Web proxy Response Time alert
grafana_folder
Salt

Related issues 1 (0 open — 1 closed)

Related to openQA Infrastructure - action #163592: [alert] (HTTP Response alert Salt tm0h5mf4k) size:MResolvedokurz2024-07-10

Actions
Actions
Copy link
 #1

Updated by okurz 17 days ago

  • Related to action #163592: [alert] (HTTP Response alert Salt tm0h5mf4k) size:M added
Actions
Copy link
 #2

Updated by okurz 17 days ago

  • Tags set to alert, infra, web proxy response
Actions
Copy link
 #3

Updated by nicksinger 15 days ago

I don't know what we're expected to do here. The only think that comes to my mind would be to adjust the alert itself but I would rather not and handle the whole outage in #163592

Actions
Copy link
 #4

Updated by okurz 15 days ago

  • Status changed from New to Blocked
  • Assignee set to okurz

yes, I agree but let's be explicit so blocking and checking afterwards.

Actions
Copy link
 #5

Updated by livdywan 9 days ago

Work on the blocker is still on-going, see #163592#note-49

Actions
Copy link
 #6

Updated by okurz 2 days ago

  • Status changed from Blocked to Resolved
Actions
Copy link

Also available in: Atom PDF