...
In addition, FioranoMQ provides built-in support for registering SMTP alerts for various types of System Events. For Backlog and Memory Events, you have a choice to sign up for JMS alerts. Alert registration can be done via dashboard. Refer to sections Server Status and Document Tracking for instructions regarding this.
...
Service Events raised by the Peer Server contain information about the current status of the service such as whether the service is running or not. Using the dashboard, you can register to receive SMTP alerts when a particular service within an Event Process is launched or killed. These alerts can be useful in detecting abnormal service termination due to unexpected errors such as a JVM crash or an unintentional shutdown. Please refer to Server Status section for more details.
...
Using the dashboard, you can create backlog policies and define SMTP/JMS alerts to be sent when a service has more than the specified number of messages in its pending messages queue. You may also create more than one policy for a single service to receive alerts at multiple levels of a pending message queue. For example, registering to receive SMTP /alerts or registering to receive JMS alerts when the size of the pending message queue reaches 5, 10 or 15 either in an upward or a downward direction. Please refer to Monitoring section for more details on Backlog Monitoring feature.
...
Using the dashboard, you can create memory usage policies to receive SMTP/JMS alerts when a Server memory reaches the specified threshold. These alerts can be used as a preventive measure to avoid any future issues caused by Out Of Memory problems. Please refer to Document Tracking in for more details.
| Anchor | ||||
|---|---|---|---|---|
|
While registering to receive SMTP alerts or registering to receive JMS alerts, Dashboard configures the framework to send email alerts for various events. Below is the list of Events under various Event Types.
| Event Type | Events Raised | Description |
|---|---|---|
| Application | APPLICATION_LAUNCH_STARTED | Starting launch of an application |
APPLICATION_LAUNCHED | Successful launch of an application | |
| APPLICATION_KILLED | Successful stop of an application | |
| APPLICATION_SYNCHRONIZED | Synchronize call sent to an application | |
| Service | SERVICE_HANDLE_BOUND | Service handle created / Service started |
SERVICE_HANDLE_UNBOUND | Service handle destroyed / Service stopped | |
| SERVICE_FAILED_TO_LAUNCH | Service failed to start | |
| FPS | FPSTIFOSI_SERVER_UNAVAILABLE_EVENT | Peer Server disconnected |
| TIFOSI_SERVER_RECONNECT_EVENT | Peer Server reconnected | |
| TIFOSI_SERVER_LAUNCHED | Peer Server started | |
| TIFOSI_SERVER_SHUTDOWN | Peer Server shutdown | |
| FES | FESSERVICE_PROVIDER_STARTED | Enterprise Server Started |
| Security | CREATE_ACL_REQUEST | Permission to create an ACL |
| SET_ACL_REQUEST | Permission to change / add new values to an existing ACL | |
| TPS_LOGIN_REQUEST | Permission seeked by Peer for logging in to the Enterprise Server | |
| APPLICATION_PREPARE_LAUNCH_REQUEST | Permission to Check Resources and Connectivity of an application | |
APPLICATION_LAUNCH_REQUEST | Permission to launch an application | |
| SP_LOGIN_REQUEST | Permission for Client for logging in to the Enterprise Server | |
| APPLICATION_KILL_REQUEST | Permission to Stop Event Process |