Replies: 1 comment
-
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
Beta Was this translation helpful? Give feedback.


Uh oh!
There was an error while loading. Please reload this page.
-
Why are you starting this discussion?
Product Feedback
What GitHub Actions topic or product is this about?
Actions Runner
Discussion Details
I work for a relatively large financial services company, and we use mostly self-hosted Actions Runners for a number of reasons related to our domain and regulatory concerns.
One issue we've repeatedly had with the Runner is job startup times that are tough to troubleshoot. We have distributed OpenTelemetry tracing for almost all of our other core services, so it's quite frustrating to have only metrics available when debugging Runner performance issues. Consider this a request to add tracing support for the Runner.
Possible Criteria
tracing_enabled, to toggle tracing on/offtracing_enabled:falsetis_enabled, to toggle TLS for the Otel exporter endpoint on/offtls_enabled:trueservice.nameResource attribute must be set for all traces emittedOut-of-Scope
Beta Was this translation helpful? Give feedback.
All reactions