Logs
The Logs screen is used to query and view log entries from various sources within IntelliDealer.
This screen provides access to interface interaction logs and Tomcat server logs, allowing users to track system events, errors, and interface communications for troubleshooting and auditing purposes.
The Log Query screen can be found by navigating to Administration > Settings > Logs.
Topics in this section include:
The Logs screen contains two main tabs:
-
Tomcat Events/Exceptions Logs - Displays application server events, exceptions, and error logs generated by the Tomcat server. This tab provides visibility into server-level issues, application errors, and system events that may require attention.
-
Interface Logs - Displays original equipment manufacturer (OEM) interface interactions that occur within IntelliDealer. Users can track data that is either sent or received from OEMs as well as the users who sent them, the status or success of an interaction, and audit additional information if necessary.
Tomcat Events/Exceptions Logs Tab
The Tomcat Events/Exceptions Logs tab displays application server logs generated by the Tomcat server. These logs provide detailed information about server events, application exceptions, errors, and system-level issues that occur during the operation of IntelliDealer.
These fields appear on the Tomcat Events/Exceptions Logs tab:
| Field | Description |
|---|---|
| Start Time | The exact date and time the event or exception occurred on the server. |
| Level | The severity level of the log entry. Common levels include: INFO (informational messages), WARN (warning messages), ERROR (error conditions), and FATAL (severe errors that may cause the application to abort). |
| Path | The path name that executed the code that generated the log entry. This is useful for tracking concurrent operations and debugging multi-threaded issues. |
| Event Message | The descriptive message associated with the log entry. This provides details about what occurred, including error messages, exception details, or informational content. |
| User | The name of the user or component that generated the log entry. This helps identify which part of the application or system generated the event. |
The Tomcat Events/Exceptions Logs tab is primarily used by system administrators and support personnel for troubleshooting server-level issues, application errors, and system performance problems. Reviewing these logs can help identify patterns in errors, diagnose connectivity issues, and monitor system health.
Tomcat Events/Exceptions Logs Details Screen
When you select an entry from the Tomcat Events/Exceptions Logs tab, a details screen opens displaying comprehensive information about the selected log entry. This details screen contains two tabs:
-
Log Master Details - Displays high-level information about the log entry, including identification, timing, and classification details.
-
Log Event Details - Displays detailed information about the specific event, including the full message content, exception details, and stack trace information.
Log Master Details Tab
These fields appear on the Log Master Details tab:
| Field | Description |
|---|---|
| Thread ID | A unique identifier for the log entry. |
| User | The name of the logger or component that generated the log entry. |
| Path | The path name that executed the code that generated the log entry. |
| Start/End Time | The exact date and time the event or exception occurred on the server. |
| Session | The name or identifier of the server instance where the log entry was generated. |
| Application Code | The name of the application or module that generated the log entry. |
Log Event Details Tab
These fields appear on the Log Event Details tab:
| Field | Description |
|---|---|
| Log Event ID | A unique identifier for the log event entry. |
| Level | The severity level of the log entry. Common levels include: INFO (informational messages), WARN (warning messages), ERROR (error conditions), and FATAL (severe errors that may cause the application to abort). |
| Event Message | The descriptive message associated with the log entry. This provides details about what occurred, including error messages, exception details, or informational content. |
| Event Class Name | The name of the Java class where the log event was generated. |
| Method Name | The name of the method where the log event was generated. |
| Line Number | The line number in the source code where the log event was generated. |
Interface Logs Tab
These fields appear on the Logs tab:
| Field | Description |
|---|---|
| Timestamp | The exact date and time the interaction occurred. |
| Interface | The specific IntelliDealer module or service that initiated the call. |
| User Id | The IntelliDealer username of the person who triggered the action. |
| Location | The physical dealership location or branch from which the request originated. |
| IntelliDealer ID | A unique internal identifier for the specific record involved. (eg. a Quote ID, a Part Number, a VIN.) |
| Event Type | Categorizes the nature of the interaction. (eg. Request, Response, Error, Timeout.) |
| OEM | The specific original equipment manufacturer the system communicated with. |
| URL Path |
The specific API endpoint or web address that was called on the OEM's server. |
| HTTP Status |
The standardized numeric status code returned by the OEM's server. Examples of HTTP Status classifications:
|
| Information | A message or the raw data payload of the request/response. A "what happened" field. This might contain the OEM's error message (ie, Invalid Part Number) or a log summary in the event of a successful interaction. |
Revision 2026.01