Proposal to add workflow name and target metric labels

[mumoshu]

Why are you starting this discussion?

Product Feedback

What GitHub Actions topic or product is this about?

ARC (Actions Runner Controller)

Discussion Details

Hey 👋

While managing a bunch of workflows and jobs along with ARC-managed runners, I often wanted to obtain fine-grained metric labels that enable me to answer a question- on which tag/branch/pull request this specific workflow and its jobs unexpectedly took longer to run?

Anyone having same or similar problems? How have you addressed it? Was job_workflow_ref label was enough for you?

Anyway, here's my PR that enables you to optionally add job_worflow_name and job_workflow_target labels derived from job_workflow_ref(#4054).

actions/actions-runner-controller#4240

This might be a nice-to-have because those labels can be derived from job_workflow_ref anyway.
But I wanted this enough times, so I used my spare time to submit a PR and hear your thoughts/experience.

FYI, here's a list of benefits I can think of:

• In some metrics systems, it's not trivial to rewrite or programatically split metric labels into two (for example, Datadog). Having two distinct metric labels out of the box is beneficial there.
• GHA performance as of today does not allow us to see metrics over time per workflow target (tag, branch, pull request head)

Hope this makes sense!

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[Samsanga]

@mumoshu, Currently, the metrics provide only the job_name and job_workflow_ref. While adding job_workflow_target is beneficial, when a job fails, we still need to manually navigate to the repository, find the correct workflow run, and locate the job. This process is slow and inefficient.

To streamline debugging, could we include the job_url (the html_url from the GitHub API) in the metrics? This would provide a clickable link, directing us to the relevant job page and its logs.

Example URL format:
https://github.com/example-org/example-repo/actions/runs/RUN_ID/job/JOB_ID

"html_url": "https://github.com/actions/actions-runner-controller/actions/runs/17616844150/job/50052101535"

This would significantly speed up troubleshooting and make it possible to automate our response to common failures.