DX Infrastructure Management

How to ensure that e2e alarms generated from a transaction script are displayed under the dedicated e2e robot in USM.

Customers, especially those new to transaction scripting may find that their e2e alarms are showing up in the Infrastructure Manager alarm sub-console but they are not showing up under the e2e Robot in USM. In the old deprecated alarm console, the use of nimSetCI within the script was not required since it was not predicated on CI Id information in the alarm (dev_id and met_id).

See attached sample script.

e2e_script_example_nimSetCI_function.docx

https://docops.ca.com/ca-unified-infrastructure-management-probes/ga/en/alphabetical-probe-articles/e2e_appmon-e2e-application-response-monitoring/e2e_appmon-api#e2e_appmonAPI-nimSetCi