Commit 85f48351 authored by Marat Kalibekov's avatar Marat Kalibekov

some fixes to gitlab-com-builds alert

1. using fqdn instead of instance will be better
1. humanize value output
parent 4f4ebada
## Pending builds for projects with shared runners enabled
ALERT number_of_pending_builds_for_project_with_shared_runners_is_too_high
IF max(rate(ci_builds_total{shared_runners_enabled_projects="1",status="pending",instance="db1"}[2h])) > 5
IF max(rate(ci_builds_total{shared_runners_enabled_projects="1",status="pending",fqdn="db1.cluster.gitlab.com"}[2h])) > 5
FOR 30m
LABELS {severity="critical", channel="infrastructure"}
ANNOTATIONS {
title="Rate of pending builds for projects with shared runners is too high: {{$value}}",
title="Rate of pending builds for projects with shared runners is too high: {{$value | humanize}}",
description="Rate of pending builds for projects with shared runners is increasing and is very high for more than 30 minutes. This may suggest problems with auto-scaling provider or Runner stability. You should check Runner's logs. Check http://performance.gitlab.net/dashboard/db/ci.",
}
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment