​

ves-io-schema-log-CustomAPI-FirewallLogQuery

Published April 5, 2023 | Last modified June 17, 2026

Examples of performing log CustomAPI FirewallLogQuery

Usecase:

Perform FirewallLogQuery on log

Request:

Request using vesctl:

vesctl request rpc log.CustomAPI.FirewallLogQuery -i request.yaml --uri /public/namespaces/namespace-literal/firewall_logs --http-method POST

where file request.yaml has following contents:

{}

vesctl yaml response:

aggs: {}
logs: []

Request using curl:

curl -X 'POST' -d '{}' -H 'Content-Type: application/json' -H 'X-Volterra-Useragent: v1/pgm=_var_folders_q2_3kp8z3zs0x5_m7pk1bgb0_ph0000gp_T_go-build1414723615_b001_apidocs.test/host=MTY6VVHQPH/svc=S:examplesvc/site=mytestce01' 'https://acmecorp.console.ves.volterra.io/api/data/namespaces/namespace-literal/firewall_logs'

curl response:

HTTP/1.1 200 OK
Content-Length: 104
Content-Type: application/json
Date: Mon, 13 Apr 2026 01:59:48 GMT
Vary: Accept-Encoding


{
  "logs": [
  ],
  "total_hits": "0",
  "aggs": {
  },
  "scroll_id": "",
  "last_sort_values": null
}
On this page: