Configuring and viewing email notifications
As a cloud user, if you provision a service offering instance (SOI) and the instance fails, there is no way to locate at which step the service offering instance failed or even rectify the error and restart the SOI. In previous releases, as a cloud administrator, if an SOI failed, an end user would notify you of the SOI failure, but there was no automated notification that immediately alerted you about the failure. You would troubleshoot the issue by deciphering the logs and look for the exact root cause of the failure.
Now, in the Configuration workspace of BMC Cloud Lifecycle Management, you can enter the email addresses of a cloud administrator or a group of administrators to notify them about SOI provisioning failure. This group of administrators receives automatic email notifications whenever the SOI provisioning fails. (The notifications can be sent only for SOI provisioning failures.) The email provides detailed steps about how and at what stage the SOI provisioning failed. A hyperlink in the email notification points the cloud administrator to the Troubleshooting menu on the BMC Cloud Lifecycle Management – My Cloud Services console.
This topic includes the following sections:
If the Platform Manager is restarted while the SOI is provisioning, the email notification does not have complete information. If the SOI is in the early stages of provisioning, the automated email notification might not be sent.
The following BMC Communities video (6:08) demonstrates the information discussed in this topic.
To configure email notifications for a cloud administrator
- Log on to the BMC Cloud Lifecycle Management Administrator Console.
- Click the vertical Workspaces menu at the left and select Configuration.
- Click the Notifications tab.
In the SMTP Server Configuration area, enter the information as described in the following table to configure SMTP server connection.
Field Description SMTP Host Name The host name of your SMTP server SMTP Port The port on which your SMTP server Sender's Email Address The email address of the sender from whose account the email notifications are sent SMTP Authentication Specifies whether to authenticate the connection to the SMTP server SMTP User Name The user name required to log on to the SMTP server SMTP Password The password that corresponds to the user name Use TLS encryption Specifies whether to use TLS encryption to establish a secure connection
In the Admin Notifications area, enter the information as described in the following table to configure administrators to receive email notifications.
You can specify any valid email address and the user would receive the email notifications for service offering instance provisioning failures. However, to access the BMC Cloud Lifecycle Management console to view more information about the failure or to remediate the root cause for the provisioning failure, the user should be a cloud administrator.
Field Description Send Notifications For Currently, you can only configure email notifications for service offering instance provisioning failures. By default, the Service Provisioning Failures check box is selected. To Email addresses of administrators whose names should be marked in the To field when the email is sent. You can specify multiple comma-separated email addresses. CC Email addresses of administrators whose names should be marked in the CC field when the email is sent. You can specify multiple comma-separated email addresses. BCC Email addresses of administrators whose names should be marked in the BCC field when the email is sent. You can specify multiple comma-separated email addresses.
- Click Save.
The details are saved and the Save button is disabled. If you make any changes and click Revert to Save, the changes are not saved.
Viewing email notifications
The following figure shows a sample email notification a cloud administrator might receive.
Components of the email proactive notifications
Name of the service offering instance that failed.
Name of the service offering based on which the service offering instance is provisioned
Name of the requestable offering
Service Request Id
The request ID for the SOI
Name of the service blueprint associated with the service offering
On behalf of User
If the service offering instance is provisioned on behalf of any other user, then that user’s name is shown here
|On behalf of Tenant||The tenant to which the user on whose behalf the SOI is provisioned|
Name of the user who has provisioned the SOI
Name of the tenant to which the user belongs
Time and date when the service offering instance started provisioning
Time and date when the service offering instance stopped provisioning
Number of times the service offering instance is provisioned again after the failure
For example, if 2, the SOI is already provisioned twice and still fails.
Specific cause for SOI provisioning failure
|Suggested Action||Action to be taken to resolve the failure|
The stage where the service offering instance failed.
Typically, there are following four stages:
If the SOI fails at any of these stages, a detailed cause is provided.
Provisioning detailed steps
The details of the stages involved in provisioning the SOI.
After viewing the possible causes for the service offering instance provisioning failures, you can click the troubleshooting link in the email and retry provisioning service offering instances.
Log in or register to comment.