Set and change timers for specific alerts, such as decreasing the required response time for a high-priority incident.
You can manage the timers for a specific alert manually in the CLI. This enables you to manage timers on a more granular level within specific alerts when the need arises. For example, the severity of the alert might dictate that you decrease the response time for the given alert.
Use the setAlert
command to set a specific alert due date or to set a specific timer field in an alert. When adding the sla
parameter to the command, it sets the time for the alert's due date. If you also add the slaField
you set the timer for the incident field.
For example, to change the Time to Assignment field target to 30 minutes in the current alert:
!setAlert sla=30 slaField=timetoassignment
To change the timer to February 1, 2024, at 11.12 am:
!setAlert sla=2024-02-01T11:12
Note
When defining the values for the slaField
use the machine name for the field, which is lowercase and without spaces. You can check the machine name by editing the alert field.
Use the following commands in the CLI:
Command | Description |
---|---|
| Starts the timer. For example, NoteTimer fields are not started automatically when an alert is created unless run in a playbook. |
| Pauses the timer. For example, |
| Stops the timer. For example, NoteTimers are automatically stopped when an alert is closed. |
| Clears all fields for the timer. This command must be used before restarting a timer that was stopped. For example, |
Note
When running commands in the CLI, you can specify the alertID
to change the timer for a different alert.