Hi, I have configured tyk-pro-docker-demo to use Jaeger but seems like no service is created in jaeger UI.
"tracing": {
"enabled": true,
"name": "jaeger",
"options": {
"baggage_restrictions": null,
"disabled": false,
"headers": null,
"reporter": {
"BufferFlushInterval": 0,
"collectorEndpoint": "",
"localAgentHostPort": "jaeger:6831",
"logSpans": true,
"password": "",
"queueSize": 0,
"user": ""
},
"rpc_metrics": false,
"sampler": {
"maxOperations": 0,
"param": 1,
"samplingRefreshInterval": 0,
"samplingServerURL": "",
"type": "const"
},
"serviceName": "tyk-gateway",
"tags": null,
"throttler": null
}
}
leon
January 23, 2020, 10:06am
2
Try using v2.9.3-rc3 docker tag. We have some related bugfixes in the upcoming release.
gathuku
January 23, 2020, 10:15am
3
leon:
v2.9.3-rc3
Getting this error on the tag. Gateway exit with code 127
tyk-gateway_1 | ./entrypoint.sh: line 27: ./tyk: No such file or directory
gathuku
January 23, 2020, 12:15pm
4
My docker-compose service
jaeger:
image: jaegertracing/all-in-one:1.16
environment:
- COLLECTOR_ZIPKIN_HTTP_PORT=9411
ports:
- "5775:5775/udp"
- "6831:6831/udp"
- "6832:6832/udp"
- "5778:5778"
- "16686:16686"
- "14268:14268"
- "9411:9411"
networks:
- tyk
did you find the solution? if yes please share how you solved it
Olu
February 8, 2022, 10:08am
6
You docker compose looks fine. So the issue may appear to be with your config file. Can you try using the config file below with zipkin
"tracing": {
"enabled": true,
"name": "zipkin",
"options": {
"baggage_restrictions": null,
"disabled": false,
"headers": null,
"reporter": {
"collectorEndpoint": "",
"localAgentHostPort": "",
"url": "http://host.docker.internal:9411/api/v2/spans",
"logSpans": true,
"password": "",
"queueSize": 0,
"user": ""
},
"rpc_metrics": false,
"sampler": {
"maxOperations": 0,
"param": 1,
"samplingServerURL": "",
"type": "const"
},
"serviceName": "tyk-gateway",
"tags": null,
"throttler": null
}
},
Olu
February 9, 2022, 8:43pm
7
@gathuku Did you manage to resolve the issue? If not then could you take a look at vivek_maurya’s answer . Maybe your version is the issue. I discovered there was some issue with Jaegers and some version 3.x