​

ves-io-schema-alert_policy-CustomAPI-GetAlertPolicyMatch

Published April 5, 2023 | Last modified October 28, 2026

Examples of performing alert_policy CustomAPI GetAlertPolicyMatch

Usecase:

GetAlertPolicyMatch

Request:

Request using vesctl:

vesctl request rpc alert_policy.CustomAPI.GetAlertPolicyMatch -i request.yaml --uri /public/namespaces/documentation/alert_policy/match --http-method POST

where file request.yaml has following contents:

labels:
  alertname: podcrash
  group: IaaS
  namespace: documentation
  severity: critical

vesctl yaml response:

alertMatch: []

Request using curl:

curl -X 'POST' -d '{"labels":{"alertname":"podcrash","group":"IaaS","namespace":"documentation","severity":"critical"}}' -H 'Content-Type: application/json' -H 'X-Volterra-Useragent: v1/pgm=_var_folders_q2_3kp8z3zs0x5_m7pk1bgb0_ph0000gp_T_go-build3348201650_b001_apidocs.test/host=MTY6VVHQPH/svc=S:examplesvc/site=mytestce01' 'https://acmecorp.console.ves.volterra.io/api/alert/namespaces/documentation/alert_policy/match'

curl response:

HTTP/1.1 200 OK
Content-Length: 26
Content-Type: application/json
Date: Mon, 28 Sep 2026 04:24:33 GMT
Vary: Accept-Encoding


{
  "alert_match": [
  ]
}
On this page: