[CI Runners] include autoscaling into the error ratio metrics
## Summary <!-- Give context for what problem this issue is trying to prevent from happening again. Provide a brief assessment of the risk (chance and impact) of the problem that this corrective action fixes, to assist with triage and prioritization. --> During https://gitlab.com/gitlab-com/gl-infra/production/-/issues/14628 our error ratio didn't change, which is not reflecting the errors we were receiving. ## Related Incident(s) <!-- Note the originating incident(s) and link known related incidents/other issues. The relation will happen automatically if you are creating this issue from an incident, if this isn't done already please uncomment the following line: --> Originating issue(s): production#14628 ## Desired Outcome/Acceptance Criteria <!-- How will you know that this issue is complete? If you have any initial thoughts on implementation details (e.g. what to do or not do, gotchas, edge cases etc.), please share them while they are fresh in your mind. --> Autoscaling has it's own SLI which eventually contributes to the service Apdex. ## Associated Services <!-- Apply the appropriate services associated with this corrective action if applicable. --> production-engineering~13295602 ## Corrective Action Issue Checklist * [x] Link the incident(s) this corrective action arose out of * [x] Give context for what problem this corrective action is trying to prevent from re-occurring * [x] Assign a severity label (this is the highest sev of related incidents, defaults to 'severity::4') * [x] Assign a priority (this will default to 'Reliability::P4')
issue