Skip to content

Latest commit

 

History

History
26 lines (15 loc) · 1.42 KB

README.md

File metadata and controls

26 lines (15 loc) · 1.42 KB
Raw

OpenTelemetry with Jaeger

Discover the distributed traces generated by Tyk Gateway through Jaeger.

Jaeger is configured to use in-memory storage, implying that data won't persist once the container is restarted or removed.

For further information on Tyk OpenTelemetry support, refer to Tyk's documentation: Tyk OpenTelemetry Overview.

Setup

Run the up.sh script with the otel-jaeger parameter:

./up.sh otel-jaeger

Usage

Open Jaeger in a browser. The Search page displays trace data based on filters:

  • For Service, select tyk-gateway to see traces from the Tyk gateway, or select jaeger-query to see traces from the Jaeger application.
  • The values for Operation change based on the service. Leave it on all to see everything.
  • Lookback filters by time, by limiting displayed data to the selected time period.

Tyk Demo generates trace data during the bootstrap process, so you should see trace entries for the tyk-gateway service without having to send any API requests yourself. If you don't see any data, try increasing the duration of the Lookback filter to a longer period, or generate some fresh trace data by sending a basic request to the Gateway.