I confirmed with @MarkTraceur (who then confirmed with @cchen) that the instrumentation could be removed.

In T299914#7972679, @RLazarus wrote:

@EChetty Hi from the SLO project! Thanks for this -- Will asked me to have a look at the schema, from the POV of where we're going next with the edit save SLO. Broadly I think this is going to have everything we need, just a couple of clarification questions.

• I see http.status_code and friends in the diagram at the top of this task, but not in the schema on Wikitech -- can I count on being able to use those fields? <snip>

Thanks for the ping!

I split out the removal of the EventLoggingSchemas entries in the hopes that it'll ease moving this task along.

In T306181#8013301, @Ottomata wrote:

Thanks ben!

Mark the schema as inactive

Thanks to @matmarex for the C+2.

Mark the legacy ArticleCreationWorkflow schema as inactive

UPDATE - there is an easier way of implementing event-logging as per a conversation with @phuedx -> the new Metrics Platform has simplified the process and removed the need to create yaml files for new streams. We will use this new method as it is currently in production. Please see new mono-yaml file with all the usual metric suspects here

In T294911#7991260, @BTullis wrote:

Now the only endpoint which appears to take longer than all of the rest is the /v1/_test/events path. This is consistently much slower than all of the other endpoints, across all eventgate deployments.

In T186627#7987841, @phuedx wrote:

The to-be-deprecated status has also been reflected on Special:ApiSandbox (per T210808#5734042) and was also documented on the mw:Extension:MobileFrontend/MobileViewApi (per https://www.mediawiki.org/w/index.php?title=Extension:MobileFrontend/MobileViewAPI&oldid=2988404).

However, not announcing the deprecation via the standard channel was an oversight.

In T186627#7986587, @Jdlrobson wrote:

I think there has been ample warning, particularly the obnoxious warnings that have been showing in responses for the last 2 months so not all is lost.

• Inspecting the loaded stream configs

Notes on the EAS instrument's (down)sampling rates:

Migrate the instrument in the DiscussionTools extension

☝️ Per T281773#7952266.

Thanks for taking the time to write this up, @Krinkle.

Here's the example stream configuration that I landed on while working through the migration:

In T281762#7941021, @phuedx wrote:

In order to properly integrate the PHP Metrics Platform client (the "client") (https://gerrit.wikimedia.org/r/c/mediawiki/extensions/EventLogging/+/791319) the following changes need to be made…

In T306181#7914450, @akosiaris wrote:

I notice that things that take like 1s to be served are things make 0 sense to take 1s to serve. Like /robots.txt or /_info. Those are extremely cheap endpoints (returning a small text file or a 1 liner of JSON) IIRC.

In T307774#7957152, @Ottomata wrote:

Should we also remove the tables and data from the event database?

Being bold. The single subtask of this epic, which appears to be a duplicate of this task, has been closed as Resolved.