Page MenuHomePhabricator

Better identify the multiple WDQS updaters via User-Agents
Closed, ResolvedPublic1 Estimated Story Points


As an operator, I want to be able to quickly identify where traffic is coming from so that I can react (and potentially block it) with a good understanding of the impact.

During a recent appserver overload issue, the new Flink based WDQS updater was blocked by shutting down webproxy. During the outage, it wasn't clear that only the new updater was blocked and the old one wasn't. The user-agent strings are very similar. Having a more descriptive user-agent would allow a better understanding of the situation, especially under stress.


  • old and new updaters have user-agent strings that are different enough and unambiguous

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript
dcausse claimed this task.
dcausse added a subscriber: dcausse.

the updater can now be configure with a user_agent (was done as part of T278385)