Status Log Limit¶
The Status Log Limit controls how many log messages QIE loads into a log panel at once. It is a display limit, not a retention limit. It changes how much of the log you see in the console, never how much of it QIE keeps.
Find it under System Administration -> System Configuration, in the Advanced Settings section (click Show Advanced Settings).
Max Log Messages¶
Max Log Messages: The maximum number of log messages loaded into a single log panel. The default is 200.
The limit applies to the three places the console renders a log:
- The log history panel on the Global System Status page
- The Channel Status tab
- The Test Log dialog produced by Testing and Debugging
Each of those panels is capped independently, and the cap is applied per request. Raising it to 1,000 means every refresh of every open log panel retrieves and renders up to 1,000 rows, for every signed-in user. The cost of a large value is paid on the browser and on the database, repeatedly, rather than once.
Tip
Raise this temporarily when you are chasing a burst of errors and the newest 200 entries do not reach far enough back, then put it back. If you routinely need thousands of rows, export the log instead. See Exporting Log Messages, which is built for volume and does not hold the results in the browser.
What it does not affect¶
The limit is frequently mistaken for a retention setting. It is not related to any of these:
- How long log messages are kept. That is the system log retention setting in the Message Retention Policy.
- What gets logged in the first place. That is the channel's log level, which decides whether a
debugorinfomessage is ever generated. Changing the Status Log Limit cannot reveal a message that was never written. - Exported logs. An export is not capped by this value.
When a change takes effect¶
The limit is handed to the console when a user signs in. Saving a new value applies it immediately for the administrator who saved it; anyone already signed in keeps the previous limit until they sign in again. No restart is required.
Changes to this setting are recorded in the configuration Revision History.