28.5. Configuring cluster alert meta options
As with resource agents, meta options can be configured for alert agents to affect how Pacemaker calls them. The following table describes the alert meta options. Meta options can be configured per alert agent as well as per recipient.
| Meta-Attribute | Default | Description |
|---|---|---|
|
|
|
If set to |
|
| %H:%M:%S.%06N |
Format the cluster uses when sending the event’s timestamp to the agent. This is a string as used with the |
|
| 30s | If the alert agent does not complete within this amount of time, it will be terminated. |
The following example procedure configures cluster alert meta options for both an alert agent and for the alert recipients. The procedure configures an alert that calls the script myscript.sh and then adds two recipients to the alert. The script gets called twice for each event.
Procedure
Configure an alert that calls the script
myscript.shand that uses a 15-second timeout.# pcs alert create id=my-alert path=/path/to/myscript.sh meta timeout=15sAdd an alert recipient that has an ID of
my-alert-recipient1, passing the call to the recipientsomeuser@example.comwith a timestamp in the format %D %H:%M.# pcs alert recipient add my-alert value=someuser@example.com id=my-alert-recipient1 meta timestamp-format="%D %H:%M"Add an alert recipient that has an ID of
my-alert-recipient2, passing the call to the recipientotheruser@example.comwith a timestamp in the format %c.# pcs alert recipient add my-alert value=otheruser@example.com id=my-alert-recipient2 meta timestamp-format="%c"