Each PingData sever provides delivery mechanisms for account status notifications, administrative alerts, and alarms using SMTP, JMX, or SNMP
Alerts, alarms, and events reflect state changes within the server that may be of interest to a user or monitoring service. Account status notifications are only delivered to the account owner. Alert handler implementations include:
- Error log alert handler
- Sends administrative alerts to the configured server error logger(s).
- Exec alert handler
- Executes a specified command on the local system if an administrative alert matching the criteria for this alert handler is generated by the server. Information about the administrative alert is made available to the executed application as arguments provided by the command.
- Groovy scripted alert handler
- Provides alert handler implementations defined in a dynamically-loaded
Groovy script that implements the
ScriptedAlertHandlerclass defined in the Server SDK.
- JMX alert handler
- Sends administrative alerts to clients using the Java Management Extensions (JMX) protocol. PingData uses JMX for monitoring entries and requires that the JMX connection handler be enabled.
- SMTP alert handler
- Sends administrative alerts to clients via email using the SMTP. The server requires that one or more SMTP servers be defined in the global configuration.
- SNMP alert handler
- Sends administrative alerts to clients using the Simple Network Monitoring Protocol (SNMP). The server must have an SNMP agent capable of communicating through SNMP.
- SNMP subagent alert handler
- Sends SNMP traps to a primary agent in response to administrative alerts generated within the server.
- Third party alert handler
- Provides alert handler implementations created in third-party code using the Server SDK.
A complete listing of system alerts, alarms, and their severity is available in <serverroot>/docs/admin-alerts-list.csv