Column | Description |
apiId | The unique identifier for the API. Example: c0f84954-9732-11e5-b9f4-f159eafe47b1 |
apiName | Name of the API in which the event occurred. Example: SampleAPI |
apiVersion | The system-assigned version identifier for the API. Example: 1.0 |
applicationId | The unique identifier for the application associated with the API invocation. Example: c0f84954-9732-11e5-b9f4-f159eafe47b2 |
applicationName | Name of the application associated with the API invocation. An application name is populated as unknown when API Gateway is unable to identify the application using a security policy that is configured for the API. Example: SampleApplication |
cachedResponse | Indicates whether the response is sent to the client from the cached data present in API Gateway through the Service result caching policy or the response is received from Native service and sent to client. Possible values are: Cached, Not-Cached |
callbackRequest | Indicates whether the event is generated for a callback request. Possible values are:  true. This denotes that the event is generated for a callback request.false. This denotes that the event is generated for a normal response. |
correlationID | The unique identifier that is automatically generated for every request coming to API Gateway and can be used to query the log. Example: MED38e9cfa4-2348-408b-9462-124b2181c1a6:656 |
creationDate | Date and time when the event was generated in API Gateway. Example: 1501671101509 |
customFields | The custom fields an API Provider can provide to log a new field and value for a transaction event. Example: {"customfield":"customvalue"} |
errorOrigin | The origin of error. Example: Nativeservice |
eventType | The type of event that occurred. Example: Transactional |
httpMethod | The HTTP method used to invoke the API. Example: GET |
messagePayload | This is applicable only for WebSocket APIs. The message payload for a particular API invocation. Example: Sample WebSocket message |
messageType | This is applicable only for WebSocket APIs. This indicates the type of a WebSocket message. Possible values are: binary, text |
operationName | Name of the API operation that is invoked. Example: Using a Calculator API, you can perform various operations such as addition, subtraction, multiplication, and division. When an addition operation is invoked in API Gateway, then the operation field name is populated as addInts. |
origin | This is applicable only for WebSocket APIs. The origin of the request. Possible values are: client, server |
pacakgeId | The unique identifier for the API package. Example: c0f84954-9732-11e5-b9f4-f159eafe47b2 |
packageName | Name of the API package. Example: Travel Package |
planId | The unique identifier for the API plan. Example: d0f84954-9732-11e5-b9f4-f159eafe47b2 |
planName | Name of the API plan. Example: Gold Plan |
providerTime | Time in milliseconds required for API Gateway to invoke a native provider and receive a response. This time includes the overhead incurred by API Gateway. Overhead includes the time it takes for a provider to process a request and return a response, plus any network latency to or from the provider. Subtracting total time from provider time must give a rough indicator of the API Gateway overhead. Example: 20 |
queryParameters | This is applicable only for REST APIs. Query parameters present in the incoming REST request. Example: {"status":"available"} |
request | The API request payload data. Example: <RequestPayload> |
requestHeaders | Request header in the incoming request from the client. Example: {"Cache-Control":"max-age=0","Accept":"text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8","Upgrade-Insecure-Requests":"1","Connection":"keep-alive","User-Agent":"Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36","Host":"mcdaso02:5555","Accept-Encoding":"gzip, deflate","Accept-Language":"en-US,en;q=0.9,ta;q=0.8","Content-Type":"application/x-www-form-urlencoded"} |
response | The API request response data. Example: <ResponsePayload> |
responseCode | The HTTP response status code that indicates success or failure of the requested operation. Example: 200 |
responseHeaders | Response header in the outgoing response. Example: {"Server":"Jetty(9.2.9.v20150224)","Access-Control-Allow-Origin":"*","Access-Control-Allow-Methods":"GET, POST, DELETE, PUT","Connection":"close","Date":"Fri, 30 Mar 2018 08:25:45 GMT","Access-Control-Allow-Headers":"Content-Type, api_key, Authorization","Content-Type":"application/xml"} |
status | Status of the API request. Possible values are: SUCCESS, FAILURE |
totalDataSize | The total combined size of request and response payloads in bytes. Example: 100 |
totalTime | Time in milliseconds required to invoke the API provider. This time includes the overhead incurred by API Gateway. Overhead includes security overhead for encryption, decryption, and load-balance retries. Example: 120 |