Object Name in Email Notification for Service Level Objective (SLO)

[Edward Teoh]

Hi,

I am working on the Service Level Objective (SLO) and would like to send a notification with the monitored object name in the email notification.

I came across the article Service Level Objective - Fulfillment Criteria (automic.com)

and aware that the following script variables can be used to provide details on the services and reasons for the violation:

• &uc_slm_slo_name#
• &uc_slm_service_name#
• &uc_slm_service_runid#
• &uc_slm_service_time#
• &uc_slm_violation_msg_number#
• &uc_slm_violation_msg_insert#

Appreciate for advice how can I incorporate the variables into the email notification

[Krum Ganev]

Hello,

There are already predifined such CALL objects. You can use them and adjust as per your needs.

------------------------------
------------------------------
Automic SME @ DXC.Technology
------------------------------
------------------------------

[Edward Teoh]

Thank you for sharing, Krum Ganev

[Georgiy Prykhnenko]

Hi Edward,

For example:

:set &runid# = &uc_slm_service_runid#
:set &object_name# = &uc_slm_service_name#
: p "Object name - &object_name#, Runid - &runid#"

Georgiy

[Marilyn Singley]

I wanted the SLO object to send me an email whenever a job failed.


You can also update the CALL Fulfillment_Mail_Notification object in the Process tab, to include different items. 
In this example, I changed the Subject line of the email, &uc_slm_service_name# is the name of the object, then the Runid, then the JOBP run id, then the Client as &$client#. 

:if &lang# = 'E'
: put_att SUBJECT = "SIT/AUT Job Failure Notification, &uc_slm_service_name#, RunID: &uc_slm_service_runid#, Client: &$client#"
: set &tt = "Notification"
: set &ht = "Service &slm_statustext#"
: set &c1#="AE System"
: set &c2#="Client"
: set &c3#="SL Objective"
: set &c4#="Service Name"
: set &c5#="Service RunID"
: set &c6#="Status"
: set &c7#="Detection Time"
: set &c8#="Message"
:endif

[Edward Teoh]

Thank you for sharing, Marilyn Singley

[Edward Teoh]

Thank you for sharing, Georgiy Prykhnenko