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.

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.
• NOTICE: Highlights informational messages that may require attention.
• 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 a PANIC.

Investigating coordinator logs

Query internal database records for recent coordinator log events using the Coordinator Logs (7 days) tab. Use the Search Logs section to filter by log table, severity, database, or free-text search, then select Search to run the query.

• Use the Errors, Warnings, and Fatal/Panic count cards at the top of the page as quick filters. Clicking a card automatically applies that severity filter to the Log Entries table.
• Narrow results to critical event levels like ERROR, FATAL, or PANIC to bypass routine system noise. Use these logs to identify commands that failed or sessions that were terminated prematurely.
• Filter by database using the database field in the Search Logs section to determine if a performance issue is widespread or isolated to a specific database.
• Select Details to view the full technical trace for a specific entry.
• Select Export CSV to download your filtered results for deeper investigation or bulk analysis in external tools.

Investigating historical logs

Search across coordinator and segment logs aggregated by Loki using the Historical Logs (Coordinator & Segments) tab. Results include Time, Severity, Job, Database, Segment, and Message columns, making it possible to correlate events across the full cluster.