​

ves-io-schema-graph-l3l4-CustomAPI-EventCount

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

Examples of performing l3l4 CustomAPI EventCount

Usecase:

Get data for events count

Request:

Request using vesctl:

vesctl request rpc l3l4.CustomAPI.EventCount -i request.yaml --uri /public/namespaces/system/graph/l3l4/event_count/123 --http-method POST

where file request.yaml has following contents:

endTime: "2020-01-30T18:00:00Z"
namespace: system
startTime: "2020-01-30T17:00:00Z"

vesctl yaml response:

events:
- bounded: "2"
  ongoing: "3"
  timestamp: "0001-01-01T00:00:00Z"
- bounded: "3"
  ongoing: "3"
  timestamp: "0001-01-01T00:00:00Z"

Request using curl:

curl -X 'POST' -d '{"namespace":"system","start_time":"2020-01-30T17:00:00Z","end_time":"2020-01-30T18:00:00Z"}' -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/infraprotect/namespaces/system/graph/l3l4/event_count/123'

curl response:

HTTP/1.1 200 OK
Content-Length: 218
Content-Type: application/json
Date: Mon, 28 Sep 2026 04:25:23 GMT
Vary: Accept-Encoding


{
  "events": [
    {
      "timestamp": "0001-01-01T00:00:00Z",
      "bounded": "2",
      "ongoing": "3"
    },
    {
      "timestamp": "0001-01-01T00:00:00Z",
      "bounded": "3",
      "ongoing": "3"
    }
  ]
}
On this page: