Display 2 most recent runner failures for instance runners in the last hour
Release notes
When managing runners, it isn't clear if a job failed because of a test or code failure, or if it had to do with a runner system failure. We now provide visibility into runner failures in the Fleet Overview Dashboard so admins and group owners can quickly locate runners that have problems and fix them.
Problem to solve
As a platform engineer, I want to know which of my runners have problems/have failed, so I can fix them and get my developers back to working seamlessly.
Intended users
User experience goal
The user should be able to see the runner figures in the last hour and look into the job log for more information.
Proposal
Add a card on the Fleet Overview Dashboard with a limit of the 2 most recent runner failures for instance runners only in the last hour including:
- Relative time of the failure (for example,
20 min ago
) - Error message
- Runner ID and description with a link to the runner's details page
- Link to view the job log
Database
As mentioned in the exploration below, we would need to add a new database table that aggregates the required fields for the recent builds. It would regularly be pruned so that we only keep the last few hours of builds.
GraphQL query
We can leverage a query like get_all_jobs.query.graphql
, with some modified filters
{
jobs(first: 2, statuses: [FAILED], runnerTypes: [INSTANCE_TYPE], failureReason: [RUNNER_SYSTEM_FAILURE] ) {
nodes {
runner {
id
description
adminUrl
}
status
detailedStatus {
...
}
trace {
htmlSummary(lastLines: 2)
}
}
}
}
Further details
Permissions and Security
Documentation
Availability & Testing
Available Tier
Feature Usage Metrics
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
What is the competitive advantage or differentiation for this feature?
Links / references
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.