Page MenuHomePhabricator

[Renaming TestKitchen] Update SLO configuration
Closed, ResolvedPublic1 Estimated Story Points

Description

Description

As part of the Test Kitchen renaming (MetricsPlatform => TestKitchen) some SLO configuration that is using old naming like xlab, mpic, Experimentation Lab and so on should be updated to reflect the new name of the platform and its components.

In general:

  • Experimentation Lab should be renamed to Test Kitchen (platform name)
  • xlab should be renamed to test-kitchen/test_kitchen depending on the allowed pattern (as a prefix for some identifiers)
  • mpic should be renamed to Test Kitchen (In the end the metrics means the platform itself)

All this work must be done once TestKitchen is available and working in production and before removing MetricsPlaform from there.

Acceptance criteria

  • The name of the thanos record rules are following the general rules
  • SLO configuration hasn't references to Experimentation Lab/MPIC/xlab. They have been replaced according to the general rules

Event Timeline

Sfaci renamed this task from [TestKitchen renaming] Update SLO configuration to [Renaming] Update SLO configuration.Jan 13 2026, 11:23 AM
Sfaci renamed this task from [Renaming] Update SLO configuration to [Renaming TestKitchen] Update SLO configuration.Jan 13 2026, 11:56 AM
Sfaci set the point value for this task to 1.

Change #1238312 had a related patch set uploaded (by Santiago Faci; author: Santiago Faci):

[operations/puppet@production] Test Kitchen SLOs: Renaming slos because of the Test Kitchen renaming

https://gerrit.wikimedia.org/r/1238312

@Sfaci: You will have to request your change to be deployed in a Puppet request window.

@Sfaci: You will have to request your change to be deployed in a Puppet request window.

Thank Sam! I had fully forgotten this ticket! I'll schedule the patch to be deployed

Some context from conversation with SREs while trying to deploy the related change:

From @RLazarus

my recommendation is to actually not make this change -- I'm pretty sure that as-is, it would lose track of your SLO history (since you'd have a brand-new recording rule under the new name) and I don't think that's what you want
normally my advice would be that we can work with observability to make this work without losing any data, *but* since we're about to move everybody to sloth and decommission the pyrra dashboards, how do you feel about just leaving it?

Also, @elukey shared with as the following:

The SLO working group is going to announce later on that Pyrra is being replaced by Sloth, a tool completely integrated in Grafana.

The new dashboard for xlab is https://grafana-rw.wikimedia.org/d/slot-pilot-slo-detail/sloth-slo-detail?forceLogin=true&from=now-7d&orgId=1&refresh=30s&timezone=utc&to=now&var-Datasource=000000019&var-> min_burning_rate=1&var-service=test-kitchen&var-sli_window=5m&var-slo=$__all&var-revision=1&var-hours_in_range=169

And it sounds like we added the right name :D

So, considering that we already have the new dashboard with the right name (test-kitchen), we could lose the SLO history with the current patch and Pyrra is being replaced by the new tool, it seems that the right thing to do here is to abandon the current patch and start using the new dashboard

Change #1238312 abandoned by Santiago Faci:

[operations/puppet@production] Test Kitchen SLOs: Renaming slos because of the Test Kitchen renaming

Reason:

https://phabricator.wikimedia.org/T414381#11775685

https://gerrit.wikimedia.org/r/1238312