Skip to content

Pause or Resume Alert / Pause or Resume a Cluster Alert

PUT
/api/v1/monitoring/single-service/stop_resume_alert/{alert_trigger_id}/
curl --request PUT \
--url 'https://api.e2enetworks.com/myaccount/api/v1/monitoring/single-service/stop_resume_alert/{alert_trigger_id}/?project_id=<PROJECT_ID>&apikey=<API_KEY>&location=<LOCATION>' \
--header 'Authorization: Bearer <API_TOKEN>' \
--header 'Content-Type: application/json' \
--data '{
"action_type": "pause_alert"
}'

Pauses or resumes an existing alert trigger without deleting it. The action_type field in the body selects the operation (pause_alert or resume_alert). The alert trigger ID is the id returned by Create Alert.

Pauses or resumes an existing alert. Send action_type: "pause_alert" to stop the alert from firing, or action_type: "resume_alert" to re-enable it. The path takes the alert’s alert_trigger_id.

Pause or Resume Alert and Pause or Resume a Cluster Alert share this request; the body you send decides which one runs.

alert_trigger_id
required
integer

The alert_trigger_id from an entry in the trigger array returned by the List Alert Triggers endpoint.

Example

34567
project_id
required
integer

Identifier of the project to scope the request to. Required integer project ID.

Example

<PROJECT_ID>
apikey
required
string

API key used to authenticate the request

Example

<API_KEY>
location
required
string

Region scope for the alert.

Example

<LOCATION>
Media typeapplication/json
One of:
object
action_type
required

Whether to pause or resume the alert trigger.

string
Allowed values: pause_alert resume_alert

Example

pause_alert

Successful response

Media typeapplication/json
object
code
integer
data
string
errors
object
message
string

Example

{
"code": 200,
"data": "",
"message": "Alert paused successfully."
}