[Core] System instrumentation with telemetry
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5
- Forks
- 4
- Avg merge
- 9h 49m
- Merged PRs (30d)
- 55
Description
About
We would like omniload to be instrumented and emit system telemetry, optimally using OpenTelemetry.
Details
We discovered a dlt collector component that converges to OpenTelemetry by @lfagliano. However, the patch was rejected from mainline dlt, so we could easily ship it with omniload when there are no objections? 🙏
Tests
We would like to be able to automatically test this end-to-end on both our workstations and on an off-the-shelf CI environment, optimally GitHub Actions.
Documentation
The feature/outcome should be documented well and easy for users to follow and exercise. Currently, there is no corresponding place in the documentation, so let's start a new section to bundle all relevant information.
Contributor guide
No contributing guide indexed for this repository
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 linked dlt collector issue and rejected pull request to understand the proposed telemetry approach. Define end-to-end coverage for workstations and an off-the-shelf GitHub Actions environment, then add a documentation section explaining how users can exercise the feature.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd, data-engineering, documentation, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100