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
I really appreciate this example, but open-telemetry-collector seems to move fast and the examples I have found online (including this one) get outdated rather quickly.
I followed the instructions in this project, and had to make several changes, not sure if they were the right thing to do, but eventually I hit a dead end.
After service.env was generated, I had to manually edit ISSUER_URL and use the real IP of my machine, not localhost, as Keycloak did not seem accessible in the gateway image at localhost.
In docker-compose.yaml, I changed image from opentelemetry-collector to opentelemetry-collector-contrib, otherwise, it failed to start, as unable to understand the extensions in the yaml config files.
In docker-compose.yaml, I removed --log-level=debug as this option is no longer supported.
In config-gateway.yaml, I changed tls_settings to tls
In config-agent.yaml, I commented out ca_file. This feels like the wrong thing to do, but agent would not start with it there.
After making all these changes, the containers started, but gateway would not connect to agent with this error, at which point I became stuck:
agent_1 | 2022-02-04T00:12:50.034Z warn zapgrpc/zapgrpc.go:191 [core] grpc: addrConn.createTransport failed to connect to {gateway:4320 gateway:4320 <nil> <nil> 0 <nil>}. Err: connection error: desc = "transport: authentication handshake failed: x509: certificate signed by unknown authority" {"grpc_log": true}
gateway_1 | 2022-02-04T00:12:50.034Z warn zapgrpc/zapgrpc.go:191 [core] grpc: Server.Serve failed to create ServerTransport: connection error: desc = "ServerHandshake(\"172.23.0.5:37352\") failed: remote error: tls: bad certificate" {"grpc_log": true}
Again, thanks for the project and instructions. I totally understand if this is not something you have time to look into, but thought you might like to know about the issues I ran into using the latest open telemetry images.
The text was updated successfully, but these errors were encountered:
Thanks for the issue note @douglasbgray. That was my experience (outdated example docs) when I compiled this example as well 😁. I'd love to post an updated guide if I'm able to find some time in the next few weeks to investigate. Will let you know if I find anything interesting.
I really appreciate this example, but open-telemetry-collector seems to move fast and the examples I have found online (including this one) get outdated rather quickly.
I followed the instructions in this project, and had to make several changes, not sure if they were the right thing to do, but eventually I hit a dead end.
opentelemetry-collector
toopentelemetry-collector-contrib
, otherwise, it failed to start, as unable to understand the extensions in the yaml config files.--log-level=debug
as this option is no longer supported.tls_settings
totls
ca_file
. This feels like the wrong thing to do, but agent would not start with it there.After making all these changes, the containers started, but gateway would not connect to agent with this error, at which point I became stuck:
Again, thanks for the project and instructions. I totally understand if this is not something you have time to look into, but thought you might like to know about the issues I ran into using the latest open telemetry images.
The text was updated successfully, but these errors were encountered: