Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Consider adding the worker name to the user agent for HTTP replication calls #12807

Open
turt2live opened this issue May 20, 2022 · 2 comments
Open
Labels
T-Enhancement New features, changes in functionality, improvements in performance, or user-facing enhancements.

Comments

@turt2live
Copy link
Member

This will help track down which worker exactly is making a request to another worker, such as where traffic on the main process might be coming from exactly.

Alternatives are to grep a bunch of logs to see if a worker can be identified, however this is extra work.

@babolivier babolivier added the T-Enhancement New features, changes in functionality, improvements in performance, or user-facing enhancements. label May 20, 2022
@realtyem
Copy link
Contributor

Is this still of interest?

@realtyem
Copy link
Contributor

If so, with the above mentioned PR, could also add

master | 2023-04-22 21:48:39,554 - synapse.http.client - 891 - DEBUG - POST-3 - Sending request POST http://event_persister1/_synapse/replication/send_events/GxzWGTCSVa
event_persister1 | 2023-04-22 21:48:39,560 - synapse.access.http.18009 - 416 - DEBUG - POST-5 - master[POST-3] - 18009 - Received request: POST /_synapse/replication/send_events/GxzWGTCSVa

as a possibility. Note specifically the master[POST-3] in the second line, which is the context/request_id from master.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
T-Enhancement New features, changes in functionality, improvements in performance, or user-facing enhancements.
Projects
None yet
Development

No branches or pull requests

3 participants