actions / actions/actions-runner-controller

Gauge metrics missing repository and enterprise label values

Open
#4,304 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

Description

I’ve noticed that all gauges metric are not populating the repository and enterprise label

In contrast, the gha_started_jobs_total and gha_completed_jobs_total counters do populate the repository label as expected. This inconsistency makes it hard to correlate job lifecycle metrics with current runner state.

  • gha_running_jobs labels: [name, namespace, repository, organization, enterprise]
  • Actual populated fields: name, namespace, and organization repository and enterprise remain empty (e.g., repository="", enterprise="")
Expected behavior:

The repository label should be populated for jobs running from repository-level runners, similar to how it appears in gha_started_jobs_total.

Request / question

Can you confirm whether this is the expected behavior is a bug/limitation in how repository context is passed to gauges?
If expected, is there a recommended configuration or update that would allow repository-level context to appear in the guages metric?

Regards,

Javier G.

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

Start by tracing how the gha_running_jobs gauge receives its repository and enterprise labels, then compare that path with the gha_started_jobs_total and gha_completed_jobs_total counters. Confirm whether repository-level runner context can populate those labels; done means either preserving the expected values or documenting the limitation and configuration needed.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, go, kubernetes
Domain
observability
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.