OpenTelemetry Integration #370
-
|
We would like to get traces out of Flux to help debug issues with Flux and get visibility on what's happening. This is even more valuable now that Flux is broken up into different controllers. Would it be possible to integrate with OpenTelemetry? Example use case:
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 3 replies
-
|
Similar to to how we defile alerts we could extend notification-controller to collect and push traces to an OpenTelemetry provider. Define a tracing provider: apiVersion: notification.toolkit.fluxcd.io/v1beta3
kind: Provider
metadata:
name: jaeger
namespace: flux-system
spec:
type: otel
address: http://jaeger-collector.jaeger:4318/v1/tracesEnable tracing for specific reconciliations: apiVersion: notification.toolkit.fluxcd.io/v1beta3
kind: Alert
metadata:
name: alert-test-1
namespace: flux-system
spec:
providerRef:
name: jaeger
eventSeverity: info
eventSources:
- kind: GitRepository
name: '*'
namespace: test-1
- kind: Kustomization
name: '*'
namespace: test-1
eventMetadata:
env: staging
cluster: cluster-1
region: eu-west-1Based on the above config, notification-controller would parse the events received and create a span for each source revision. |
Beta Was this translation helpful? Give feedback.
-
|
@stefanprodan Are there any plans on adding OpenTelemetry-Support in the near future? |
Beta Was this translation helpful? Give feedback.
-
|
PR was just merged and will be released in Flux 2.7, end of September: |
Beta Was this translation helpful? Give feedback.
Similar to to how we defile alerts we could extend notification-controller to collect and push traces to an OpenTelemetry provider.
Define a tracing provider:
Enable tracing for specific reconciliations: