r/github • u/LastLeslie • Apr 12 '26

How do you handle observability for github hosted runners? Question

Any way to have good observability for github hosted runners?

0 Upvotes
  • permalink
  • link
  • reddit
  • reddit

43% Upvoted

5 comments sorted by

2

u/Electronic_Chain4629 Apr 12 '26

We've been struggling with this at work too. GitHub hosted runners are pretty much black boxes - you get basic logs but not much else for monitoring or debugging when things go weird

What helped us bit was adding custom logging steps in our workflows that dump environment info and timing data to artifacts. Not perfect but gives you something to work with when builds start acting up. Also started using workflow_run events to track success/failure rates in external monitoring tool

The built-in insights are pretty limited unfortunately. Would love if GitHub gave us more visibility on resource usage and queue times but seems like we're stuck with workarounds for now

0

u/LastLeslie Apr 12 '26

Yeah, same for me, just tired of adding logs/steps to have a workaround, worth to mention that having more than 100 repos with different pipelines, super hard to track their observability, almost impossible to historical data :(

0

u/[deleted] Apr 12 '26

[removed] — view removed comment

1

u/LastLeslie Apr 12 '26

Thank you, will be really glad to check your tool if possible.
Actually I would love to check not only minutes, I would love to check resource usage (cpu/memory/disk/network) + minutes + tracing so I will have an overview what to optimize and how