open-feature/flagd

[FEATURE] Implement a possibility to track changeEvents throughout the whole software lifecycle

Open

#1,388 opened on Aug 28, 2024

View on GitHubContributor guide
 (2 comments) (3 reactions) (0 assignees)Go (118 forks)github user discovery
enhancementhelp wanted

Repository metrics

Stars
 (925 stars)
PR merge metrics
 (Avg merge 3d 9h) (8 merged PRs in 30d)

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

Research direction
Implement OpenTelemetry trace ID propagation in flagd change events and initial connections to enable end to end tracing across services.
Tech stack
goopentelemetry
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoOpenTelemetry
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50