Update ApplicationSetting with `mimir_api_url` settings for `gprd`
Staging Change
Change Summary
As Thanos is being decommissioned, we need to provide a new client to fetch metrics from Prometheus and add a new url to our config.
gitlab-org/gitlab!153629 (diffs) introduced a new client that will use mimir_api_url
stored in ApplicationSetting.prometheus_alert_db_indicators_settings
.
This CR aims to add mimir_api_url
for gprd. Check the gstg issue.
Note:
- The functionality is behind db_health_check_using_mimir_client FF. It will be enabled after this CR changes goes in and the proper secretes were updated for
gprd
.
Commands to be run in the console
application_setting = ApplicationSetting.last
prometheus_alert_db_indicators_settings = application_setting.prometheus_alert_db_indicators_settings
application_setting.update(
prometheus_alert_db_indicators_settings: prometheus_alert_db_indicators_settings.merge(
mimir_api_url: 'https://mimir-internal.ops.gke.gitlab.net'
)
)
Rollback commands
old_config = {
prometheus_api_url: 'http://thanos-query-frontend-internal.ops.gke.gitlab.net:9090',
apdex_slo: { ci: 0.997, main: 0.997, main_cell: 0.997 },
wal_rate_slo: { ci: 70000000, main: 70000000, main_cell: 70000000 },
apdex_sli_query: {
ci: "avg_over_time(gitlab_service_apdex:ratio_5m{env='gprd',environment='gprd',monitor='global',type='patroni-ci'}[5m])",
main: "avg_over_time(gitlab_service_apdex:ratio_5m{env='gprd',environment='gprd',monitor='global',type='patroni'}[5m])",
main_cell: "avg_over_time(gitlab_service_apdex:ratio_5m{env='gprd',environment='gprd',monitor='global',type='patroni'}[5m])"
},
wal_rate_sli_query: {
ci: "avg(postgres:pg_xlog_bytes_per_second:rate5m{env='gprd', type='patroni-ci'})",
main: "avg(postgres:pg_xlog_bytes_per_second:rate5m{env='gprd', type='patroni'})",
main_cell: "avg(postgres:pg_xlog_bytes_per_second:rate5m{env='gprd', type='patroni'})"
},
wal_receiver_saturation_slo: { ci: 0.7, main: 0.7, main_cell: 0.7 },
wal_receiver_saturation_sli_query: {
ci: "max(1 - quantile_over_time(0.50, postgres_replication_process_state_ratio{env='gprd', type='patroni-ci', process_type='walreceiver' process_state='S'}[5m]))",
main: "max(1 - quantile_over_time(0.50, postgres_replication_process_state_ratio{env='gprd', type='patroni', process_type='walreceiver', process_state='S'}[5m]))",
main_cell: "max(1 - quantile_over_time(0.50, postgres_replication_process_state_ratio{env='gprd', type='patroni', process_type='walreceiver', process_state='S'}[5m]))"
}
}
application_setting = ApplicationSetting.last
application_setting.update(prometheus_alert_db_indicators_settings: old_config)
Change Details
- Services Impacted - Thanos Query FE, Batched background migrations
-
Change Technician -
@l.rosa
- Change Reviewer -
- Time tracking - unknown
- Downtime Component - none
Detailed steps for the change
Change Steps - steps to take to execute the change
Estimated Time to Complete (mins) - Single update call to Db, should be quick
-
Set label changein-progress /label ~change::in-progress
-
Run above commands in the rails console in gstg
ENV -
Set label changecomplete /label ~change::complete
Rollback
Rollback steps - steps to be taken in the event of a need to rollback this change
Estimated Time to Complete (mins) - Single update call to Db, should be quick
-
Run the rollback commands in gstg
rails console. -
Set label changeaborted /label ~change::aborted
Monitoring
Key metrics to observe
- Metric: Metric Name
- Location: Dashboard URL
- What changes to this metric should prompt a rollback: Describe Changes
Change Reviewer checklist
-
Check if the following applies: - The scheduled day and time of execution of the change is appropriate.
- The change plan is technically accurate.
- The change plan includes estimated timing values based on previous testing.
- The change plan includes a viable rollback plan.
- The specified metrics/monitoring dashboards provide sufficient visibility for the change.
-
Check if the following applies: - The complexity of the plan is appropriate for the corresponding risk of the change. (i.e. the plan contains clear details).
- The change plan includes success measures for all steps/milestones during the execution.
- The change adequately minimizes risk within the environment/service.
- The performance implications of executing the change are well-understood and documented.
- The specified metrics/monitoring dashboards provide sufficient visibility for the change.
- If not, is it possible (or necessary) to make changes to observability platforms for added visibility?
- The change has a primary and secondary SRE with knowledge of the details available during the change window.
- The labels blocks deployments and/or blocks feature-flags are applied as necessary
Change Technician checklist
-
Check if all items below are complete: - The change plan is technically accurate.
- This Change Issue is linked to the appropriate Issue and/or Epic
- Change has been tested in staging and results noted in a comment on this issue.
- A dry-run has been conducted and results noted in a comment on this issue.
- The change execution window respects the Production Change Lock periods.
- For C1 and C2 change issues, the change event is added to the GitLab Production calendar.
- For C1 and C2 change issues, the SRE on-call has been informed prior to change being rolled out. (In #production channel, mention
@sre-oncall
and this issue and await their acknowledgement.) - For C1 and C2 change issues, the SRE on-call provided approval with the eoc_approved label on the issue.
- For C1 and C2 change issues, the Infrastructure Manager provided approval with the manager_approved label on the issue.
- Release managers have been informed (If needed! Cases include DB change) prior to change being rolled out. (In #production channel, mention
@release-managers
and this issue and await their acknowledgment.) - There are currently no active incidents that are severity1 or severity2
- If the change involves doing maintenance on a database host, an appropriate silence targeting the host(s) should be added for the duration of the change.
Edited by Leonardo da Rosa