Access a summary of API feature usage logs by user agent. For more information, see the extension wiki page.
Details
Fri, Aug 30
Change #1058672 merged by jenkins-bot:
[mediawiki/core@master] api: make ApiMain::getUserAgent() only use api-user-agent when set
Change #1058672 had a related patch set uploaded (by Krinkle; author: Aaron Schulz):
[mediawiki/core@master] api: make ApiMain::getUserAgent() only use api-user-agent when set
Jul 29 2024
Jul 26 2024
Change #1057269 had a related patch set uploaded (by Aaron Schulz; author: Aaron Schulz):
[mediawiki/extensions/ApiFeatureUsage@master] Various improvements to ApiFeatureUsageQueryEngineSql
Jul 25 2024
Creating new tables needs to be signed off by a DBA beforehand: https://wikitech.wikimedia.org/wiki/Creating_new_tables
Jul 18 2024
Change #1020385 merged by jenkins-bot:
[mediawiki/extensions/ApiFeatureUsage@master] Add option to use a SQL table instead of ElasticSearch
Jun 14 2024
Change #1020383 merged by jenkins-bot:
[mediawiki/core@master] Add ApiLogFeatureUsage hook
Apr 16 2024
Change #1020385 had a related patch set uploaded (by Aaron Schulz; author: Aaron Schulz):
[mediawiki/extensions/ApiFeatureUsage@master] WIP: add option to use a SQL table instead of ElasticSearch
Change #1020383 had a related patch set uploaded (by Aaron Schulz; author: Aaron Schulz):
[mediawiki/core@master] [WIP] Add ApiLogFeatureUsage hook
Apr 10 2024
Apr 9 2024
Apr 5 2024
Feb 29 2024
Feb 23 2024
Change 869582 abandoned by Gehel:
[operations/puppet@production] ApiFeatureUsage logstash servers are owned by Observability.
Reason:
Feb 8 2024
Jan 30 2024
Yes. It's not just replication, there are many more pieces in our infra.
In any case, I'm fine with having periodic pruning on the INSERT/UPDATE. My main preference is to not have it tied to the special page SELECT.
Yes, That's how other pruning of old rows works in mediawiki (RC, CU, etc.) and for the sake of simplicity of architecture, it should just reuse the same concepts if not the same code.
Not to mention we just had a page due to the switchover.
Jan 25 2024
I'd rather not have the writes be cross-datacenter, tying up the working thread in the post-send stage of web requests, especially given the potential for spikes. If there was some aggregation service in the middle (batching/flushing counter updates), that would less risky, though more complex.
Jan 8 2024
The ApiFeatureUsage extension, or more specifically the SpecialPage frontend and Action API module, ultimately just need a table with incrementing counters.
Dec 3 2023
Oct 8 2023
Sep 18 2023
Change 958021 merged by jenkins-bot:
[mediawiki/extensions/ApiFeatureUsage@master] Use HookHandlers for core hook
Sep 16 2023
Change 958021 had a related patch set uploaded (by Umherirrender; author: Umherirrender):
[mediawiki/extensions/ApiFeatureUsage@master] Use HookHandlers for core hook