Skip to content

Detach Alert from Load Balancer

DELETE
/gateway/{gateway_id}/alerts/{attachment_id}/
curl --request DELETE \
--url 'https://api.e2enetworks.com/myaccount/api/v1/gpu/gateway/{gateway_id}/alerts/{attachment_id}/?project_id=<PROJECT_ID>&location=<LOCATION>&apikey=<API_KEY>' \
--header 'Authorization: Bearer <API_TOKEN>'

Detaches an alert from the Load Balancer, so the Load Balancer is no longer watched against it. The alert itself stays and can be attached again. Needs the Delete permission for Load Balancers.

gateway_id
required
integer

Load Balancer ID

attachment_id
required
integer

Alert attachment ID

project_id
required
integer

Project ID

active_iam
integer

Active IAM ID (To access contact person account) Find your Active IAM ID here

location
required
string
Allowed values: Delhi Chennai

Location

The alert was detached

Media typeapplication/json
object
code
integer
message

The detach success text.

string
data
object
errors
object

Example

{
"code": 200,
"data": {},
"errors": {}
}

project_id is missing or not a number. errors holds the project’s own text.

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

Example

{
"code": 400,
"message": "Bad Request",
"data": {}
}

No attachment with that ID on this Load Balancer, or the alert rule could not be removed. errors is the reason.

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

Example

{
"code": 412,
"message": "Precondition Failed",
"data": {}
}