Jaeger Datasource Plugin
How to install
This plugin requires react and react-dom 18 or 19.
Install peer dependencies:
npm install react@18 react-dom@18 # or react@19 react-dom@19
Install the plugin:
npm install @perses-dev/jaeger-plugin
Compatibility
The plugin reads traces from the Jaeger query API v3 (/api/v3/traces, /api/v3/services and /api/v3/operations).
Jaeger 2.21 removed the older /api/traces, /api/services and /api/operations endpoints, so the plugin no longer
uses them.
It has been tested with Jaeger 2.10 to 2.22. Filtering the search by span kind needs Jaeger 2.20 or later; older
releases ignore that filter.
Jaeger 1.x is not supported, and it reached end of life on December 31, 2025. Jaeger 1.52 and older answer the API v3
with base64-encoded IDs and stream one JSON chunk per trace, which the plugin cannot read, and 1.53 still returns
base64-encoded IDs. Releases 1.54 to 1.76 return the same response as Jaeger 2.x, so searches can work, but they ignore
the tag and span kind filters. Datasources that use the Perses proxy and only allow the former endpoints fall back to
/api/traces, but datasources that use a directUrl never fall back.
If the datasource uses the Perses proxy, its allowed endpoints should include GET /api/v3/traces,
GET /api/v3/services and GET /api/v3/operations. Datasources saved with the previous allowed endpoints
(/api/traces, /api/services, /api/operations) keep working against Jaeger 2.20 and older: when the proxy rejects the
API v3 paths, the plugin falls back to the former API. Against Jaeger 2.21 and later, those datasources must be updated
with the paths above, and the plugin reports it when a request is rejected.
Development
Setup
Install dependencies:
npm install
Get Started
Start the dev server:
npm run dev
Build the plugin for distribution:
npm run build