Transaction Graph

Overview

Get a graph of callers, callees from a transaction:

• All objects of transaction paths are considered, including start points and end points.
• A callee is an object refered in the code statements of the caller.
• The nodes are sorted by object name. The links are sorted by depth, and then the order is undetermined.

URI

GET /rest/applications/{name}/transactions/{id}/graph

Path parameters

name (string)

This parameter identifies the analyzed application. The application name must be properly encoded if it is required. Character back-quote is not allowed.

id (number)

The unique identifier of the transaction from CAST Imaging. This ID is used to retrieve the specific transaction within the application.

Responses

application/json

A list of nodes and a list links. Each node is an object of the transaction call graph. Each link is a transaction call step. Example:

{
  "links": [
    {
      "type": "CALL",
      "depth": 0,
      "origin": {
        "id": "326010",
        "isStartPoint": true
      },
      "target": {
        "id": "323876",
        "isEndPoint": true
      }
    },
    ...
  ],
  "nodes": [
    {
      "id": "326425",
      "name": "http://channels.netscape.com/ns/browsers/download.jsp",
      "type": "JavaScript HttpRequest Get Service",
      "typeId": "CAST_HTML5_GetHttpRequestService"
    },
    ...
  ]
}

JSON representation