Retrieve ADDoS Trends Baseline Segment timeseries statistics

post

http://127.0.0.1:8080/stats/timeseries/addos/trends/baselineSegment

Retrieves ADDoS Trends Baseline Segment timeseries statistics for a specific appliance. Returns flow metrics (concurrent, embryonic, flows/sec) used for DDoS baseline analysis within the specified time range and segment.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Query Params

startTime

int64

required

≥ 0

Start time boundary for data retrieval as Unix epoch timestamp in milliseconds. Must be >= 0 and less than endTime.

endTime

int64

required

≥ 0

End time boundary for data retrieval as Unix epoch timestamp in milliseconds. Must be >= 0 and greater than startTime.

segmentId

int32

required

Unique identifier of the network segment to filter statistics. Used to scope baseline data to a specific segment.

protocol

int32

enum

required

Protocol filter for traffic analysis. Valid values: 0 (All protocols), 1 (TCP), 2 (UDP), 4 (Others).

Allowed:

metric

int32

enum

required

Flow metric type for baseline measurement. Valid values: 0 (Concurrent flows), 1 (Embryonic flows), 2 (Flows per second), 3 (Embryonic Two-Way flows).

Allowed:

classification

int32

enum

required

Classification type for grouping statistics. Valid values: 1 (Zone-based classification), 2 (Source-based classification).

Allowed:

Body Params

Request body containing the appliance identifier to filter statistics.

Request body containing the appliance identifier.

nePk

string

required

^\d+\.NE$

Network Element Primary Key - unique appliance identifier assigned by Orchestrator. Format: '.NE'.

Responses

401

Unauthorized - Authentication required or invalid credentials.

403

Forbidden - Insufficient permissions. Requires READ or READ_WRITE role.

Language

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

200Successfully retrieved ADDoS baseline segment statistics. Returns column definitions and timeseries data arrays.

400Bad Request - Invalid or missing parameters.

503Service Unavailable - Server is busy processing other requests.