Event Log Reference
The Event Log on each adapter records significant operational events: connection state changes, actions taken, and errors. This page explains what you'll see and what to do about it.
How the Event Log is Organized
Each entry in the event log has three fields:
| Field | What it tells you |
|---|---|
| Level | How serious it is: info, warning, or error |
| Category | Which part of the system it came from: connection, action, or system |
| Description | A plain-English explanation of what happened |
Entries may also include a details section with additional context (for example, the session ID or destination involved).
Connection Events
These events track the lifecycle of your connections. The specific event names depend on which plugin is providing the connection.
| Description | Level | What it means |
|---|---|---|
| Connection Enabled | info | The connector has started and is attempting to establish a session |
| Connection Stopped | info | The connector has been stopped, either manually or by the platform |
| Session Established | info | The session is fully established and messages can now flow |
| Session Closed | info | The session has been closed cleanly |
| Connection Active | info | The connection is established and active |
If you see a connection enabled event but the session never establishes, the adapter is trying to connect but something is preventing the session from completing. Check:
- Is the host address and port correct?
- Is the external system's firewall allowing your connection?
- Are the session credentials and identifiers correct?
- Does the connection require encryption? If so, is TLS termination configured at the load balancer by your infrastructure team?
For plugin-specific event names and troubleshooting, see the Official Plugins documentation.
Action Events
These events are created when a command is sent to the adapter, for example enabling or disabling it, resetting a session, or updating sequence numbers.
| Description | Level | What it means |
|---|---|---|
| Action received: <action> | info | The platform has received and is processing a command |
| Action <action> completed successfully. | info | The command completed without errors |
| Action <action> failed: <reason> | error | The command failed; the reason is included in the description |
| Action <action> failed with an unexpected internal error. | error | An unexpected error occurred; check Orchestrator logs for more detail |
| Session reset initiated | info | A session reset was triggered from the Portal |
| Sequences updated manually | info | Protocol sequence numbers were manually adjusted |
Common action names you'll see: START, STOP, RESET_SESSION, UPDATE_SEQUENCES.
If you see an action failure, the description will include the reason. Check the details field for more context.
What's NOT in the event log
The event log records operational events (connection state and commands). It does not show individual protocol messages (orders, execution reports, etc.). Those are in the message log, accessible separately from the adapter detail page.
Using the Event Log Effectively
- Filter by level. When something's wrong, set the filter to
errorto cut through the noise. - Filter by category. For connection problems, filter to
connection; for action failures, filter toaction. - Check timestamps. If an adapter went into error state at a specific time, look for events in that window.
- Details field. Expand any event to see additional context like session IDs or configuration values.