Show TOC

Background documentationProcess Server Alert Sources Locate this document in the navigation structure

 

Process server alert sources raise alerts when process servers change status. Likewise, job alert sources raise alerts when jobs reach a specific status.

They match on two criteria:

  • A pattern matching the name of the process server or job.

  • The new status of the process server or job.

Alerts will be raised if both Name and Statuses criteria match. Glob matching is done, so the wildcards * and ? can be used, just like in Microsoft Windows or Unix.

Actions

Process server alert sources support the following actions:

Action

Description

Export

Export the process server alert source into a CAR file

Edit

Edit the process server alert source

Edit Security

Edit the security of the process server alert source

Delete

Delete the process server alert source

Duplicate

Make a copy of the process server alert source to create a similar one

Expand All

Expand all process server alert sources in the current filter

New

Create a new process server alert source

Filter > New Filter

Create a new process server alert source filter

Filter > Edit Filter

Edit current process server alert source filter

Filter > Delete

Delete current process server alert source filter
Operator message and reply expressions

The operator message to use is specified as an expression that allows substitution parameters below. The message can be specified at the alert source level, and overridden per status. If no message is specified at any level, the default message is Acknowledge.

The reply expression works the same way as the reply expression for the System_OperatorMessage job. This can be specified at the alert source level, and overridden per status. If no reply expression is specified, the default reply expression is Acknowledge.

Variables

Process server alert sources support the following variables:

  • ${processServer} - the name of the process server that changed status.

  • ${oldStatus} - the old status of the process server.

  • ${newStatus} - the new status of the process server.

Escalation

When nobody has resolved the alert in a timely fashion, you can escalate the alert to another operator. This is done with escalations.

Process server alert sources use two rules to determine the alert escalation to use:

  • An expression to determine a dynamic escalation name. This expression supports ${variable} substitutions and the Redwood Expression Language syntax for expressions.

  • A default alert escalation

The expression is always evaluated first. If the escalation returned by the expression exists, then it is used. If it does not exist, then the default is used. This allows the escalation used to be dynamic.

For example, different escalation paths can be defined depending on the new status of a process server:

  • Match Name: PS_PRD*

  • Expression: PS_PRD_${newStatus}

  • Default: PS_PRD_Alert

  • Statuses: Connecting, PartiallyRunning, Shutdown, Unknown

  • The following alert escalations are defined: PS_PRD_Connecting, PS_PRD_Shutdown, PS_PRD_Alert

If the new status of a process server named PS_PRD_EMEA_DB2, for example, is:

  • Connecting - PS_PRD_Connecting will be tried, found and used.

  • Unknown - PS_PRD_Unknown will be tried, but not found, so PS_PRD_Alert will be used.

  • Shutdown - PS_PRD_Shutdown will be tried, found and used.

  • Running - no alert will be raised.

Alert Source Actions

Alert source actions are used to customize the behavior using RedwoodScript.

Finding Process Server Alert Sources

You can search for process server alert sources using filters and the Search Process Server Alert Sources box on the Process Server Alert Sources tab. This box is known as the intelliSearch box and located under your username on the top right-hand side of the user interface. Filters allow you to specify a list of objects with static criteria. IntelliSearch allows you to specify complex queries in a simple way using prefixes. Prefixes are used to specify which property you are searching in and have short and long syntaxes. For example, if you want to display all process server alert sources with the term error in the comment, you would use the search criteria as follows:

c:error

You can search more than one property, as follows:

c:error n:all

Note Note

No spaces should be entered before or after the colon (:).

End of the note.

See the Advanced Object Search for more information.

The following table illustrates the available prefixes for process server alert sources:

Prefixes

Description

n, name

searches the name property

c, com, comment

searches the comment property

d, desc, description

searches the description property

a, app, application

searches the application property
Security

Privilege

Description

ProcessServerAlertSource.Create

Create process server alert sources

ProcessServerAlertSource.Delete

Delete process server alert sources

ProcessServerAlertSource.Edit

Edit process server alert sources

ProcessServerAlertSource.View

Access process server alert sources

You can grant privileges on two levels, Access and Admin; a privilege granted on Admin level allows the grantee to grant the privilege to other users. These privileges can be granted system-wide, per partition or isolation group.

If you have the security module, which requires the Module.Security license key, you have an additional Security tab on the process server alert source. It allows you to specify which users can access, edit, and delete the process server alert source.