Is the metric label actions_github_com_scale_set_name requirement in the demo dashboard accurate? #161939
-
Why are you starting this discussion?Question What GitHub Actions topic or product is this about?Metrics & Insights Discussion DetailsIn this example dashboard document, you stipulate some required labels. I don't see references to Is this something you expect users to attach at metric-ingestion time? Strikes me as an odd name for a user-provided label. |
Beta Was this translation helpful? Give feedback.
Replies: 11 comments 3 replies
-
|
I got clarification on this here: https://github.com/orgs/community/discussions/160451#discussioncomment-13005956 |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
@GlacierWalrus I've encountered this as well and just wanted to contribute to the discussion. It's certainly perplexing that actions_github_com_scale_set_name is a required field in the dashboard with no explanation of how or where it's being set within the Helm chart. I also didn't see it referenced in the values.yaml or within the Prometheus job configs themselves. Upon reading @nocturne1's response and diving into it, I concur: the label must be applied manually during Prometheus scraping, usually through relabel_configs. That should most likely be spelled out more explicitly in the docs or auto-exported by the Helm chart, as the label values are already known at deployment time. It'd be nice if the dashboard either gracefully dealt with the lack of this label or the chart exported it automatically. |
Beta Was this translation helpful? Give feedback.
-
|
Internal or Legacy Artifact: |
Beta Was this translation helpful? Give feedback.
-
|
Ensure your documentation reflects the latest run timestamps (e.g., current attempt) for accurate metrics. |
Beta Was this translation helpful? Give feedback.
-
|
Hey folks, I'm going through the example dashboard doc, and I noticed that it mentions a required label: actions_github_com_scale_set_name. I couldn’t find this label anywhere in the Helm chart values or other parts of the documentation. Is this something we're supposed to manually attach when ingesting metrics? It feels like an oddly specific name for something a user would provide — sounds more like something that might be auto-injected by GitHub or some internal infrastructure. Just trying to understand whether this is required in self-hosted setups, or if it's safe to ignore/remove it from the example if it's not relevant to our deployment. Appreciate any clarification! Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
The confusion around actions_github_com_scale_set_name seems to stem from a mismatch between the example dashboard expectations and what's actually exposed in self-hosted deployments. Recommended Fixes:
Let me know if a sample relabel_configs block or dashboard patch would help — happy to contribute. |
Beta Was this translation helpful? Give feedback.
-
|
You're absolutely right to question that — This label is most likely intended for setups using self-hosted runners in autoscaled environments, such as:
In those cases, this label is expected to be manually attached during metric ingestion, for example:
The purpose is to tag metrics with a runner pool or scale set name, allowing dashboards to group and filter data more effectively — especially in multi-tenant or enterprise-scale environments. That said, I agree with your observation: |
Beta Was this translation helpful? Give feedback.
-
|
It did seem like actions_github_com_scale_set_name might have been an internal label from GitHub-hosted runners rather than something users are expected to provide. Since it’s not referenced in the Helm chart or ingestion pipeline, I just wanted to double-check whether it was an oversight or if we’re supposed to replicate that label ourselves. Would it make sense to either: Update the dashboard to remove the dependency on that label (if it’s not critical), or Add a note in the documentation explaining how/when users should provide it (if needed)? Happy to open a PR if a change is needed. |
Beta Was this translation helpful? Give feedback.
-
|
actions_github_com_scale_set_name is not included by default in the Helm chart or exporter config. It’s expected to be manually attached during metric ingestion, likely via Prometheus relabeling or a custom setup. The label is likely used to identify scale sets in self-hosted runner environments. It’s not mandatory unless your infrastructure requires that level of detail. You can safely replace it with a more relevant label for your environment. |
Beta Was this translation helpful? Give feedback.
-
|
Please clarify:
General Answer (assuming Prometheus + GitHub Actions + autoscaler):
What You Should Check
|
Beta Was this translation helpful? Give feedback.


I got clarification on this here: https://github.com/orgs/community/discussions/160451#discussioncomment-13005956
It requires prometheus scraping changes.