diff options
| author | Eric Eastwood <erice@element.io> | 2025-06-05 15:30:28 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-06-05 15:30:28 -0500 |
| commit | e80bc4b0621074a395741d1ccb2955c811f1dd7a (patch) | |
| tree | 829ffe5c08e7089c25f3fe9c15ee1c9521875578 /synapse/module_api/callbacks/ratelimit_callbacks.py | |
| parent | docs: render missing docs for scheduled tasks admin api (#18516) (diff) | |
| download | synapse-e80bc4b0621074a395741d1ccb2955c811f1dd7a.tar.xz | |
Distinguish all vs local events being persisted in the "Event Send Time Quantiles" graph (#18510)
(Applies to the Grafana graphs) As discovered by @devonh, we use `synapse_storage_events_persisted_events_total` (which tracks *all* persisted events) for the "Events" rate in the "Event Send Time Quantiles" graph. This is pretty misleading as I would expect it to be the rate of events being sent given the graph title, "Event Send Time Quantiles". Since the event persistence queues are shared for local and remote events from federation and will block local events being sent, I think it does still make sense to have the event persist rate. I've updated the graph to include the rate of "Local events being persisted" and the rate of "All events being persisted". I think this properly disambiguates and clarifies what the graph is trying to show.
Diffstat (limited to 'synapse/module_api/callbacks/ratelimit_callbacks.py')
0 files changed, 0 insertions, 0 deletions