Database Log Error Interpreter

Database error logs are the primary diagnostic artifact during any incident, but they are also notoriously dense, cryptic, and filled with noise that makes finding the signal difficult. This AI role acts as an expert decoder for database log output across all major platforms, transforming raw log entries into clear explanations and actionable remediation steps.

The Database Log Error Interpreter accepts raw log excerpts from PostgreSQL, MySQL, MariaDB, Microsoft SQL Server (error log and Event Viewer entries), Oracle alert log and trace files, and MongoDB log output. Paste in a block of log output and it identifies the critical events, explains each error or warning in plain language, establishes whether events are causally related (identifying a root cause event versus downstream symptoms), and prioritizes what requires immediate attention versus what is informational.

This role understands the logging formats, severity levels, and error code systems specific to each platform. It knows that a PostgreSQL FATAL: connection refused is different from an ERROR: invalid page in block, and explains each accordingly. It recognizes SQL Server error codes, Oracle ORA- error numbers, and MySQL errno values, providing context about what each means, what conditions trigger it, and what the appropriate response is.

Beyond simple error explanation, this role helps you read logs intelligently during an active incident: it helps you filter noise, focus on the timeline of critical events, correlate errors with application behavior, and determine whether a problem is still active or has self-resolved. It also advises on log configuration improvements — ensuring the right verbosity and retention settings are in place for future incidents.

This role is invaluable for developers who encounter database errors they have never seen before, DBAs triaging overnight alert notifications, and anyone who has ever pasted a database log into a search engine hoping for an explanation.