SNMP Traps (Magic xpa 2.x)

The Magic engine, broker and requester will send SNMP compliant messages to the SNMP monitor (NMS). These will be messages regarding the process and not the application. Application messages will continue to be sent to the Magic xpa Activity Log. Errors will be sent to the various logs independently, which means that errors and traps can be found both in the logs and in the NMS.

Non-applicative traps from the enterprise server

• Thread crash / every fatal error of Magic xpa and the gateway

• Termination due to license limit

• Cannot establish connection to a specific DBMS

• Database connections threshold reached

Note: If an SNMP trap cannot be sent, the error will be written only as an Activity Log error.

Non-applicative traps from the Broker

• An enterprise server was stopped or started (enterprise server’s address)

• An enterprise server aborted its connection to the broker (the trap will contain the enterprise server’s address)

• The broker aborted (it is automatically restarted by itself)

• Request timed out

• Threshold limit reached:

• • Average wait time

  • Average process time

Note: If an SNMP trap cannot be sent, the error will be written only as an Activity Log error.

Non-applicative traps from a Requester

Requester status codes are sent to the NMS, for example –105.

Note: If an SNMP trap cannot be sent, the error will be written only to the requester log.