feat(rperf): integrate rperf with device registry #484

Closed
opened 2026-03-28 04:24:58 +00:00 by mfreeman451 · 1 comment
Owner

Imported from GitHub.

Original GitHub issue: #1442
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/1442
Original created: 2025-08-03T06:02:31Z


rperf servers and rperf clients should be identifed as devices by the core/device registry, right now they are associated by the old poller heirarchy/ownership system.

Imported from GitHub. Original GitHub issue: #1442 Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/1442 Original created: 2025-08-03T06:02:31Z --- rperf servers and rperf clients should be identifed as devices by the core/device registry, right now they are associated by the old poller heirarchy/ownership system.
Author
Owner

Imported GitHub comment.

Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/1442#issuecomment-3813957555
Original created: 2026-01-28T21:12:04Z


closing, stale

Imported GitHub comment. Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/1442#issuecomment-3813957555 Original created: 2026-01-28T21:12:04Z --- closing, stale
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
carverauto/serviceradar#484
No description provided.