Targets
The hosts registered for your organisation, and how each did recently.
Reached from: Sidebar, Test journey, stage 1
1 page
- One target
Product guide
Where each part of DDoSphere lives and when you use it.
Getting started
Loading Getting started. This is taking longer than usual. The server has not answered yet. No answer after 20 seconds.
Getting started
Test journey
Plans
Saved plans: what traffic to send, from where, for how long.
Reached from: Sidebar, Test journey, stage 2; the Plan a run button beside it
4 pages
- Plan a run
- One plan
- Edit plan
- Review and launch
Runs
Every run and how it ended, with its timeline, map and log.
Reached from: Sidebar, Test journey, stage 3
8 pages
- Run insights
- Compare runs
- One run
- Timeline
- Map
- Log and notes
- Evidence report
- Wall display
Reports
The evidence report of each finished run, ready to hand over.
Reached from: Sidebar, Test journey, stage 4
Workspace
Scheduled tests
Plans set to run on their own, once or on a repeat, in UTC.
Reached from: Sidebar, Workspace
2 pages
- Schedule a plan
- Edit scheduled test
Generators
Where the load comes from, and the source addresses to allowlist.
Reached from: Sidebar, Workspace
Audit log
Who created and last changed each record.
Reached from: Sidebar, Workspace
Settings
The organisation name, the team, the plan and usage, and labels.
Reached from: Sidebar, Workspace
4 pages
- Organisation
- Team
- Plan and usage
- Labels
Help and account
Notifications
Run results and account notices sent to you.
Reached from: Top bar, the Notifications bell
Your account
Your details, password and notification preferences.
Reached from: Top bar, the Account menu
2 pages
- Change password
- Notification preferences
Contact support
A message to DDoSphere staff. We reply by email.
Reached from: Top bar, the Help menu, and every error page; Product guide
Words used in DDoSphere
Words used in DDoSphere
Terms
- Run
- One execution of a plan against a target.
- Plan
- Saved steps, generator regions and pacing.
- Step
- One part of a plan, with its own traffic and duration.
- Target
- A host DDoSphere staff registered for your organisation.
- Generator
- A machine that sends the test traffic; its location is a region.
- Evidence report
- The document to hand over after a run.
- Not measured
- No reading was taken. It is never shown as zero.
- demo only
- Sample data for a reading that has no connected source yet.
Readings on the screens
- Request raterps
- Requests per second the generators sent toward the target. Technical term: Offered rate
- Requests sentrequests
- Requests the generators sent in the window.
- Responses receivedrequests
- Responses the generators received back from the target. Technical term: Responses received (generator-observed)
- Bandwidth sentbps
- Bits per second the generators sent toward the target.
- Response timems
- Time the target took to answer, as seen by the generators.
- First down event
- The first time a health monitor reported the target as down.
- Resilience rating
- The backend's resilience score, grouped as Strong, Partial or Weak. Technical term: Resilience band
- Verdict
- How the target held up: Held, Degrading or Target down.
- Traffic to your serverrps
- Requests per second that passed the protection layer and reached the origin. Technical term: Leaked to origin
- Blocked by protectionrps
- Requests per second the protection layer blocked.
- Customer actions completed%
- Share of the business probe's scripted purchases that completed during the run. Technical term: Business probe success
- Time for protection to reacts
- Seconds from the start of the load until the protection layer acted. Technical term: Time to mitigate