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
Right now it seems that the tracing integration is broken.
β Expectations
we can deploy jaeger on minikube (all in one configuration)
we can tell trustify v2 to send tracing information to this instance
π₯ Problem
I see the following errors in the pod logs:
OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: tcp connect error: Connection refused (os error 111)
I don't see tracing information in the jaeger instance.
β»οΈ Reproduce
Clone helm chart repository
git clone git@github.com:trustification/trustify-helm-charts.git
cd trustify-helm-charts
progress π
the issue changed now to received message with invalid compression flag: 60 (valid flags are 0 and 1) trustification/trustify-helm-charts#11
Right now it seems that the tracing integration is broken.
β Expectations
π₯ Problem
I see the following errors in the pod logs:
I don't see tracing information in the jaeger instance.
β»οΈ Reproduce
Clone helm chart repository
git clone git@github.com:trustification/trustify-helm-charts.git cd trustify-helm-charts
Run minikube
Set env
Deploy infrastructure chart with jaeger enabled
Deploy application with tracing enabled
β¬οΈ Steps
The text was updated successfully, but these errors were encountered: