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
The WebReports Logs page provides visibility into activity, processing, and errors within the WebReports application. These logs are commonly used for troubleshooting issues, monitoring scheduled processes, and gathering information for support investigations.
The logs are separated into categories to make it easier to locate relevant information.
Accessing the Logs
To access the WebReports logs:
- Open the WebReports application.
- Log in using your assigned credentials.
- Locate and select the Logs option from the navigation bar.
After opening the Logs section, you can choose from the available log categories:
- WebReports
- Executions
- All
- Exceptions
Each category is designed to help users quickly locate specific types of logging information for monitoring and troubleshooting purposes.
Log Categories
The following log categories are available:
| Category | Description |
|---|---|
| WebReports | Displays logs related to general WebReports application activity, system operations, and Bridgit Chat activity. |
| Executions | Displays logs related to scheduled jobs, SQL query execution, processing activity, and execution-related errors. |
| All | Displays all available logs from every category in a single view. |
| Exceptions | Displays application exceptions and critical error messages for troubleshooting failures and unexpected behavior. |
Bridgit Chat Logging
Beginning with WebReports 2026.05.12, Bridgit Chat activity is captured within the standard WebReports logging framework.
This allows administrators to review Bridgit-related events alongside other WebReports activity when monitoring system usage, troubleshooting issues, or validating AI interactions.
Bridgit log entries can be searched, filtered, grouped, and exported using the same tools available for other WebReports log entries.
Note: Available log details may vary depending on the type of Bridgit activity being recorded.
Standard Log Columns
The WebReports, Executions, and All categories all contain the same set of columns.
| Column | Description |
|---|---|
| Log Time | The date and time the log entry was created. |
| Log Type | The type or severity of the log entry (such as Information, Warning, or Error). |
| Log ID | A unique identifier assigned to the log entry. |
| Process | The process or operation associated with the log entry. |
| User | The user account associated with the activity. |
| Connection ID | The identifier for the connection used during the operation. |
| Connection Name | The name of the configured connection used by the process. |
| View | The application view or component associated with the log entry. |
| Message | Detailed information describing the logged event or operation. |
Exception Log Columns
The Exceptions category contains a simplified set of columns focused specifically on application errors and exception details.
| Column | Description |
|---|---|
| Time | The date and time the exception occurred. |
| Exception | The exception or error message generated by the application. |
Searching and Filtering Logs
The log viewer includes several tools to help narrow down and organize log information.
Date and Time Filtering
Logs can be searched using the Date/Time Picker to narrow results to a specific time range. This is useful when troubleshooting issues that occurred during a known timeframe.
Refreshing Log Results
The WebReports Logs page includes a Refresh button in the upper-right corner of the log grid that allows users to manually retrieve the latest available log entries.
Log results do not automatically refresh while you are viewing the page. If new log entries are generated after the page is loaded, select Refresh to update the displayed results.
Note: Refreshing the logs updates the current log view without requiring you to leave or reload the Logs page.
Grid Features
The log grids support:
- Filtering to display only matching results
- Sorting by column values
- Grouping logs by selected columns for easier analysis
These features help isolate relevant log entries more efficiently.
Exporting Logs
Logs can be exported directly to Microsoft Excel for additional analysis or sharing.
Exporting logs is especially useful when:
- Creating a support ticket
- Sharing troubleshooting information
- Reviewing large sets of log data outside the application
Troubleshooting Usage Examples
Users commonly review logs to:
- Identify application errors
- Investigate failed scheduled jobs
- Review SQL execution activity
- Monitor application behavior
- Gather details for support investigations
Because logs are separated into categories, users can more quickly locate the information most relevant to the issue being investigated.
Comments
0 comments
Please sign in to leave a comment.