Update an alertCopy Pageput https://{hostname}/alerts/v2/alert-definitions/{definitionId}Modifies the criteria that determine when an alert fires.Path ParamsdefinitionIdstringrequiredIdentifies the alert definition.Query ParamsaccountSwitchKeystringFor customers who manage more than one account, this runs the operation from another account. The Identity and Access Management API provides a list of available account switch keys.Body ParamsAlert configured with thresholds for monitoring.accountIdstringlength ≥ 1Identifies the account under which the alert was created.definitionIdstringlength ≥ 1Identifies the alert definition.editInfoobjectA summary of the alert's creation time and most recent edit.editInfo objectfieldsobjectrequiredThe set of criteria that determines when the alert fires. The object's members vary depending on the template on which the alert is based. However, all fields include a name, the templateId on which the alert was based, and an array of email addresses for the alert's recipients.fields objectlinksarray of objectslength ≥ 2Link relations to schemas and REST endpoints.linksADD objectoriginstringenumIdentifies the type of alert the template enables, either STATIC or ADAPTIVE. Static alert types specify raw values, while the adaptive alert type expresses standard deviations. The only available ADAPTIVE alert identifies excessive traffic, and its templateId is a@1.STATICSTATICADAPTIVEAllowed:STATICADAPTIVEResponses 204Alert successfully updated. 400Bad request. 401Unauthorized error. 403Access is forbidden. 405Method not allowed. 415Unsupported media type. 500Server error.Updated 4 months ago