Open franco-bocci opened 1 year ago
hi, please raise the issue on seldon core repository https://github.com/SeldonIO/seldon-core/
actually - I was able to transfer it
The field was renamed to opentelemetry.disable
and it still does not work if this field is set to true
. I get errors from multiple resources within Seldon Core v2 with log:
2023/11/07 14:13:30 max retry time elapsed: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp: lookup seldon-collector.seldon-mesh on 169.254.20.10:53: no such host"
The images and tags I use are:
agent:2.6.0
rclone:2.6.0
scheduler:latest
,envoy:latest
andcontroller:latest
Can i know what is the fix or solution here ? i am using 2.6.0 version libraries and i get the same issue
[otel.javaagent 2023-06-23 09:58:28:834 +0000] [OkHttp http://seldon-collector:4317/...] ERROR io.opentelemetry.exporter.internal.grpc.OkHttpGrpcExporter - Failed to export metrics. The request could not be executed. Full error message: seldon-collector: Name or service not known
And instead seldon-mesh mamespace. we have our own name space. I should change the endpoint right as per my new namespace name like below ?
"opentelemetry": map[string]interface{}{
"endpoint": "seldon-collector.<my-own-ns>:4317",
},
The field
opentelemetry.enable
is being ignored in theseldon-core-v2-setup
chart. https://github.com/SeldonIO/helm-charts/blob/master/helm-charts/seldon-core-v2-setup/values.yaml#L74This causes errors at least in the
dataflow-engine
component like: