## Tracing messages through routes

Debugging a route usually involves solving one of two problems:

- a message was improperly transformed

- a message failed to reach its destination endpoint

Tracing one or more test messages through the route is easiest way to solve these problems.

The route tracing feature of the developer tools enable you to monitor the path a message takes through a route and see how the message is transformed as it passes from processor to processor.

Diagram View displays a graphical representation of the route, which enables you to see the path a message takes through it. For each processor in a route, it also displays the average processing time, in milliseconds, for all messages processed since route start-up and the number of messages processed since route start-up.

Messages View displays the messages processed by a JMS destination or route endpoint selected in the Fuse JMX Navigator tree. Selecting an individual message in Messages View, displays the full details and content of the message in the Properties view.

Tracing messages through a route involves the following steps:

1. Creating test messages for route tracing

2. Activating route tracing

3. Tracing messages through a route

4. Deactivating route tracing