Appendix: Email Notifications Generated By Services Director
Notifications/Alerts from the Services Director Core Software
The following notifications are generated from the core Services Director software. They are common to both the software-only and VA form factors of Services Director.
Only email subject lines are shown. Email bodies will normally contain further detail related to the reason for the notification/alert.
Functionality | Area Email Subject Line | Event Description |
|---|---|---|
Licensing | Ivanti Services Director: License is due to expire on <Services Director host> | Sent on a daily basis when a Services Director controller license is due to expire within the license expiry warning period (this warning period is configurable, but defaults to 30 days). |
| Ivanti Services Director: Required bandwidth/add-on pack is due to expire on <Services Director host> | Sent on a daily basis when a Services Director bandwidth pack license is due to expire within the bandwidth license expiry warning period (this warning period is configurable, but defaults to 30 days). |
Monitoring | Ivanti Services Director Monitoring has detected <failure / recovery events> | Sent as a result of monitoring detecting that connectivity to vTM instances or Services Director controllers have either failed or recovered after a failure. |
vTM Self-Registration | Instance <Instance name> has registered itself and requires your attention. | Sent when a self-registering instance has sent a registration request that the Services Director Administrator may wish to manually accept. |
| Instance <instance name> has re-registered itself and requires your attention. | Sent when a self-registering instance has been declined but has attempted to self-register again with different parameters. |
| Instance <instance name> has registered itself and was auto-accepted by policy <policy name> | Sent when a self-registering instance has been received by Services Director, and automatically accepted by an auto-acceptance policy. |
| Instance <instance name> registered itself and failed to be auto-accepted by <policy name> | Sent when a self-registering instance has been received by Services Director, but for some reason failed to be automatically accepted by an auto-acceptance policy. |
Metering | Services Director: Metering Warnings have been found for instances on <Services Director host> | Sent periodically if potential metering discrepancies are identified. |
| Ivanti Services Director: Log space low on <Services Director host> | Sent periodically if available log space has dropped below 512 MB (the period is configurable, but set to one hour by default). |
| Ivanti Services Director: Log space critical on <Services Director host> | Sent periodically if available log space has dropped below 256 MB (the period is configurable, but set to one hour by default). |
| Metering phone-home successful | Sent to confirm that Services Director has successfully sent a set of metering logs back to Ivanti. |
| Metering phone-home failure | Sent if Services Director has been unable to send a set of metering logs back to Ivanti. |
Notifications/Alerts from the Services Director VA
The following notifications are sent from the Services Director VA. These are in addition to those sent from the Core software.
Only email subject lines are shown. Email bodies will normally contain further detail related to the reason for the notification/alert.
Event Description | Functionality | Area Email Subject Line |
|---|---|---|
Local Services Director Process Failure (Killed or Crashed) | Services Director service | Local Services Director Failure Notification |
Local Services Director Process Recovery | | Local Services Director Recovery Notification |
Local DB Failure | Database | Local Database Failure Notification |
Local DB Recovery | | Local Database Recovery Notification |
Peer Services Director Failure | High Availability | Peer Services Director Connectivity Failure Notification |
Peer Services Director Recovery | | Peer Services Director Connectivity Recovery Notification |
Local Gluster Failure | | Local File System Replication Failure Notification |
Local Gluster Recovery | | Local File System Replication Recovery Notification |
Services Director Backup Generation Failure | Disaster Recovery | Backup Generate Operation Failure Notification |
Services Director Backup Generation Recovery | | Backup Generate Operation Recovery Notification |
Services Director Backup Transfer Failure | | Backup Transfer Operation Failure Notification |
Services Director Backup Transfer Recovery | | Backup Transfer Operation Recovery Notification |
Master Password Missing | Master Password | Master password Operation Failure Notification |
Master Password Recovery | | Master password Operation Recovery Notification |
Crash Core Generated | System | Core file found for process: <Process Name> |
High CPU Usage | | CPU utilization too high |
High CPU Usage Recovery | | CPU utilization alarm clearing |
Paging Alarm | | Paging activity too high |
Paging Alarm Cleared | | Paging activity alarm clearing |
File Systems Mount Failures | | File System %s is full |
File System Mount Recovery | | File System %s is no longer full |
Link State | | Linkstate alarm triggered |
Link State Cleared | | Linkstate alarm cleared |
Link Duplex | | Link duplex alarm triggered |
Link Duplex Clear | | Link duplex alarm cleared |
Link IO Errors | | Link I/O errors alarm triggered |
Link IO Errors Recovery | | Link I/O errors alarm cleared |
Memory Error | | Memory Error Detected |
Memory Error Cleared | | Memory error alarm cleared |
Unexpected Shutdown | | Unexpected shut down |
Secure Vault Locked | | Secure vault must be unlocked |
Secure Vault Unlocked | | Secure vault has been unlocked |
Process Crash | | Process failure: %s |
Process Unexpected Exit | | Process exit: %s |