microsoft / microsoft/FeatureManagement-Dotnet
OpenTelemetry: Semantic Conventions for Feature Flags
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.2k
- Forks
- 129
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 5
Description
Previous discussion: #412
We used to follow the feature flag in span (defined in OTEL spec 1.27) path, so we build the telemetry story on ActivityEvent of the .NET Activity system.
But, recently, I found in OTEL spec 1.30, "feature flag in span" has been removed. There is only "feature flag in log`. We should revisit the decision we've made.
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 reading the previous discussion in issue #412 and the current use of .NET ActivityEvent for feature-flag telemetry. Compare that decision with the linked OpenTelemetry 1.30 semantic conventions. Done requires a settled direction for the span-based approach and the resulting implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- observability
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100