​

ves-io-schema-shape-brmalerts-alert_gen_policy-API-Replace

Published April 5, 2023 | Last modified March 20, 2025

Examples of replacing alert_gen_policy

Usecase:

Replace the alert that was created in previous example

Request using vesctl:

vesctl configuration replace alert_gen_policy -i alert_gen_policy.yaml

where file alert_gen_policy.yaml has following contents (alert_gen_policy.ReplaceRequest):

RequestJSON:

{
    "metadata": {
        "name": "analysis",
        "namespace": "system"
    },
    "spec": {
        "details": {
            "severity": "MAJOR",
            "alert_name": "Traffic Alert",
            "alert_message": "Traffic Alert Message",
            "alert_message_details": "Traffic Alert Message details"
        }
    }
}
Copied!

vesctl yaml response: None

Request using curl:

curl -X 'PUT' -d '{"metadata":{"name":"analysis","namespace":"system"},"spec":{"details":{"severity":"MAJOR","alert_name":"Traffic Alert","alert_message":"Traffic Alert Message","alert_message_details":"Traffic Alert Message details"}}}' -H 'X-Volterra-Useragent: v1/pgm=_var_folders_q2_3kp8z3zs0x5_m7pk1bgb0_ph0000gp_T_go-build436303540_b001_apidocs.test/host=MTY6VVHQPH/svc=S:examplesvc/site=mytestce01' 'https://acmecorp.console.ves.volterra.io/api/shape/alerts/namespaces/system/alert_gen_policys/analysis'
Copied!

curl response:

HTTP/1.1 200 OK
Content-Length: 4
Content-Type: application/json
Date: Tue, 11 Mar 2025 00:56:45 GMT
Vary: Accept-Encoding

{

}
Copied!
On this page: