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
@@ -1125,30 +1125,24 @@ Port-forward, and send a request through the gateway:
1125
1125
1126
1126
### Tracing and Observability
1127
1127
1128
-
The agentgateway data plane supports comprehensive observability through OpenTelemetry (OTEL) tracing. You can configure tracing using custom ConfigMaps to integrate with various observability platforms and add custom trace fields for enhanced monitoring of your AI/LLM traffic.
1128
+
The agentgateway data plane supports comprehensive observability through OpenTelemetry (OTEL) tracing. You can configure tracing using the `rawConfig` field in AgentgatewayParameters to integrate with various observability platforms and add custom trace fields for enhanced monitoring of your AI/LLM traffic.
1129
1129
1130
1130
For detailed information about tracing configuration and observability features, see the [agentgateway observability documentation](https://agentgateway.dev/docs/reference/observability/traces/).
1131
1131
1132
-
#### Configuring Tracing with ConfigMaps
1132
+
#### Configuring Tracing with RawConfig
1133
1133
1134
-
> **Note**: This approach statically configures tracing at startup. Changes to the ConfigMap are only picked up during agentgateway pod initialization, so you must restart the pod to apply configuration updates.
1135
-
1136
-
To enable tracing, you need to:
1137
-
1138
-
1. **Create a custom ConfigMap** with your tracing configuration
1139
-
2. **Reference the ConfigMap** in your AgentgatewayParameters
1140
-
3. **Deploy your Gateway** with the agentgateway class
1141
-
1142
-
**Step 1: Create a ConfigMap**
1134
+
To enable tracing, configure the `rawConfig` field in AgentgatewayParameters with your tracing settings. Changes to `rawConfig` will automatically trigger an agentgateway pod rollout.
- **ConfigMap Updates**: The ConfigMap is only read during agentgateway pod startup. To apply ConfigMap changes, restart the agentgateway pod (TODO(chandler): DLC: update this README)
1349
-
- **Namespace**: The ConfigMap must be in the same namespace as the AgentgatewayParameters resource
1307
+
- **RawConfig Updates**: Changes to `rawConfig` in AgentgatewayParameters will trigger an agentgateway pod rollout automatically
1350
1308
- **Validation**: Invalid CEL expressions in trace fields will be logged but won't prevent the gateway from starting
1351
1309
- **Performance**: Be mindful of the number and complexity of custom trace fields, as they impact performance
1352
1310
- **Sampling**: Use `randomSampling` to control trace volume in production environments
0 commit comments