Headless Actions

Example: It's possible to schedule Export Report to Server File action of a Recent Alerts report and use bindings to generate a different file name each time the report is being exported. In this case, the following binding should be added to the Input: Export to Server File table:

• Target: File Path (file), String

• Expression: "alerts_report_" + year(now()) + "_" + month(now()) + "_" + day(now()) + ".pdf"

Example: We can execute an external application upon alert by adding Execute Application action to the list of alert's corrective actions. However, it's often necessary to pass alert message and other alert parameters to this application. In this case, the following and similar bindings should be added to the Input: Execute Application or Operating System Command table:

• Target: Command (command), String

• Expression: """ + cell({env/parameters}, "message") + """

This expression refers parameters environmental variable those value is a Data Table associated with alert event.

Example: To send an e-mail message upon an alert with custom text that describes alert cause, add Send E-mail automatic corrective action to the alert, open its input parameters, get inside Input: Send E-Mail table:

• Target: Message (message), String

• Expression: "An alert was raised, it is caused by value of custom field: " + cell(cell({env/parameters},'data'),'customField')

This expression refers parameters environmental variable those value is a Data Table associated with alert event. It then uses first (inner) cell() function to extract data table that corresponds to value of variable (or data of an event) that has caused the alert. Another (outer) cell() function extracts custom field out of this data table. The field value is appended to e-mail message text.