l3montree-dev / l3montree-dev/devguard
Improve Telemetry Data captured via Umami
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 161
- Forks
- 43
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 37
Description
We are collecting anonymized telemetry data to improve for instance incident reponse, see the second screenshot to see what we are capturing
We are collecting too much data, at least to a point where we can't properly understand whats going on anymore.
Functions in the Backend are in telemetry.go
A lot of data is being captured in a runner/ cicd pipeline.
This is quite important since it generally shapes the devguard project, how safely devguard is deployed, and more clearly understand Backporting decisions
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 reading telemetry.go, then trace how telemetry is collected in the runner and CI/CD pipeline. Compare the captured fields with the screenshots and identify which data should be reduced or generalized, including version values; done means the telemetry is more understandable while preserving the intended incident-response insight.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devops, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100