Question about the Jaeger service address #9818
|
Hi, I'm trying to integrate the Jaeger tracing data into our own frontend application. I can access the Jaeger UI at http://jaeger.fr-bigdata/search from my browser, but I'm unable to resolve the hostname jaeger.fr-bigdata from my local development environment (the DNS lookup fails with "Non-existent domain"). Could you please provide the following information so I can configure a reverse proxy to reach the Jaeger Query API? The internal IP address of the Jaeger service (e.g., 10.x.x.x), or a fully qualified domain name that is resolvable from our internal network. GET /api/services |
Replies: 1 comment 1 reply
|
The Jaeger project can't tell you that, unfortunately. For the ports, the defaults for the query service are:
These can be changed in the deployment, so it's worth confirming with whoever runs it. Since the UI is already reachable at that address, the simplest setup is usually to point your reverse proxy at the same host and port and call the |
The Jaeger project can't tell you that, unfortunately.
jaeger.fr-bigdatais a hostname inside your organization's network, so the IP address and how it's exposed depend on how your platform team deployed Jaeger. They'll have to give you an address you can reach from your machine, or a VPN or DNS setup that resolves that name. The fact that it works in your browser but not in a DNS lookup from your dev environment suggests the browser goes through a proxy, or that your machine uses a different DNS server.For the ports, the defaults for the query service are:
16686: HTTP. This serves both the UI and the JSON API under/api/(for example/api/servicesand/api/traces?service=...), so if th…