ARCHIVED - use Instrument-ClientError instead!
Work related to the client error instrument that reports runtime errors from MediaWiki and other platforms.
ARCHIVED - use Instrument-ClientError instead!
Work related to the client error instrument that reports runtime errors from MediaWiki and other platforms.
Change 700241 abandoned by Gergő Tisza:
[mediawiki/extensions/WikimediaEvents@master] clientError: Use dedicated field for canonical special page name
Reason:
This was done in If8d5732cd2e973df7096b88bdbc824e69bb58961
Thanks for the quick response here!
Resolving per discussion here and normal-looking graphs.
Thank you all! Yes, only the 'analytics' eventgate clusters use dynamic schema lookup. All others rely on schemas baked into their local docker image, so they don't have to be runtime coupled to a remote schema service.
In T319261#8282373, @BTullis wrote:Is anyone else able to confirm whether or not this fix has been successful?
Both logstash and grafana look really good, I think that the task can be closed!
I have merged @elukey's change to eventgate-wikimedia (https://gerrit.wikimedia.org/r/c/eventgate-wikimedia/+/838067) which built a new production eventgate image.
Change 838107 merged by jenkins-bot:
[operations/deployment-charts@master] Bump version of eventgate image that is in use
Change 838107 had a related patch set uploaded (by Btullis; author: Btullis):
[operations/deployment-charts@master] Bump version of eventgate image that is in use
Change 838067 merged by Btullis:
[eventgate-wikimedia@master] blubber: update primary schema registry's git sha
Change 838067 had a related patch set uploaded (by Elukey; author: Elukey):
[eventgate-wikimedia@master] blubber: update primary schema registry's git sha
It seems that the Docker image needs to be rebuilt with a new version of the schema registry, see this prev commit: https://gerrit.wikimedia.org/r/c/eventgate-wikimedia/+/625966/1/.pipeline/blubber.yaml
Tried a roll restart of codfw pods, not successful.
I think that the issue is related to how eventgate-logging-external reads the schemas, namely from local disk only:
(On an aside, the schema version is hardcoded in puppet here, maybe that should be updated. But that's for the beta cluster.)
Failed loading schema at /mediawiki/client/error/2.0.0 with ENOENT (meaning the schema file was not found).
@Tgr @phuedx pinging you given the activity in WikimediaEvents last week (https://gerrit.wikimedia.org/r/c/mediawiki/extensions/WikimediaEvents/+/700242)
I am marking this as a train blocker for now, as it could potentially mean errors leak into production that we don't know about. Feel free to adapt once you've assessed! Thanks in advance!
Change 829300 merged by jenkins-bot:
[mediawiki/extensions/WikimediaEvents@master] Tag errors when a banner is displayed
Change 700242 merged by jenkins-bot:
[mediawiki/extensions/WikimediaEvents@master] clientError: Log everything sent from mw.errorLogger.logError()
Change 829299 merged by jenkins-bot:
[mediawiki/extensions/WikimediaEvents@master] clientError: Add more information to log events
Change 829295 merged by Ottomata:
[schemas/event/primary@master] mediawiki/client/error: rename 'tags' to 'error_context'