You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Support tracing via the ObservabilityPolicy (#2004)
* Support tracing via the ObservabilityPolicy
Problem: As a user, I want to be able to enable tracing for requests flowing through NGF to my backend applications, so I can understand and debug my requests.
Solution: Using the ObservabilityPolicy, an app dev can now enable and configure tracing for their Route(s). The policy will only be applied if the NginxProxy configuration containing the tracing collector endpoint has been defined and attached to the GatewayClass. The policy can be attached to one or more HTTP or GRPC Routes.
Updated span attributes from the NginxProxy to be applied at the location block context, otherwise they are overwritten.
Also added functional tests to ensure that the complete solution is working.
* Add functional tests for tracing
Verify end to end tracing by creating a collector and sending trace data to it.
Test cases:
1. one policy attached to one route
2. one policy attached to multiple routes
// +kubebuilder:validation:XValidation:message="TargetRef Kind must be: HTTPRoute or GRPCRoute",rule="(self.exists(t, t.kind=='HTTPRoute') || self.exists(t, t.kind=='GRPCRoute'))"
51
+
// +kubebuilder:validation:XValidation:message="TargetRef Group must be gateway.networking.k8s.io.",rule="self.all(t, t.group=='gateway.networking.k8s.io')"
0 commit comments