Transaction Traces are not displayed at the Called Backends node in the Metric Tree
search cancel

Transaction Traces are not displayed at the Called Backends node in the Metric Tree

book

Article ID: 280609

calendar_today

Updated On:

Products

CA Application Performance Management (APM / Wily / Introscope)

Issue/Introduction

Transaction Traces are not displayed at the Called Backends node in the Metric Tree.

The traces are displayed above Called Backends and they are also displayed in the Backends node. 

Resolution

The trace query in Metric View actually uses the node path as a filter parameter to retrieve traces matching the filter.

i.e. 

When you click on your test Agent "testhost1|TomcatProcess|TomcatAgent" node "Frontends|Apps|TestApp1|URLs|/examples" node, from the browser Developer tool, you will see the /trace/summary request has a parameter pathFilter like this:

{
    "pathFilter": {
        "agent": "testhost1|TomcatProcess|TomcatAgent",
        "path": "Frontends|Apps|TestApp1|URLs|/examples"
    }
}

 

This query will return all traces matching this particular agent and path.

 

In case of "Called Backends" node, there is no trace matching path "Frontends|Apps|TestApp1|URLs|/examples|Called Backends", as this is not a real front URL path, but a concatenated path to show the correlation between Frontend and Backend.