Retrieving recorded trace data
The API contains the following topics:
Use the following URL to register the API:
Replace the following entries, as required:
|Protocol used to send the request|
|Host name or IP address of the App Visibility portal|
Communication port number of the App Visibility portal.
The default port number is 8100.
Identifying string (automatically assigned) of the transaction
Sample JSON response
The response show details about the transaction fragments, such as the information you can see in the Trace Details view.
If true, all App Visibility collectors are online; if false, some data might be missing
If true, some results might be missing because the portal cannot reach one or more collectors; if false, all results are recorded
Class of request fragment data
Fragments are listed with most recent request first.
Identifying string (automatically assigned) of the application server
|duration||Duration of the request|
|startTime||Epoch time, in milliseconds, that the request began|
|topLevel||Indication of the first fragment in the transaction (true) or not (false)|
|errorViolation||Indication of error on the request (true) or not (false)|
|requestID||Identifying string (automatically assigned) of the request|
|latencyViolation||Indication that the duration exceeds thresholds (true) or not (false)|
|traceId||Identifying string (automatically assigned) of the trace|
|entryPoint||Entry point name|
|exitStatus||If the fragment has an error, the HTTP status code|
|euemTag||Object for internal use|
Represents the fragment level regarding the flow of the transaction: