actions / actions/actions-runner-controller
Adding support for open telemetry
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.5k
- Forks
- 1.5k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 27
Description
Is your feature request related to a problem? Please describe.
Often we have trouble distinguishing whether root cause of any issue is something with the controller or our own self-hosted infrastructure. For example I'd like to see how long specific methods in the reconcilation loop are taking to run, to rule out any issues.
Describe the solution you'd like
Similar to open metrics I'm thinking we can add support for open telemetry.
Describe alternatives you've considered
We've enabled the open metrics which has already given us a lot more insight, but I think tracing will take it further.
Additional context
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the controller's reconciliation loop and the existing OpenMetrics support mentioned in the issue. Identify which methods need tracing and what OpenTelemetry integration should cover; done should provide useful traces for diagnosing controller versus self-hosted infrastructure latency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100