sfaci opened https://gitlab.wikimedia.org/repos/data-engineering/metrics-platform/-/merge_requests/111

In T384506#11400833, @phuedx wrote:

In T384506#11400635, @Sfaci wrote:

@phuedx @Milimetric Can I assume that the replacement is the following?

• mw.log() -> console.log
• mw.log.warn()-> console.warn()
• mw.log.deprecate() -> console.warn()
• mw.log.error() -> console.error()

Only mw.log() needs to be replaced. mw.log.warn() and .error() call the equivalent methods on the console object. We shouldn't replace mw.log.deprecate() as it's for marking methods as deprecated / tracking deprecations via a dashboard.

Change #1210616 merged by Brouberol:

[operations/puppet@production] dse-k8s: delete the stat-> PG on k8s ingress firewall rule

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

Change #1210616 had a related patch set uploaded (by Brouberol; author: Brouberol):

[operations/puppet@production] dse-k8s: delete the stat-> PG on k8s ingress firewall rule

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

In T384506#11400635, @Sfaci wrote:

@phuedx @Milimetric Can I assume that the replacement is the following?

• mw.log() -> console.log
• mw.log.warn()-> console.warn()
• mw.log.deprecate() -> console.warn()
• mw.log.error() -> console.error()

In T384506#11371703, @JVanderhoop-WMF wrote:

Definition of Done here:
. . .

• Replace all instances of mw.log() with console.log()

. . .

In T384506#11371703, @JVanderhoop-WMF wrote:

Definition of Done here:

• Legacy EventLogging has a visual debug mode that is very rarely used. We killed it but we didn't tell anyone (including ourselves!). Tell people we killed it.

. . . .

Decision Record: http://wikitech.wikimedia.org/wiki/Test_Kitchen/Decision_Records/Increase_action_context_limit

Moving into sprint since Julie is working on this (drafted decision record, shopping it around with stakeholders)

just so we have the data here too -- here is the section in the report (created for SDS2.1.2) that provides insight by browser - https://docs.google.com/document/d/1XK8sZ2CCpFurOUV6PUXgCApjBrx-yOKVQe5BbPDsxsc/edit?tab=t.0#heading=h.fevi2ziuetdv

This setup looks good to me @Sfaci! A good question you raised is: Do we want to stop at 1.6% (so that we can say that 1% of enwiki is safe for experimentation), or do we want to keep going until we see an impact?

In T408133#11370867, @phuedx wrote:

In T408133#11366050, @pfischer wrote:

Regarding CirrusSearch: Do you already have particular open questions/obstacles related to the A/B test scenarios covered in the backend?

• Session starting by following a link to blank Special:Search
• Session starting by following a link to Special:Search with a query
• Session starting at Special:Search with a 'go'

Thanks @pfischer. A couple of questions spring to mind:

1. Is Scenario 1 treated the same as the other scenarios? In my mental model, a user searching or interacting with the search autocomplete starts a session. Is that correct?

Change #1204815 merged by jenkins-bot:

[mediawiki/extensions/MetricsPlatform@master] Enable experiment enrollment in the MediaWiki Action API

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

Change #1204815 merged by jenkins-bot:

[mediawiki/extensions/MetricsPlatform@master] Enable experiment enrollment in the MediaWiki Action API

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

Change #1206840 merged by jenkins-bot:

[operations/deployment-charts@master] Test Kitchen UI: Deploying v1.1.2 release to production

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