- Home
- API Enriched
- Telemetry And Insights
- data
- Flow Anomaly detection.
Flow Anomaly detection.
const url = 'https://example-corp.console.ves.volterra.io/api/v1/api/production/us-east-1/namespaces/default/api/data/namespaces/system/flows/top_flow_anomalies';const options = { method: 'POST', headers: {Authorization: '<Authorization>', 'Content-Type': 'application/json'}, body: '{"end_time":"example","field_selector":["BYTES"],"filter":"example","group_by":["SITE"],"limit":1,"sort_by":[{"sort_direction":"SORT_DIRECTION_DESC","sort_label":"SORT_LABEL_NONE"}],"start_time":"example"}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://example-corp.console.ves.volterra.io/api/v1/api/production/us-east-1/namespaces/default/api/data/namespaces/system/flows/top_flow_anomalies \ --header 'Authorization: <Authorization>' \ --header 'Content-Type: application/json' \ --data '{ "end_time": "example", "field_selector": [ "BYTES" ], "filter": "example", "group_by": [ "SITE" ], "limit": 1, "sort_by": [ { "sort_direction": "SORT_DIRECTION_DESC", "sort_label": "SORT_LABEL_NONE" } ], "start_time": "example" }'Request to GET flow anomaly records.
Authorizations
Section titled “Authorizations”Request Bodyrequired
Section titled “Request Bodyrequired”object
End time of flow collection Format: unix_timestamp|RFC 3339
Optional: If not specified, then the end_time will be evaluated to start_time+10m
If start_time is not specified, then the end_time will be evaluated to
Select fields to be returned in the response.
Required: YES.
\site-1”,“site-2”)}”
filter is used to specify the list of matchers
syntax for filter := {[
Optional: If not specified, counter will be aggregated based on the group_by labels.
Aggregate data by labels specified in the group_by field.
Limits the number of results.
Sort the data by specified fields, in the given direction.
Sorting for data by given fields.
object
Start time of flow collection Format: unix_timestamp|RFC 3339
Optional: If not specified, then the start_time will be evaluated to end_time-10m
If end_time is not specified, then the start_time will be evaluated to
Responses
Section titled “Responses”A successful response.
object
FlowAnomalyData wraps the response for flows with anomalies.
object
Data or content configuration
Anomaly Data contains key/value pairs that uniquely identifies the group_by labels specified in the request.
object
Data or content configuration
Security-related configuration
Configuration parameter for anomaly score
Configuration parameter for anomaly start time
Number of items or occurrences
Key-value labels for organization and selection
object
Configuration parameter for scan time
Data or content configuration
Example
{ "flowAnomalyData": [ { "anomaly_data": [ { "anomaly_level": "LOW_ANOMALY_LEVEL" } ], "type": "BYTES" } ]}Returned when operation is not authorized.
Examplegenerated
exampleReturned when there is no permission to access resource.
Examplegenerated
exampleReturned when resource is not found.
Examplegenerated
exampleReturned when operation on resource is conflicting with current value.
Examplegenerated
exampleReturned when operation has been rejected as it is happening too frequently.
Examplegenerated
exampleReturned when server encountered an error in processing API.
Examplegenerated
exampleReturned when service is unavailable temporarily.
Examplegenerated
exampleReturned when server timed out processing request.
Examplegenerated
example