Show environment block on any environment:action job's details page.
Instead of showing the environment block with the linked environment on deploy jobs only (environment:action = start, show it on any action that accesses the environment (on any environment:action value).
Changelog: changed
Access an environment for preparation or verification purposes
| Before | After |
|---|---|
![]() |
![]() |
![]() |
|
![]() |
|
![]() |
environment:action values for each job. Sample file: sample-gitlab-ci.yml
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Related to #450878
@rcobb, can you do the first review?
Allison Browne (a8dd6d17) at 27 Feb 14:56
Fix spec/lib/gitlab/sidekiq_death_handler_spec.rb spec
TODO before leave: Add json for grafana dash or MR for grafana dash I've been working on
@sxuereb, I'm very grateful for the reviews
@thisisrick25, I'm heading out on parental leave so I re-ran the danger bot to re-run the review roulette. If you are able to make updates you can mention @erren for the next review cycle.
I will un-assign myself from this one.
The MR to redirect alerts to the sec channel was merged
This also ends up refactoring the alerts to be generated via ./scripts/generate-jsonnet-rules.sh so that they are less duplicative.
Closing the issue.
Another idea would be to create a dashboard to review for the last week for each alert type. That could be less disruptive but lead to a similar result of filing issues for any problematic queries/patterns identified.
I've started to build something like this for CPU saturation. Which would combine the 3 top 10 statements graphs from the runbook as well as links to those queryIds in kibana. Possibly we can add other saturation related metrics like apdex, CPU saturation % and anything else that can cause saturation.
Thanks @sxuereb, I've addressed your feedback. Let me know what you think
To be consistent with the original alerts I've removed generating mimir-rules/gitlab-gstg and mimir-rules/gitlab-pre only the production alerts are very relevant here.
Allison Browne (6fb5ad79) at 26 Feb 21:30
Remove generating gstg and pre files
Allison Browne (78172381) at 26 Feb 20:40
Since tenant is passed I get:
$ jsonnet -J libsonnet/ -J metrics-catalog/ -J services/ -J vendor/ mimir-rules-jsonnet/patroni-saturation-alerts.jsonnet
RUNTIME ERROR: function expected 1 positional argument(s), but got 2
when I try to remove this arg, even though it's not used.
Allison Browne (97c9efe0) at 26 Feb 20:02
Fix sidekiq_middleware/server_metrics_spec.rb spec