New issue
Advanced search Search tips

Issue 620144 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Customizable alerting threshold for builders

Project Member Reported by mariakho...@chromium.org, Jun 14 2016

Issue description

I've got the following alert

internal.client.clank.orderfile-clankium has been building for 5h26m34.027067728s (last step update 2016-06-14 17:31:41 +0000 UTC), past the alerting threshold of 3h0m0s

However, looking at the bot's previous successful runs, it took:
4 hrs, 39 mins, 20 secs
5 hrs, 31 mins, 48 secs

So we should change alerting threshold for this bot to match the expectation of slow runtime.
 
 Issue 619745  has been merged into this issue.
Status: Available (was: Untriaged)
I've noticed this as well; do you consider it a blocker to adoption?

It would required modifying both the configs, and the alerts dispatcher. However, we're kinda dumping a lot of stuff in there that doesn't belong. So, it'd be nice to refactor that information into another config, which would be complicated.

sean, WDYT? We could either add this field to gatekeeper.json, or gatekeeper_trees.json.
Components: -Infra Infra>SheriffOMatic
Labels: -SheriffOmatic
I don't think it's a blocker to adoption -- more of a nice to have.
If gatekeeper itself wouldn't do anything with this information, it probably doesn't belong in gatekeeper's config. 

How often would this kind of setting change?
Also, wdyt about using LUCI-config for this (and possibly other config things that are currently squirreled away in various repos)?
luci-config would be great; good use case for this.

This would change relatively infrequently, I believe.
Summary: Customizable alerting threshold for builders (was: Increment alerting threshold for Orderfile bot)
Components: Infra>Sheriffing>Gatekeeper
Components: -Infra>Sheriffing
Labels: Type-Bug
Issue 638547 has been merged into this issue.
Project Member

Comment 13 by sheriffbot@chromium.org, Aug 18 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: Available (was: Untriaged)

Sign in to add a comment