How to approch Distributed Tracing for FluxCD

[adri1197]

I'm implementing distributed tracing for a Kubernetes controller that processes events and converts them into trace spans asynchronously. This one called notification-controller manages GitOps reconciliation events with hierarchical relationships (Source -> Kustomization → ). The challenge is establishing parent-child span relationships when:

• Parent spans are created and ended before child events arrive.
• Child spans need to reference a parent that no longer exists in memory (completely stateless).
• The parent SpanContext must be reconstructed from stored identifiers (Source UID + revision)

Therefore, I would like to know what's the proper way of addressing the aforementioned challenges and if any contribution may be required in that sense.