Interaction Service log statements
Agent Priority logs are located by default at C:\Program Files (x86)\Virtual Hold Technology\VHLogs\Logs. The Agent Priority logs folder contains the log statements for the application.
Interaction Service log statements
The Interaction Service log statements log the message exchanges between RabbitMQ and Interaction Service.
- Low level log statements
| Event | Log statement |
|---|---|
| Interaction Service is starting. | Starting |
| Interaction Service started. | Started |
| Interaction Service is stopping. | Stopping |
| Interaction Service has stopped. | Stopped |
| An error occurred during Interaction Service startup. | Unable to start. |
| An error occurred during Interaction Service startup, and startup is retrying. | Retrying startup. |
| The routing key is truncated when greater than 255 characters. | Routing key truncated to 255 characters {key} |
- Exception level log statements
| Event | Log statement |
|---|---|
| Messages are being received faster than they can be processed. | [name] message queue has been full for [time] seconds |
| Interaction Service cannot connect to RabbitMQ to receive or send events. | Failing to connect to RabbitMQ |
| Could not parse the call data from the Interaction Event JSON file. | Failed to parse call data from interaction event file |
| Could not read or access the Interaction Event JSON file | Exception loading InteractionEvent file |
| Interaction Event file contained an invalid JSON file. | Error reading interaction event file [fileName], this event will be disabled. |
| Template string in Interaction Event JSON was invalid | Exception trying to parse data format |
| Configuration file could not be found | Unable to find config file |
| Configuration file was not accessible | Unable to setup configuration file |
| InteractionEvents directory is not in the InteractionService folder so no events can be loaded | Could not locate InteractionEvents directory |
| An error occurred loading the InteractionEvents files | Error reading InteractionEvents files |
| Service has an error on startup | Unable to start service |
| Couldn't connect to receive events, or lost connection | Error consuming queue |
| Couldn't connect to receive events, or lost connection | Unable to connect to incoming queue |
| Either or both event publishing exchanges are not available | Publish Service is not connected. |
- Full level log statements
| Event | Log statement |
|---|---|
| InteractionEvent JSON file configuration has been loaded. | Successfully loaded InteractionEvent from [file name] |
- Warning level log statements
| Event | Log statement |
|---|---|
| InteractionEvent JSON file configuration had an issue and has not been loaded. | Could not load InteractionEvent from [file name] |
| We have received events faster than we can process them, but not (yet) for a sustained period. | Message queue full |
| Connection to RabbitMQ failed for the topic output exchange | Unable to connect to topic exchange |
| Connection to RabbitMQ failed for the direct output exchange | Unable to connect to direct exchange |
| We were unable to publish event message | Failed to publish message [body] to routing key [routingKey] |
| Interaction Event JSON validation failure | Field: [error.Field], message: [error.Message] |
- Medium level log statements
| Event | Log statement |
|---|---|
| All data for the interaction has been removed when the call is deleted from QM. | Expired call [callId] removed from data store |
| We have loaded details for the interaction ready to send an event | Got interaction with name [name] and event name [event name] |
- Super level log statements
| Event | Log level |
|---|---|
| Preparing to send an event message. | About to use key [routingKey] to publish message [body] |
- Debug level log statements
| Event | Log level |
|---|---|
| We successfully parsed a template string from an Interaction Event JSON file. | Successfully compiled call data for [value] |
