Statistics

Statistics retrieves statistics from the F5 Distributed Cloud API across resource types. The current HTTP deployment demonstrates access logs, load balancer and origin metrics, application health, API activity, and security telemetry. Use the Statistics APIs reference to find queries for every resource group. Choose a resource guide, then set up cURL below before running its query.

Question	Guide	What you can learn
How much traffic arrived?	Load balancer metrics	Request rate, throughput, ingress/egress, requests to origin, and client/server round-trip time (RTT)
Which requests failed?	HTTP access logs	Response codes, classes, and methods from a first page or a complete paginated window
Is the origin slow?	Origin performance	Rates, errors, latency, throughput, server RTT, and transfer time on the matched origin node and edge
Is the application healthy?	Application health	Calculated graph health scores with their returned timestamps
Which APIs are busiest?	API activity	Calls by response class, top active endpoints, and discovery inventory
Did the web application firewall (WAF) act?	WAF metrics and security events	Measured counters and authoritative block events

Set up cURL

Use Bash, cURL 7.76 or later, and jq 1.7 or later. Obtain an F5 Distributed Cloud API token with read access to the selected namespace. Tenant-wide system queries need separate access and are outside this guide.

Examples start with illustrative defaults. Customize the form above with your environment values, then copy this complete setup into a Bash session. Leave the token field empty to use your existing $XCSH_API_TOKEN, or enter a token for inline commands. Keep credentials in the environment and private browser session. Static Markdown shows sanitized templates.

export XCSH_API_URL='<XCSH_API_URL>'
export XCSH_API_TOKEN="<XCSH_API_TOKEN>"
: "${XCSH_API_TOKEN:?Set XCSH_API_TOKEN in your shell or enter a token in Customize examples}"
export XCSH_NAMESPACE='<XCSH_NAMESPACE>'
export XCSH_LB_NAME='<XCSH_LB_NAME>'
export XCSH_DOMAINNAME='<XCSH_DOMAINNAME>'
set -euo pipefail
umask 077
export XCSH_END_TIME="$(date -u +%s)"
export XCSH_START_TIME="$((XCSH_END_TIME - 7200))"
export XCSH_START_24H="$((XCSH_END_TIME - 86400))"
test "$XCSH_START_24H" -lt "$XCSH_START_TIME"
test "$XCSH_START_TIME" -lt "$XCSH_END_TIME"

Discover the shared identifiers once in this session, then run your selected query. Origin performance includes its own origin discovery. Query reference also covers time-window refresh and response conventions.

Running demo

The existing demo owns a namespace, a blocking WAF, API discovery, and an HTTPS load balancer at its configured hostname. Its dedicated Azure origin serves health and HTTP API routes. The running generator sends three marked requests each minute and one WAF probe every fifth minute. Query this deployment directly; no persistent metrics collector is needed.

Demo readiness checks the deployment. HTTP access logs includes an optional bounded sequence for known response codes, and Load balancer metrics preserves its measured rollup comparison. Use troubleshooting for authentication, identity, and delay problems. Statistics APIs separates currently empty HTTP metrics from families requiring future resources.

For infrastructure ownership, pinned resources, local state, plan/apply, and teardown, use the Terraform reference. A running deployment needs no infrastructure change to follow these queries.