Getting the error while exporting traces to jaeger from mule application: io.opentelemetry.exporter.internal.grpc.OkHttpGrpcExporter: Failed to export metrics. The request could not be executed. Full error message: Failed to connect to localhost/127.0.0.1:4317 #12
We are facing the above mentioned error while trying to export the traces on Jaeger using the OTEL Connector in our mule application with following connector configuration.
Trace Collector Endpoint: https://jaeger.com
OLTP Transport Protocol: GRPC
Rest configuration is same as the one we use for dynatrace export.
The strange issue here is that we can see the traces in jaeger once the flow is called but after a minute or so this error starts popping in the logs ( one per minute ).
Even tho the traces are exported to Jaeger host , still this error is populating in the application , post completion of the flow.
Kindly help with this issue.
io.opentelemetry.exporter.internal.grpc.OkHttpGrpcExporter: Failed to export metrics. The request could not be executed. Full error message: Failed to connect to localhost/127.0.0.1:4317
We are facing the above mentioned error while trying to export the traces on Jaeger using the OTEL Connector in our mule application with following connector configuration. Trace Collector Endpoint: https://jaeger.com OLTP Transport Protocol: GRPC Rest configuration is same as the one we use for dynatrace export. The strange issue here is that we can see the traces in jaeger once the flow is called but after a minute or so this error starts popping in the logs ( one per minute ). Even tho the traces are exported to Jaeger host , still this error is populating in the application , post completion of the flow.
Kindly help with this issue. io.opentelemetry.exporter.internal.grpc.OkHttpGrpcExporter: Failed to export metrics. The request could not be executed. Full error message: Failed to connect to localhost/127.0.0.1:4317