open-feature / open-feature/flagd
[RESEACH] Add comprehensive metrics and tracing
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 998
- Forks
- 136
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 11
Description
First, there is some research to do. We must identify the question we want to answer here
- how many clients are listening?
- how many flags have been evaluated?
- how many evaluations are erroring?
- sync source update data/metrics, when were they last updated?
- latency/duration of flag evaluations
- what flags-sets/sources/versions are available
- what selectors are used by client
- propagation time from source update to client notification
Once we understand these, we need to build metrics for them. This may be done as sub issues.
Relates to: https://github.com/open-feature/flagd/issues/1141
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
No files, tests, or entry points are named. Begin by reviewing the listed research questions and related issue #1141, then define the metrics and tracing scope; done requires an agreed set of measures and a plan to implement them, potentially as sub-issues.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100