Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The filters screen the data that is passed at the beginning of the API execution except OAuth, Latency, Response codes and Error messages which are collected at the end of the transaction.
If the API did not finish, the OAuth, Latency, Response codes and Error message will not be collected and will not be displayed in the grid.
See Available Filters for a complete list of filters for the API Connect view.

Most common filters are visible by default. press "Image Added" link to view additional filters.

Transactions Grid

The following information is available for each transaction:

...

API Name

The API Name



Time

The time this transaction was logged

Device

The device this transaction ran on.
Clicking the device name link applies a device filter to the results, showing only transactions that ran on this device.

Catalog

Name

/Space

The API Catalog Name

and API Space Name separated by a slash character (i.e. my-catalog/my-space).

Product
Plan
APIThe API
Space NameOperation IDThe invoked operation within the APIClient IDThe ID of the client that invoked the APIOAuth ScopeOAuth Scope
Name and API Version seperated by a dash character (i.e. api-name - 1.0.0).
App NameConsumers application name.
URIThe last part of URL which identifies the API invoked by the client. 

Status

The status of the transaction. This may be either OK, ERROR

Trans. ID

This is the monitored device's transaction ID.
Clicking the Transaction id link loads the Single Transaction details view

Client IP

The client originating the transaction. This can sometimes be the IP of the load balancer.

Gl. Trans. IDThe global transaction ID

Elapsed (ms)

The elapsed time of the transaction in milliseconds

Payload

When WS-M recording is on, this column will contain the payload of the transaction.