-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Metrics (esp. synapse_notifier_users) and workers #7312
Comments
Hey there, which worker are you trying to retrieve this metric from? From what I can see, only the synchrotron ( To retrieve metrics from a worker, just add the following to its configuration file, under the - type: metrics
bind_address: ''
port: 9101 (feel free to edit the |
Ok thanks for the pointer.. we were receiving the URL from the main homeserver process.. |
It doesn't seem to be documented anywhere and means that you suddenly start losing metrics without any obvious reason when you go from monolith to workers (e.g. #7312).
Gah, sorry, I missed your reply.
Yes, different workers will handle different data and thus they'll all expose different timeseries.
Yup. The general rule here is that if you want to monitor a cluster of workers you should monitor every worker, not only the master. This isn't clear in the documentation so I've opened #7357 to address that. I'm going to close this issue now. If you have further comments or questions, feel free to join #synapse:matrix.org and share them there, as it is our main support channel :) |
It doesn't seem to be documented anywhere and means that you suddenly start losing metrics without any obvious reason when you go from monolith to workers (e.g. #7312).
It doesn't seem to be documented anywhere and means that you suddenly start losing metrics without any obvious reason when you go from monolith to workers (e.g. matrix-org#7312).
Description
Is the assumption correct that
synapse_notifier_users
should reflect the number of active user devices at a given time?Since activating workers,
synapse_notifier_users
has turned to 0.0, leaving us without this vital measure of server activity.. With 7k+ users atm... 😅 💦Here's a dump of our metrics.gz..
Steps to reproduce
synapse_notifier_users 0.0
Version information
The text was updated successfully, but these errors were encountered: