Skip to content

OpenTelemetry integration #1097

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
adri1197 opened this issue Apr 15, 2025 · 1 comment · May be fixed by fluxcd/flux2#5321
Open

OpenTelemetry integration #1097

adri1197 opened this issue Apr 15, 2025 · 1 comment · May be fixed by fluxcd/flux2#5321

Comments

@adri1197
Copy link

adri1197 commented Apr 15, 2025 •
edited
Loading

Hello!

We would like to know if there is any plan to add OpenTelemetry for notification-controller in order to get traces of out of FluxCD for debugging and get better visibility. Found the following discussion about it (fluxcd/flux2 #370), following a similar implementation as Alerts CR.

Thereby, is this implementation still applicable? We're really interested in having it in. Also, we're willing to contribute if needed.

Any comments @stefanprodan @matheuscscp?

Thanks in advance!
@stefanprodan
Copy link
Member

Hey @adri1197 we'll need an RFC for the Trace API in notification-controller. Given that Flux controllers are stateless, I'm not sure how a span could include both source-controller and kustomize-controller/helm-controller events (the revision annotation being the key), so this should be addressed in the RFC.

@adri1197 adri1197 linked a pull request Apr 24, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[RFC-0011] OpenTelemetry Tracing RFCS adri1197/flux2
2 participants
@stefanprodan @adri1197