HomeGuidesAPI Reference
API Reference

Retrieve real-time tunnel stats, flow stats, packet drop stats (with reason codes), DSCP stats, traffic class stats, shaper stats, and interface stats from an EdgeConnect appliance for monitoring scripts and alerting

Real-time monitoring API for tunnel bandwidth, TCP/UDP flow counts, packet drops, QoS shaper metrics, DSCP traffic, traffic class throughput, and interface bandwidth. Poll faster than every 3 seconds to avoid data gaps.

Common Use Cases:

  • Build monitoring scripts that poll this API at configurable polling intervals
  • Set up threshold-based alerting when packet drops exceed a defined threshold
  • Track packet drop reason codes to identify specific network issues
  • Monitor consecutive polling intervals to trigger alerts on persistent problems
  • Create real-time dashboards with input parameters for EdgeConnect appliance metrics

Statistics Types:

TypenamefilterDescription
tunneltunnel name, 'pass-through', or 'pass-through-unshaped'not usedReturns per-tunnel tx/rx bytes, packets, and MOS scores for voice quality monitoring on overlay tunnels.
trafficType'0' (optimized) or '3' (all-traffic)not usedReturns aggregate bandwidth metrics across all optimized WAN-accelerated traffic or all traffic types combined.
dscp'0' to '63'requiredReturns per-DSCP marking statistics to monitor QoS policy effectiveness and traffic classification by differentiated services code point.
trafficClass'0' to '9'requiredReturns per-traffic-class throughput and packet counts to verify business intent traffic prioritization (class 0 is highest priority).
flow'0' (TCP accel), '1' (TCP unaccel), '2' (non-TCP)required (use '3' for all traffic)Returns flow metrics: CREATED (flows created/sec), DELETED (flows deleted/sec), EXISTING (active flows), MAX (peak flows), plus byte/packet counters.
shaper'0' to '9' (traffic class)0=outbound, 1=inboundReturns QoS shaper queue depth, throughput, and shaped traffic metrics per traffic class for outbound or inbound direction.
drops'' (empty string)not usedReturns packet drop counters with reason codes to identify congestion, policy drops, or interface errors across the appliance.
interfaceinterface name (e.g., 'wan0')requiredReturns per-interface tx/rx bytes, packets, and error counters for physical and logical interfaces like wan0, lan0, or bvi0.

Internal Drop Reason Codes (for type=drops):

The response keys are numeric reason codes (1-399). The complete code-to-description mapping is available in the x-drop-reason-codes extension on the RealTimeStatsResponse schema. Common categories include:

Code RangeCategory
1-27LAN Rx/Tx errors (pass-through, packet length, tunnel, policy, checksum, queue full, buffer)
28-57WAN Rx/Tx errors (tunnel, TPH, frame, queue full, checksum, flow state, SYN, buffer)
58-77NAT, MTU, FEC, fragmentation errors
78-88QoS drops (packet expired, tunnel down, bad flow, enqueue full - egress/ingress)
89-101Packet/stream encode/decode/transform errors
102-113FRED/FMST flow errors
114-135IPsec and TCP errors
136-140ZCI and kernel errors
141-165License, control packets, NAT, overlay errors
166-177Routing errors (no route, TTL, bridge, VXLAN, FEC framing)
178-189QoS flow errors, security policy drops
190-213ICMP, tunnel, bridge port, VRF errors
214-260Local packet errors, hash collisions, multicast, WTX encap
261-293Zone/VRF, IDS/IPS, segmentation, IPSec queue errors
294-339ZCI internal errors, datapath overflow, FPOC fragment errors
340-399FPOC cleanup, DDOS, VXLAN, tracert, OTO, IDS inline, bridge/switch errors

To get the live code mapping from a specific appliance, call stats/drops/meta/info via the appliance proxy API.

Filter Values (string): '0'=optimized_traffic, '1'=pass_through_shaped, '2'=pass_through_unshaped, '3'=all_traffic

Response Format: {'metric': [[timestamp, value], ...]} with up to 3 data points.

Authorization: READ or READ_WRITE role.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Query Params
string
required
^\d+\.NE$

Network Element Primary Key - unique appliance identifier assigned by Orchestrator. Format: '.NE' (e.g., '0.NE', '10.NE').

Body Params

Specifies which real-time statistic category and metric to retrieve from the appliance.

Request body specifying which real-time statistic to retrieve. The 'type' determines which metric category, 'name' identifies the specific resource, and 'filter' (when required) specifies traffic type or direction.

string
enum
required

Statistics category. Determines valid 'name' and 'filter' values. Note: 'app' type removed in Orchestrator 9.3.0.

string
required

Resource identifier. Value interpretation depends on 'type'.

string
enum
Defaults to 0

Traffic type filter or direction (string). Required for: dscp, trafficClass, flow, interface. For shaper: direction filter. Ignored for: tunnel, trafficType, drops.

Allowed:
Responses

Language
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json