Transaction logs
The following table provides information about each of the fields within the transaction log record:
Field | Description |
|---|---|
Name | A system generated sequence. The name is always unique in the Salesforce org and is prefixed by TX. |
Time | A time stamp of when the transaction started. |
Type | The type of transaction. Type can be one of the following values:
|
Channel | The name of the channel used in the transaction. |
Summaries Saved | The total number of agent or call summary records created or updated from data retrieved by the transaction. |
Bytes Read | The total number of bytes in data retrieved for all invocations of the Stats API in this transaction. |
Rows Processed | The total number of events—agent states, outbound calls or inbound calls—retrieved from Vonage Contact Center. |
Heap | The peak heap size recorded during this transaction. |
Limits | Diagnostic data on the percentage consumption of per-transaction Salesforce Governor Limits |
Size | Size of the Log text |
Logs and Logs2 | The log text for the transaction. Log records are delimited by new lines; entry columns are delimited by pipe (|) characters. Logs contains the first 131072 bytes of log data; where more than 131072 bytes of log data is available, Logs2 contains the last 131072 bytes. Each row of information in the Logs field contains a new log entry. A log record consists of the following information:
A pipe character (|) separates the items in the log records. For example, the following log record was created at 49 ms after the start of the transaction; the log record represents an error that occurred in the Constants class; the log message is "Set ORG_TIMEZONE_KEY failed; defaulted to: Europe/London":
Some log records appear only the first time the event occurs to save memory but support debugging. For example, the following log record contains details of an event that occurred multiple times. "<<First Time>>" indicates that the event occurred subsequently:
|
Is Last Inbound | Indicates that this was the last inbound call log for this channel. The channel uses the value in the Window End field as the starting point when it next runs. For more information, see Window End later in this table. |
Failed | Indicates that the transaction encountered a fatal error, such as misconfiguration. Logs or Logs2 will include more information about the error encountered. |
Warnings | Indicates that the transaction encountered a non-fatal error, such as misconfiguration. Logs or Logs2 will include more information about the error encountered. |
Timezone | The time zone that the transaction ran in and in which a subsequent one will run |
Transaction Group | A concatenation of transaction type, channel and time. Transaction Group is useful in grouping transactions when reporting. For example, you could report on how many transactions ran for each channel each hour for the last few hours. |
Interval | Number of seconds spanned by the transaction. For example, an interval of 300 indicates that the transaction spanned 300 seconds or 5 minutes worth of data. Only values equating to whole numbers of minutes are currently supported for the version 0 of the Stats APIs. When using version 3 or above of the Stats API, Advanced Reporting and Statistics manages the interval itself. Intervals will range from 60-86400 as Advanced Reporting and Statistics optimizes data requests to make fewer API calls. |
Window End | The time up to which data was retrieved. |
Channel Checked | Indicator that this is a transaction that the system resumed from after sleeping or another interruption, such as a Salesforce maintenance window. |
Duration | Elapsed transaction run time in milliseconds. Includes the amount of time from the transaction starting to the transaction having saved all the new or updated data in Salesforce. Duration is not the same as the CPU time which will be far less. |
ReQueued Job | ID of any job requeued if this transaction was a resume point (see Channel Checked above). |
Page | A page count populated when using version 3 or above of the Stats API with Advanced Reporting and Statistics. Page records which page of statistics data the channel fetched where one or more pages is available for the requested time range. This field is not populated when using the version 0 Stats APIs. |
Pages Available | The number of pages of stats available for the type of data requested by the transaction over the time range requested when using version 3 or above of the Stats API with Advanced Reporting and Statistics. This field is not populated when using the version 0 Stats APIs. Advanced Reporting and Statistics uses a default page size, but you can override this using a flag if you require very high interaction complexity. |
Cycle Complete | A check box which denotes that this transaction fetched the last page of data predicted by the number of pages available according to the API. |
For general assistance, please contact Customer Support.
For help using this documentation, please send an email to docs_feedback@vonage.com. We're happy to hear from you. Your contribution helps everyone at Vonage! Please include the name of the page in your email.