open-feature / open-feature/flagd
[FEATURE] Implement a possibility to track changeEvents throughout the whole software lifecycle
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 997
- Forks
- 136
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 11
Description
Requirements
The 'in-process' providers work great; tracking information spread from flag to the contrib-sdks is hard. It would be a nice addition if we generate and populate a trace ID from flagd to its consumers so we can easily connect logs from all services together.
Goal
Provide an otel trace ID when emitting change events and initial connection with flagd. So we can also utilize them among the providers.
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 locating the code that emits change events and handles the initial connection with flagd, then trace how providers and contrib-SDK consumers receive those events. Define how an OpenTelemetry trace ID is generated and propagated across the full lifecycle; done means change events and the initial connection expose a usable ID to consumers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100