You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having this data in Job Server and also within Grafana will allow us to:
(1) proactively manage user experience and therefore reduce copilot support burden
(2) scale the service to prevent critical resource exhaustion and the resulting firefighting and sadness
We believe that Job Runner can provide this information in the data it sends up to Job Server. Job Server can then store this data with the rest of the information about a Job.
We don't yet know what sort of aggregation to do to provide an accurate measure of CPU/memory/disk, so we should start with something easy to do and build up from there. Once it's stored in the Job Server database it will be easy to show in Grafana.
Note: surfacing this information in Job Server is out of scope for this ticket.
The text was updated successfully, but these errors were encountered:
Having this data in Job Server and also within Grafana will allow us to:
(1) proactively manage user experience and therefore reduce copilot support burden
(2) scale the service to prevent critical resource exhaustion and the resulting firefighting and sadness
We believe that Job Runner can provide this information in the data it sends up to Job Server. Job Server can then store this data with the rest of the information about a Job.
We don't yet know what sort of aggregation to do to provide an accurate measure of CPU/memory/disk, so we should start with something easy to do and build up from there. Once it's stored in the Job Server database it will be easy to show in Grafana.
Note: surfacing this information in Job Server is out of scope for this ticket.
The text was updated successfully, but these errors were encountered: