...
- returnedObjectId - For any method that returns an object with an ID, this column will contain the returned ID. This is the only way to determine the ID of a newly created object from a POST.
- elaseMS - The elapse time of the call in milliseconds.
- timestamp - The exact time the call was made in epoch time (milliseconds since 1/1/1970).
- via - The value of the "via" header (see: http://en.wikipedia.org/wiki/List_of_HTTP_header_fields).
- host - The value of the "host" header (see: http://en.wikipedia.org/wiki/List_of_HTTP_header_fields).
- threadId- The ID of the thread used to process the request.
- userAgent - The value of the "User-Agent" header (see: http://en.wikipedia.org/wiki/List_of_HTTP_header_fields).
- queryString - The value of the request queryString.
- sessionId - For each call a new UUID is generated for the sessionId. The sessionId is also bound to the logging thread context and written in all log entries. This ties access records to log entries.
- xForwardedFor - The value of the "X-Forwarded-For" header (see: http://en.wikipedia.org/wiki/List_of_HTTP_header_fields).
- resquestURL - The URL of the request.
- userID - For calls where the users is authenticated via a sessionToken or an API key, this column will contain the numeric ID of the user.
- origin - The value of the "Origin" header (see: http://en.wikipedia.org/wiki/List_of_HTTP_header_fields).
- date - The year-month-day date string.
- method - The HTTP method: GET, POST, PUT, DELETE
- vmId - When each EC2 instances of a stack starts, a new unique identifier for the "queryString"JVM is issued. This is captured in the access log so calls form a single machine can be grouped together.
- instance - The instance number of the stack.
- stack - The stack identifier. This will always be "prod" for production stacks.
- success - Set to true when a call complete without an exception, otherwise set to false. The stack trace of exceptions can be found by searching the logs for the the sessionId of any failed access records.
Log Files
Log files for all components of a stack are also captured in S3, including data from: repo, portal, and works.