Repository navigation
[FEATURE] Implement a possibility to track changeEvents throughout the whole software lifecycle #1388
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.
Reacted by Todd Baert, Kavindu Dodanduwa and chrfwow
Activity
Rahul-Baradol commentedon Jun 14, 2025
@aepfli @toddbaert
Could you please elaborate more on what you mean by
changeEventsSo one thing I observed was that there are no traces being generated when a client (running
in-processprovider), hitsflagdvia port 8015 (for flag syncing)...Are we talking about that, or is it something totally different !?
aepfli commentedon Jun 14, 2025
Oh I forgot about this issue, there is a PR open regarding this, linked to a spec ticket. But this is still in discussion. Please see #1595 and open-feature/spec#313