This task covers client-side code for a variety of APIs owned by different teams. Perhaps it would make sense to split it into separate tasks, each covering the client side code for functionality owned by a given team.

In T359383#9722417, @daniel wrote:

This task covers client-side code for a variety of APIs owned by different teams. Perhaps it would make sense to split it into separate tasks, each covering the client side code for functionality owned by a given team.

I agree, and that makes sense. I would greatly appreciate it if folks could kindly break down the subtasks for any metrics they support under this list, as I currently lack sufficient context around MW code/service ownership to do so.

In T359383#9755431, @colewhite wrote:

These metrics were migrated as part of https://gerrit.wikimedia.org/r/c/mediawiki/core/+/990176

That takes care of all the keys that contain .executeTiming. and .extraDataTiming..

From the way the keys are grouped in the task description, I assumed that some API modules emit additional metrics... was I wrong about that? Or do they do this using a different prefix? I just saw that the ContentTranslation extension's API modules record a metric under MediaWiki.cx., rather than MediaWiki.api.cx... Is that the case for all extensions?

In T359383#9764864, @daniel wrote:

From the way the keys are grouped in the task description, I assumed that some API modules emit additional metrics... was I wrong about that? Or do they do this using a different prefix? I just saw that the ContentTranslation extension's API modules record a metric under MediaWiki.cx., rather than MediaWiki.api.cx... Is that the case for all extensions?

Most extensions I've seen so far follow the pattern you describe.

I can't say for sure if it's 100% consistent across all extensions, but I have yet to find evidence of api prefix usage outside of core.

In T359383#9765763, @colewhite wrote:

In T359383#9764864, @daniel wrote:

From the way the keys are grouped in the task description, I assumed that some API modules emit additional metrics... was I wrong about that? Or do they do this using a different prefix? I just saw that the ContentTranslation extension's API modules record a metric under MediaWiki.cx., rather than MediaWiki.api.cx... Is that the case for all extensions?

Most extensions I've seen so far follow the pattern you describe.

I can't say for sure if it's 100% consistent across all extensions, but I have yet to find evidence of api prefix usage outside of core.

So much the better. I got my initial assessment wrong then. Apologies.