Skip to content

Re-use already collected ServicePing data

Mikołaj Wawrzyniak requested to merge mwaw/reuse_already_recorded_service_ping_data_from_db_in_application_settings into master

What does this MR do and why?

In admin application settings one can preview SerivcePing payload that would be reported from given instance. Since ServicePing collection is heavy process it can take longer time to complete and result in timeout error. In order to avoid re generating payloads and improve performance, this commit first try to find recent payload recorded in RawUsageData relation before re calculating anything.

This is MVC for: #354139 (closed)

In follow up MRs it will be delivered so the payload is generated in background job also for instances that not yet opted in for ServicePing reporting. Such report would be stored in DB but will NOT BE SENT TO GITLAB WITHOUT USER CONSENT

Screenshots or screen recordings

These are strongly recommended to assist reviewers and reduce the time to merge your change.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports