Project

General

Profile

Actions

action #153418

closed

http based health check against proxy.scc.suse.de size:M

Added by okurz 4 months ago. Updated 4 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
2023-12-21
Due date:
2024-01-30
% Done:

0%

Estimated time:
Tags:

Description

Motivation

See #152857-18

Acceptance criteria

  • AC1: There is an alert about proxy SCC http responsiveness

Suggestions


Related issues 1 (0 open1 closed)

Copied from openQA Infrastructure - action #152857: [tools] alert ping between hosts timeout proxy.scc.suse.deResolvedokurz2023-12-21

Actions
Actions #1

Updated by okurz 4 months ago

  • Copied from action #152857: [tools] alert ping between hosts timeout proxy.scc.suse.de added
Actions #2

Updated by okurz 4 months ago

  • Target version changed from Tools - Next to Ready
Actions #3

Updated by mkittler 4 months ago

  • Subject changed from http based health check against proxy.scc.suse.de to http based health check against proxy.scc.suse.de size:M
  • Description updated (diff)
  • Status changed from New to Workable
Actions #4

Updated by nicksinger 4 months ago

  • Status changed from Workable to In Progress
  • Assignee set to nicksinger
Actions #5

Updated by openqa_review 4 months ago

  • Due date set to 2024-01-30

Setting due date based on mean cycle time of SUSE QE Tools

Actions #7

Updated by okurz 4 months ago

Both MRs merged. Data should arrive shortly.

Actions #8

Updated by okurz 4 months ago

https://gitlab.suse.de/openqa/salt-states-openqa/-/merge_requests/1088 to add monitoring panels, also done.

  1. I suggest to change $tag_server - $tag_host to $tag_host - $tag_server to be consistent with the ping check where we also use <source> - <target>
  2. Please add an according alert
Actions #10

Updated by nicksinger 4 months ago

  • Status changed from In Progress to Feedback
Actions #11

Updated by okurz 4 months ago

  • Status changed from Feedback to In Progress

MR merged. https://gitlab.suse.de/openqa/salt-states-openqa/-/jobs/2186107 shows that the deployment is done. I don't know why you chose to create an alert not linked to the dashboard so I don't know what's expected to be different. I can see an alert "Salt
http_response_codes" on https://monitor.qa.suse.de/alerting/list?search=http but it does not say "provisioned". Can you crosscheck if the alert was actually deployed or if that is still the one that you created manually to prepare it.

EDIT: Nope, the problem is likely that your newly mentioned file needs to be mentioned in monitoring/grafana.sls

Actions #12

Updated by nicksinger 4 months ago

  • Status changed from In Progress to Resolved

Good catch, thank you. I fixed that with https://gitlab.suse.de/openqa/salt-states-openqa/-/merge_requests/1096 - it now shows up as "Provisioned" in grafana. As described in https://gitlab.suse.de/openqa/salt-states-openqa/-/merge_requests/1094 I couldn't find a way to link that alert to an panel and for the sake of "getting it done" I just didn't do it no not waste more time :)

Actions

Also available in: Atom PDF