-
|
Hello, I'm looking at the (excellent in general) Envoy Gateway docs in order to ship opentelemetry traces to an otel-collector's grpc endpoint. It's in the namespace When I look at the API Reference, it says that Here's a commented version of what I mean: apiVersion: gateway.envoyproxy.io/v1alpha1
kind: EnvoyProxy
metadata:
name: gwclass-tier1
namespace: gateways
spec:
mergeGateways: true
telemetry:
tracing:
# sample 100% of requests
samplingRate: 100
provider:
# Deprecated style works ->
host: otel-collector.monitoring.svc.cluster.local
port: 4317
# backendRefs: # Preferred style (commented here) does not work
# - name: otel-collector
# namespace: monitoring
# kind: Service
# port: 4317
type: OpenTelemetryIs it possible this is due to API versions or something? I was trying to enable debug logs but wasn't sure which logs to enable. Versions:
|
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 4 replies
-
|
Without #7694, you need to make sure the |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the quick reply! We can wait for a future release if grpc becomes the default, then. Is there more information on setting |
Beta Was this translation helpful? Give feedback.
-
|
ah, got it. thank you. |
Beta Was this translation helpful? Give feedback.
-
|
just to follow-up: I updated my otel-collector kind: Service
apiVersion: v1
metadata:
name: otel-collector
namespace: monitoring
spec:
selector:
app.kubernetes.io/name: opentelemetry-collector
ports:
- name: otlp
protocol: TCP
port: 4317
targetPort: 4317
appProtocol: grpcThank you again for the help, @zirain |
Beta Was this translation helpful? Give feedback.
Without #7694, you need to make sure the
appProtocolconfiged to use grpc.