Anish Ansari

Well put, Rishabh. A gate that gets skipped on a busy deploy day is really just documentation, so keeping it quick matters more than making it exhaustive.

Right, if the check only takes a minute people actually run it before a deploy instead of skipping it when they are in a hurry.

Fully agree, Rishabh. Keeping that tag page small is what makes the review check stick as the job list grows.

Exactly, catching it in the diff is way cheaper than cleaning up a messy dashboard a month later. Thanks for all the ideas in this thread, Rishabh.

Making the tag part of the same PR review is a nice touch, Rishabh. The reviewer already has the job open, so checking it against the page costs almost nothing.

Completely agree Diego, a fallback that only runs during a real outage is usually the part that breaks. Forcing the breaker open in tests so the cached value or pay later path actually gets exercised is worth the effort.

One short page with an example per tag is the right size, Rishabh. If it gets longer than that nobody reads it before adding a new job anyway.

Good point Rishabh, a shared list of allowed tags stops "report-export" and "export-report" from showing up as two different causes. A short convention doc next to the dashboard would keep it from drifting.

Agreed, a short tag list keeps the graph readable, otherwise you end up with five labels that all point at the same slow job.

Tagging each peak with the endpoint or job name is a great idea, then the graph points you straight at the culprit instead of sending you off to search through logs.