Can we implement a metric to be published for the Run Id of each job?

What would you like added?

A clear and concise description of what you want to happen.

Can we implement a metric to be published for the Run Id of each job?

I'm trying to setup some monitoring now with Prometheus and the metrics that are shared feel a little light. I'd like to ideally get the Run Id (github.run_id) so I can isolate which jobs are taking the longest to run and if that is specific to our github workflows or the application teams code bae.

The Run Id would help me narrow down the longer running workflows. I have the repository but no Run Id - so it is hard to review historical data (we have ephemeral runners and I believe this may be the reason run_id might not exist).

Why is this needed?

To help isolate Github Workflow runs against executions times and completely/incompleted jobs

Additional context

My assumption is this is possible as the job_workflow_ref is shared - however I can see potential limitations through Long Lived Runners vs Ephermal runners - hope this is not the case.

The GHA metrics shared by kenmuse are helpful however are feeling a little thin the more observability you want

Start by tracing the existing Prometheus metrics for jobs and how job_workflow_ref is exposed in actions-runner-controller. Check whether github.run_id is available for ephemeral and long-lived runners, then define completion as publishing a usable Run Id alongside each job metric without breaking the existing metric behavior.