Auditing system logs
Correlate system-level events with specific query failures by consolidating database metrics with external log aggregation. Use the Logs panel on the left sidebar to identify the root cause of execution errors and monitor real-time cluster telemetry.
Loki integration required
You must configure a Loki URL in your system environment to enable infrastructure-wide log searching. See Configuring WEM for details.
Understanding log levels
WarehousePG Enterprise Manager (WEM) displays severity levels generated directly by the underlying WarehousePG (WHPG) engine. These levels categorize every log entry based on its impact on database operations:
DEBUG: Contains granular technical details used primarily for deep-dive troubleshooting and development analysis.INFO: Provides standard informational messages regarding routine system operations.LOG: Reports standard engine-level events and process completions.WARNING: Highlights non-fatal events that can indicate potential configuration issues or approaching resource limits.ERROR: Reports a problem that prevented a specific command or query from completing successfully.FATAL: Indicates an error that caused a specific session to be terminated, though the rest of the database remains operational.PANIC: Indicates a critical error that caused all database sessions to be disconnected; the system will usually attempt a restart after aPANIC.
Investigating historical database errors
Query internal database records for specific historical events, and investigate SQL errors and session-level failures.
- Narrow your search to critical event levels like
ERROR,FATAL, orPANICto bypass routine system noise. Use these logs to identify commands that failed or sessions that were terminated prematurely. - Filter results by user, database, or session ID to determine if a performance issue is widespread or isolated to a single application service or developer account.
- Select the Details button to view the full technical trace. Use the timestamp, job, and the specific source code file/line reference to pinpoint exactly where a query failed.
- Select the Export CSV button to download your filtered results. This file is the primary resource for deeper investigation by support teams or for performing bulk analysis in external tools.
Could this page be better? Report a problem or suggest an addition!