Skip to main content

InterSystems IRIS SNMP Traps

InterSystems IRIS SNMP Traps

In addition to the object data and metrics available through SNMP queries, InterSystems IRIS can send asynchronous alerts or SNMP traps. The following table describes the InterSystems IRIS-specific SNMP traps.

InterSystems IRIS SNMP Notification Objects (Traps)
Trap Name (Number) Description
irisStart (1) The InterSystems IRIS instance has been started.
irisStop (2) The InterSystems IRIS instance is in the process of shutting down.
irisDBExpand (3) An InterSystems IRIS database has expanded successfully.
irisDBOutOfSpace (4) Future expansion of an InterSystems IRIS database may be limited; there is not enough free space on the file system for 10 more expansions or there is less than 50 MB of free space.
irisDBStatusChange (5) The read/write status of an InterSystems IRIS database has been changed.
irisDBWriteFail (6) A write to an InterSystems IRIS database has failed. It includes the InterSystems IRIS error code for the failed write.
irisWDStop (7) The write daemon for an InterSystems IRIS instance has stalled.
irisWDPanic (8) The write daemon for an InterSystems IRIS instance has entered “panic” mode; that is, the write daemon is out of buffers and must write database blocks directly to disk without first committing them to the Write Image Journal (WIJ) file.
irisLockTableFull (9) The lock table for an InterSystems IRIS instance is full, which causes subsequent Locks to fail.
irisProcessFail (10) A process has exited InterSystems IRIS abnormally (due to an access violation). For detailed information, see the messages.log file.
irisECPTroubleDSrv (11) A connection to this ECP Data Server for an InterSystems IRIS database has encountered a serious communication problem. For detailed information, see the messages.log file.
irisECPTroubleASrv (12) A connection from this ECP Application Server to a remote InterSystems IRIS database has encountered a serious communication problem. For detailed information, see the messages.log file.
irisAuditLost (13) InterSystems IRIS has failed to record an Audit event. The most likely cause is a problem with space for the Audit database, which requires operator assistance.
irisLoggedError (14) A “severe ” error has been logged in the messages.log file. This trap includes the error message defined in irisSysErrorMsg.
irisLicenseExceed (15) A request for a license has exceeded the number of licenses currently available or allowed.
irisEventLogPost (16) An entry posted in the Interoperability Event Log.
irisAppAlert (100) This is a generic trap that can be used by InterSystems IRIS applications to generate alerts via SNMP. For detailed information about how this trap can be used, see the %Monitor.Alert.External class method.

The following table describes the InterSystems IRIS-specific auxiliary objects that can be sent in the traps described in the preceding table.

InterSystems IRIS-specific Auxiliary Objects Sent in Traps
Auxiliary Object Name (Number) Description
irisDBWriteError (1) The InterSystems IRIS-specific error code for a failed database write. Possible values are: <DATABASE>, <DISKHARD>, <BLOCKNUMBER>, <FILEFULL> or <DATABASE MAP LABEL>.
irisApp (2) A short text string (maximum of 20 characters) that identifies the application that generated (or was the source of) an irisAppAlert trap.
irisAppSeverity (3) A code that indicates the severity of the problem for a irisAppAlert trap. The code can be 0 (info), 1 (warning), 2 (severe), or 3 (fatal).
irisApptext (4) A text string description (maximum of 1024 characters) of the problem, error, or event that caused the irisAppAlert trap.
FeedbackOpens in a new tab