Visualization in Jaeger UI #

Note

VictoriaTraces is currently under active development and not ready for production use. It is built on top of VictoriaLogs and therefore shares some flags and APIs. These will be fully separated once VictoriaTraces reaches a stable release. Until then, features may change or break without notice.

Jaeger UI is the official frontend that ships with Jaeger. It queries Jaeger Query Service JSON APIs and visualizes the response trace data.

Deploy Jaeger UI #

You can get Jaeger UI from release page .

As it provides only assets and source code, an HTTP server is needed for serving requests.

Nginx Example #

Here’s an example where we use Nginx to:

  • Serve static content of Jaeger UI.
  • Forward query requests to VictoriaTraces.

Assume you already have:

  1. VictoriaTraces running locally and listening on port :10428.
  2. Jaeger UI assets (index.html and /static) located under /path/to/jaeger-ui/build/.
  3. Nginx Installed.

Create the following config file jaeger.conf and place it to the Nginx config folder:

      server {
    listen       8080;
    listen  [::]:8080;
    server_name  localhost;

    location / {
        root   /path/to/jaeger-ui/build; # change this path to your asserts location.
        try_files $uri $uri/ /index.html;
    }

    location /api {
        proxy_pass http://127.0.0.1:10428/select/jaeger/api; # change this address to VictoriaTraces' address.
    }
}

Here are some common paths of Nginx config folder:

      # Ubuntu & Install with apt
cd /etc/nginx/sites-available/

# MacOS & Install with homebrew
cd /opt/homebrew/etc/nginx/servers/

After reloading Nginx, you should be able to visit Jaeger UI on: http://127.0.0.1:8080/ .

Previous Visualization in Grafana Next