Go to XRay Analytics and your page should look like the one below. The Analytics page is pretty powerful and can help you debug and identify issues quickly. Take some time and look around the options available for you to play with.
In the above screenshot you can see that there are certain traces that seem to exhibit higher latency (in the order of 3 seconds or more) compared to others. Let’s see how we can filter those traces easily and find out the root cause.
Before we do that, remember that there are a variety of options available for you to filter traces. We will use the
Response time distribution table to filter the traces because we are investigating a higher latency scenario.
Go ahead and select the area of the graph where you see higher latency as shown below.
In my scenario I see that about 56% of the traces were related to
PetType=bunny querystring and I would like to investigate it. Clicking on one of the links in the list will apply another filter on the already filtered traces and show a screen like the one below.
Scroll down to see that the root cause for latency has been automatically identified by X-Ray Analytics based on the trace data captured.
Using the Analytics console you can also compare two sets of traces with different conditions for root cause analysis purposes.
Now with one set of filters applied, click on the
Compare box at the top right of the Analytics page, which will create trace set B and color the traces in green color. By default, X-Ray will create another set of with the same filter conditions as trace set A.