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 | Indicates the operation performed which will The type of transaction. Type can be one of : Fetching Interaction Statisticsthe 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 ContactWorld. |
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. Delimited Log records are delimited by new lines; per entry columns are delimited by pipe ("|") characters, see below. Logs is contains the first 131072 bytes of log data; Logs2 is where more than 131072 bytes of log data is available, Logs2 contains the last 131072 bytes where there is more log data than fits into the first Log field alone. Each row of information in the Logs fieldcontains 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 statistics log for this channel |
Failed | Indicates transactions that encountered a fatal error, such as misconfiguration and that in the Logs/Logs2 data there will be more information on the ERROR . 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 so. For example, for example you can see you could report on how many transactions ran per for each channel per each hour over for the last few hours. |
Interval | Number of seconds spanned by the transaction. For example, an interval of 300 indicates that the transaction spanned 300s 300 seconds or 5 minutes worth of data. Only values equating to whole numbers of minutes are currently supported. |
Window End | The time up to which data was fetched. If you subtract the Interval, you can derive the time span of the interaction starts or agent event starts which would have been fetchedretrieved. |
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 transaction run time in milliseconds; not the same as the CPU time which will be far less. The . Includes the amount of time it took from Transaction start to completing 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). |
...