When you configure alerts, they use the following template:
Event: <the type of event>
Value: <the specific trigger for the event>
When: <the date and time of the event>
Where: <the IP address or hostname of the server where the event occurred>
The following is an example alert you might receive:
Event : high memory usage
Value : 82.19%
When : 2019-May-16 18:30:00 PST
Where : vortex-132
Email alerts are sent based on the following event categories:
- System resource
- System resources are polled every 30 minutes to calculate usage. An email alert is sent if the value exceeds the defined threshold.
- Configuration
- When configuration changes occur, an email alert is sent for these events:
- Adding or removing an API
- Adding or deleting a server
- Nodes of a cluster are
UP
orDOWN
- Decoy API
- When decoy APIs are accessed for the first time, an email alert is sent. The time between
consecutive alerts is set using
decoy_alert_interval
in the ase.conf file. The default value is 180 minutes.Note:For more information on decoy APIs, see In-Context decoy APIs.
- ASE-ABS log transfer and communication
- ASE sends an alert in the following two conditions:
The following alerts are logged in the controller.log file when email
alerts are disabled (enable_email=false
) in the
ase.conf file:
- High CPU use
- High memory use
- High filesystem use
- Adding API to ASE
- Removing API from ASE
- Updating and API
- Adding a backend server
- Removing a backend server
- ASE cluster node available
- ASE cluster node unavailable
- Backend server state changed to UP
- Backend server state changed to DOWN
- Log upload service failure
- Error while uploading file
- Invalid ASE license file
- Expired ASE license file