Super Heroes on OpenShift Workshop

Super Heroes on OpenShift Workshop
Application Services Deployment
Application Deployment
- Microservices Deployment
Continuous Deployment (CD)
- GitOps
Application Monitoring
- Application Metrics
  - Configure Service Monitoring
  - Query Application Metrics
- Distributed Tracing
Appendix
- What's Quarkus?
- Useful Resources

Powered by GitBook

On this page

Tracing application information
Trace a fight transaction
What have you learnt?

Application Monitoring

Distributed Tracing

Trace Application Transaction

PreviousConfigure OpenShift Distributed Tracing Data Collection NextWhat's Quarkus?

Last updated 2 years ago

Tracing application information

Open Super Heroes main UI web then start a random fight.
Switch back to OpenShift web console, then open Jaeger web console by click on arrow icon from jaeger entity.
Click Log in with OpenShift button.
Log in with your username and password.
Click Allow selected permissions button.
Select following options then click Find Traces button.
- Service: rest-fights
- Operation: /api/fights/randomfighters
Click on one of the Traces result.
You'll see the trace from the Fight (rest-fights) service all the way down to the Villain (rest-villains) service.
Expand the Tags section to see details of each span e.g. data, configurations, context information etc.

Trace a fight transaction

Select rest-fights service and the /api/fights operation. Click Find Traces then click on the first trace from result.
Click on rest-fights FightService.performFight then click Tags to see API call input.
Note the name of fighters in the input request.
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.
Go back to Jarger web console and expore more spans. You'll see the trace to Kafka topic as well.

What have you learnt?

How to use Jaeger to trace application transaction.