​

ves-io-schema-shape-bot_defense-reporting-CustomAPI-MaliciousAttackIntentTimeSeries

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

Examples of performing reporting CustomAPI MaliciousAttackIntentTimeSeries

Usecase:

MaliciousAttackIntentTimeSeries in ns1,

Request:

Request using vesctl:

vesctl request rpc reporting.CustomAPI.MaliciousAttackIntentTimeSeries -i request.yaml --uri /public/namespaces/ns1/reporting/traffic/malicious/dimension/attackintent/timeseries --http-method POST

where file request.yaml has following contents:

namespace: ns1

vesctl yaml response:

attackIntentData: []

Request using curl:

curl -X 'POST' -d '{"namespace":"ns1"}' -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/shape/bot/namespaces/ns1/reporting/traffic/malicious/dimension/attackintent/timeseries'

curl response:

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


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