actions / actions/actions-runner-controller

Listener-Specific Metrics Dashboard

Open
#3,753 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

community enhancement needs triage
Dominant language
Go
Stars
6.5k
Forks
1.5k
Avg merge
2d 2h
Merged PRs (30d)
27

Description

Requirements:

Per Listener Metrics:

A chart/dashboard that shows real-time metrics for specific listeners.The chart should include:
Number of running jobs.
Number of queued jobs.
Idle runners.
Failed jobs.
Average job duration.
Resource utilization (CPU, memory).
Listener Filter:

Ability to filter or segregate data based on listener type.
Option to display cumulative data or drill down into specific runners' performance.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue provides no file, test, or entry point to start from. First map the repository's existing metrics and dashboard-related components, then determine how listener and runner data are exposed. Done means a real-time dashboard supports the listed metrics and listener filtering, including cumulative and runner-specific views.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, go, kubernetes
Domain
devops, observability
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.