Substitution Parameters for Scripts

In the execution parameter string you supply to be passed to your shell script, you can include substitution parameters that are replaced at execution time with values from the alert that triggers the script.

Substitution parameters are available for both state-based and threshold-based alerts.

Substitution Parameters for State-based Alerts
Parameter Description
%Alert% A three-part name supplied by the alert system. It includes the names of this alert, the resource, and the key performance indicator on which this alert is based.
%Current_state% The current state of the resource on which this alert is configured.
%KPI% The name of the key performance indicator on which this alert is based.
%Resource% The name of the resource with which this alert is associated.
%SCC_URL% A link to Sybase Control Center, where more information about the alert may be available.
%Severity% The severity of this alert: critical or warning.
%Source_application% The application on the managed resource that generated this alert.
%Time% The date and time at which the alert fired, in this format:

Tue Sep 15 10:10:51 2009

%Top_resource% The name of the alerted resource’s top-level parent resource. This is valuable when the alerted resource is a component of a larger system (a database in a server, for example). If the alerted resource has no parent, %Top_resource% and %Resource% have the same value.
Substitution Parameters for Threshold-based Alerts
Parameter Description
%Alert% A three-part name supplied by the alert system. It includes the names of this alert, the resource, and the key performance indicator on which this alert is based.
%Datapoint% The current value, on the alerted resource, of the KPI on which this alert is based.
%KPI% The name of the key performance indicator on which this alert is based.
%Resource% The name of the resource with which this alert is associated.
%SCC_URL% A link to Sybase Control Center, where more information about the alert may be available.
%Severity% The severity of this alert: critical or warning. (Critical is more serious.)
%Source_application% The application on the managed resource that generated this alert.
%Threshold% The threshold value at which this alert fires.
%Time% The date and time at which the alert fired, in this format:

Tue Sep 15 10:10:51 2009

%Top_resource% The name of the alerted resource’s top-level parent resource. This is valuable when the alerted resource is a component of a larger system (a database in a server, for example). If the alerted resource has no parent, %Top_resource% and %Resource% have the same value.


Created February 25, 2010. Send feedback on this help topic to Sybase Technical Publications: pubs@sybase.com