Trace Application Transaction

Tracing application information

1. Open Super Heroes main UI web then start a random fight.

   

   Application transaction tracing
2. Switch back to OpenShift web console, then open Jaeger web console by click on arrow icon from jaeger entity.

   

   Application transaction tracing
3. Click Log in with OpenShift button.

   

   Application transaction tracing
4. Log in with your username and password.

   

   Application transaction tracing
5. Click Allow selected permissions button.

   

   Application transaction tracing
6. Select following options then click Find Traces button.

   • Service: rest-fights

   • Operation: /api/fights/randomfighters

   

   Application transaction tracing
7. Click on one of the Traces result.

   

   Application transaction tracing
8. You'll see the trace from the Fight (rest-fights) service all the way down to the Villain (rest-villains) service.

   

   Application transaction tracing
9. Expand the Tags section to see details of each span e.g. data, configurations, context information etc.

   

   Application transaction tracing

Trace a fight transaction

1. Select rest-fights service and the /api/fights operation. Click Find Traces then click on the first trace from result.

   

   Application transaction tracing
2. Click on rest-fights FightService.performFight then click Tags to see API call input.

   

   Application transaction tracing
3. Note the name of fighters in the input request.

   

   Application transaction tracing
4. Switch to Super Heros main UI, then compare the fighter names you see in Jaeger to the fighter names of the last fight in Super Heros main UI.

   

   Application transaction tracing
5. Go back to Jarger web console and expore more spans. You'll see the trace to Kafka topic as well.

   

   Application transaction tracing

What have you learnt?

How to use Jaeger to trace application transaction.