Log Viewer
Monitor ServiceNow system logs in real-time from a floating Sidekick window.
Last updated: February 19, 2026
Last updated: February 19, 2026
The Log Viewer shows system log entries in real-time, right next to your ServiceNow instance. No need to open syslog_list.do in another tab — logs stream live into the Sidekick window as they happen.
Use the slash command /sklog or open Sidekick and select the Log Viewer tab.
Once open, the Log Viewer polls your instance for new log entries and displays them in a scrollable, filterable list. Each entry shows:
New entries appear at the top (newest first) and the list auto-scrolls to show the latest entry unless you've scrolled up to review older logs.
The Log Viewer includes filters to help you focus on relevant entries:
A Range row above the level chips lets you scope how far back the viewer fetches:
The active range applies to the initial load, the Refresh button, the Open in Platform link, and any search you run with the filter box. Live polling for new entries is unaffected — new logs always stream in regardless of range. Your choice persists across opens; if a search comes back empty, the empty state offers a one-click Search all logs link to widen the range without re-typing the filter.
A row of toggle pills under the toolbar — fatal · error · warning · info · debug · trace — lets you scope the view to one or more levels at any time. Inactive levels are dimmed; active levels are full colour:
error pill on any log entry adds error to the filter, just like clicking it in the toggle row above.The level filter is applied server-side (levelIN…), so refreshes, the 3-second polling loop and the Open in Platform button all carry it through — useful for filtering to a rare level like fatal that wouldn't be in the in-memory buffer of recent entries.
Use the search field to filter log entries containing specific text in either the message or the source. Useful for finding logs related to a particular record, script, or error message. The match is highlighted in the result list.
You can also click any sys_id in a log message to search for that record. When a log entry contains both a table name and a sys_id, it becomes a direct link to that record.
/skloggs.info() or gs.debug() statements to your script/sklogerror (and optionally fatal) in the level toggle row under the toolbar