-
Title
Questions about Sybase errors and DatabaseErrorlog tables -
Description
How does Foglight retrieve Sybase errors?
How are the tables DatabaseErrorlog and DatabaseErrorlogDetails used, and how does Foglight decide the severity of the messages? -
Cause
-
Resolution
Foglight collects the information that is passed into these tables from the Sybase MDA table -> "monErrorLog".
Foglight sums up the rows (grouped by severity) that appeared since the last poll cycle into the "DatabaseErrorLog". The Foglight rule for this table is to fire an alert if there are any rows with the severity WARNING, CRITICAL, or FATAL (the severity is derived from the "monErrorLog table" and cross referenced with Sybase's description of severity levels)
The ErrorLogDetail tables simply returns the rows that match the criteria for the error log filter (message trap) - by default only Error Messages are returned (messages with text 'Error:')- Navigate to Administration | Agents | Agent Status
- Select the Sybase agent
- Click the Edit Properties button
- Click the link to Modify properties for this agent only.
- Click the Edit button next to Message Trap List
- Add or Edit error log message trap entries
- Click on the Save Changes button
Sybase_MDA Agent Database_Error_Log Rule
PurposeThe Database_Error_Log rule reports the messages in the ASE error log matching the patterns in the Log Filter List in the agent property. If Warning or Critical messages are detected, the rule sends an email to the database administrator specifying the total numbers of Warning and Critical messages. The alarm message indicates the name of the Adaptive Server, the number of instances with the related error number, the severity level (Warning or Critical) and the current state of theAdaptive Server.
Scope
Sybase_MDA_DatabaseErrorlog
Interpreting the RuleThis rule fires when messages are written to the ASE error log since the last collection cycle after meeting a set of user-specified filter patterns. When receiving an alert, the database administrator should review the server's error log and decide how to resolve the problem.
Sybase_MDA Agent DatabaseErrorLog Data Table.
The DatabaseErrorLog table stores any messages from the server error log that meet the criteria or pattern defined in the agent properties. The following table describes the data stored in the DatabaseErrorLog table:
Field Description error_count The number of times the error occurs in the database. server_error The error number of the trapped message. severity The severity of the error that is trapped: 1 = INFORMATIONAL2 = WARNING3 = WARNING4 = CRITICALuser_message A short description of the severity type. Sybase MDA Agent Database Error Log Details By Severity
PurposeThe Database_Error_Log_Details_By_Severity rule fires an alarm of appropriate severity when a new message arrives in the DatabaseErrorLogDetails topology from the Sybase error log.
Scope
Sybase_MDA_DatabaseErrorlogDetails
Interpreting the RuleWhen a new message arrives in the DatabaseErrorLogDetails topology from the Sybase error log, this rule filters the message and fires an alarm with the appropriate severity (Warning, Fatal, or Critical). The filter and severities are defined in the Message Trap List ASP.
Views Which Render the Data on Which This Rule is Based
- Sybase Error Log on the Instance pane of the “MDA Home Page Dashboard”
Sybase_MDA Agent DatabaseErrorLogDetails Data Table
The DatabaseErrorLogDetails table stores any messages from the server error log that meet the criteria or pattern defined in the agent properties. The following table describes the data stored in the DatabaseErrorLogDetails table:
Field Description engine_num The engine on which the process was running. error_message The text of the error message. error_num The error message number. error_severity The severity of the error. error_time The timestamp when the error occurred. fid The Session process identifier (SPID) of the parent process.kpid The kernel process identifier. spid The session process identifier.