Review Request - Impact of refresh rate setting on monitoring dashboard
Scaling Request
The feature/improvement we'd like some assistance with is:
When users visit our monitoring dashboard, they'll be able to set a refresh rate to keep their screen of to date.
The refresh rate can be 5, 10, 30 seconds or more...
The epic and relevant issues are:
gitlab-org/gitlab#204920 (closed)
The reason we're asking for a scaling review on this item is:
In particular, we are concerned about:
-
Memory -
Migrations -
N+1 -
Queueing -
Design implementation -
Other...
We're hoping to release this as part of milestone: %13.2, and we can easily change the refresh rate options to adapt our implementation, so it's not "all-or-nothing".
Usage Details
We may have a high usage rate if/when our dashboards replace https://dashboards.gitlab.net/ as they are public facing.
These are dashboards that we have made public:
Technical Implementation Details
The requests for metrics data are proxied by GitLab and sent to the Prometheus instance HTTP API. Some of the requests can hold relatively large sets of data.
Also, during refresh, each refresh is scheduled to occur only after all data has been loaded, so the actual refresh rate is less than what's shown in the UI.