VDM Logs Overview

Trouble Viewing Images? Right-click on any image and select "Open in new tab" to view a larger version. You can also zoom in using Ctrl + Mouse Wheel for easier readability.

Summary

VDM Logs provide a centralized location for monitoring system activity. Users have access to Application Logs, WebReports Logs, and Service Logs. Within the logs, you can configure settings such as the number of days to display, log time, log type, and more. Logs are presented in a Data Grid that supports functionality similar to the Detail Grid, including grouping and filtering.

Log Types

• Success: Connection-related events (e.g., establishing connections to a database) 
• Info: General informational messages 
• Warning: Non-critical issues encountered while opening or running a view 
• Error: Critical issues that impact execution or results

Tip: Use the Date & Time (calendar) filter to narrow down logs to a specific timeframe. This makes it much easier to identify when an issue occurred or to focus on events during a particular window without sorting through all entries.

Application Logs

• Log Time – The date and time the log entry was created 
• Log Type – The type of log (Success, Info, Warning, Error) 
• Version – The VDM version running at the time the log was generated 
• Process – The process ID (PID) used to identify tasks in Task Manager 
• Sessions – The number of active sessions at the time the log was created 
• Mem Usage – The amount of memory being used by VDM 
• Available Memory – The amount of memory available to VDM 
• User – The user who initiated the VDM session 
• Workstation – The machine where VDM is installed and running 
• ID – Internal error codes used to identify error locations within VDM 
• Type – The process driving VDM (e.g., Service, Master Job, Separate Session) 
• Connection – The database connection in use 
• Appointment / Master Job – The associated appointment or master job 
• Appointment Window – The scheduled time window for the appointment 
• Job – The job that was executed 
• View – The file path of the view used 
• Execution – The execution job that was run 
• Message – Details about the log entry and system state (e.g., error codes, scheduler messages)

Service Logs

• Log Time – The date and time the log entry was created 
• Log Type – The type of log (Success, Info, Warning, Error) 
• Version – The VDM version running at the time the log was generated 
• Process – The process ID (PID) used to identify tasks in Task Manager 
• Sessions – The number of active sessions at the time the log was created 
• Mem Usage – The amount of memory being used by VDM 
• Available Memory – The amount of memory available to VDM
• Total Memory – The total amount of memory available on the system
• User – The user who initiated the VDM session 
• Workstation – The machine where VDM is installed and running 
• ID – Internal error codes used to identify error locations within VDM 
• Type – The process driving VDM (e.g., Service, Master Job, Separate Session) 
• Connection – The database connection in use 
• Appointment / Master Job – The associated appointment or master job 
• Appointment Window – The scheduled time window for the appointment 
• Job – The job that was executed 
• View – The file path of the view used 
• Execution – The execution job that was run 
• Message – Details about the log entry and system state (e.g., error codes, scheduler messages)

Ask Bridgit AI

Ask Bridgit AI lets you quickly troubleshoot logs in VDM by selecting a log entry (from Application or Service Logs), right-clicking the message in the Messages column, and choosing “Ask Bridgit AI.” This opens a chat where the AI analyzes the message and provides a clear explanation, likely causes, and suggested fixes, helping you resolve issues faster without manually digging through documentation.

If you would like to learn more about how to use Ask Bridgit AI, please refer to the article Bridgit AI Overview and Usage Guide.