feat: bandwidth tracker (rperf) updates #825

New issue

Open

opened 2026-03-28 04:28:56 +00:00 by mfreeman451 · 0 comments

mfreeman451 commented

2026-03-28 04:28:56 +00:00

Owner

Imported from GitHub.

Original GitHub issue: #2442
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/2442
Original created: 2026-01-22T06:52:46Z

Is your feature request related to a problem?

Need to update rperf so it accepts the --enroll and --token parameters for edge onboarding
Update UI for easier deployment/configuration of rperf
bandwidth tracker card becomes clickable
bandwidth tracker details page, includes link to rperf settings page
link/info on easily deploying rperf reflectors on bandwidth tracker page
add public (serviceradar cloud) rperf reflectors (servers)

Not sure if our current rperf client can handle multiple targets or not, need to check that out.

Describe the solution you'd like

A clear and concise description of what you want to happen.

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

Additional context

Add any other context or screenshots about the feature request here.

Imported from GitHub. Original GitHub issue: #2442 Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/2442 Original created: 2026-01-22T06:52:46Z --- **Is your feature request related to a problem?** - [ ] Need to update `rperf` so it accepts the --enroll and --token parameters for edge onboarding - [ ] Update UI for easier deployment/configuration of rperf - [ ] bandwidth tracker card becomes clickable - [ ] bandwidth tracker details page, includes link to rperf settings page - [ ] link/info on easily deploying rperf reflectors on bandwidth tracker page - [ ] add public (serviceradar cloud) rperf reflectors (servers) Not sure if our current rperf client can handle multiple targets or not, need to check that out. **Describe the solution you'd like** A clear and concise description of what you want to happen. **Describe alternatives you've considered** A clear and concise description of any alternative solutions or features you've considered. **Additional context** Add any other context or screenshots about the feature request here.