Flow Anomaly¶

Low Risk

Operations on this resource are generally safe.

List the set of flow_anomaly in a namespace.

Tools¶

Tool	Description
`f5xc-api-statistics-flow-anomaly-get`	GET Flow Anomaly.
`f5xc-api-statistics-flow-anomaly-list`	List Flow Anomaly.

Parameters¶

Path Parameters¶

Parameter	Description	Example
`name`	Name	`-`
`namespace`	Namespace	`-`

Query Parameters¶

Parameter	Description	Example
`response_format`	The format in which the configuration object is to be fetched. This could be for example	`-`
`label_filter`	A LabelSelectorType expression that every item in list response will satisfy.	`-`
`report_fields`	The report_fields parameter	`-`
`report_status_fields`	The report_status_fields parameter	`-`

Example Usage¶

Ask Claude to help you work with Flow Anomaly resources:

List Flow Anomalys¶

"List all flow-anomalys in the 'production' namespace"

Get Flow Anomaly Details¶

"Get details of the flow-anomaly named 'example' in namespace 'production'"

CURL Examples¶

# List resources
curl -X GET "https://${TENANT}.console.ves.volterra.io/api/config/namespaces/${NAMESPACE}/flow_anomalys" \
  -H "Authorization: APIToken ${F5XC_API_TOKEN}" \
  -H "Content-Type: application/json"

# Get specific resource
curl -X GET "https://${TENANT}.console.ves.volterra.io/api/config/namespaces/${NAMESPACE}/flow_anomalys/<name>" \
  -H "Authorization: APIToken ${F5XC_API_TOKEN}" \
  -H "Content-Type: application/json"

# Create resource
curl -X POST "https://${TENANT}.console.ves.volterra.io/api/config/namespaces/${NAMESPACE}/flow_anomalys" \
  -H "Authorization: APIToken ${F5XC_API_TOKEN}" \
  -H "Content-Type: application/json" \
  -d @flow_anomaly.json

# Delete resource
curl -X DELETE "https://${TENANT}.console.ves.volterra.io/api/config/namespaces/${NAMESPACE}/flow_anomalys/<name>" \
  -H "Authorization: APIToken ${F5XC_API_TOKEN}"