What it is for

Omni-Testing is the stress-testing part of 1sc Observability. It answers one question: does this core carry the load you need? It starts simulated UEs, sends traffic through the core, and reports passed, failed, incomplete, or not evaluated with the measured evidence. High-volume traffic is the first test type.

  • Size a deployment before a pilot.
  • Find the UE count where throughput or packet loss breaks.
  • Compare a core release with the previous release.
  • Confirm that an instance size meets your bounds.

Start a traffic run

  • Sign in to 1sc.dev and open Dashboard → Observability → Omni-Testing.
  • Set the UE count, the duration, and the rate per UE.
  • Optionally set pass conditions: minimum aggregate Mbit/s, maximum loss, and maximum RTT p95.
  • Optionally set a load host instance. Leave it empty to send traffic from the core host.
  • Click Start traffic run. The tab shows progress and adds a row when the run finishes.
terminal
curl -X POST https://www.1sc.dev/api/deployments/<deployment-id>/traffic-run \
  -H "Authorization: Bearer $ONE_SC_API_TOKEN" -H "content-type: application/json" \
  -d '{"confirmTrafficRun":true,"ueCount":16,"durationSeconds":120,"bitratePerUe":"2M","sla":{"minAggregateMbps":15,"maxLossPercent":1}}'

GET on the same path returns the progress of the current run and the newest 20 runs. The capability id is deployment.traffic_run.start, and it requires the radio-attach:run scope.

Read the result

ResultMeaning
PassedEvery pass condition held and the measurement quality is complete.
FailedA measured value broke a pass condition.
IncompleteEvidence is missing, or the load host was saturated, so the core cannot be judged.
Not evaluatedThe run declared no pass conditions.

Search commands, workflows, configuration, attach, API, and reports.