bug(sync): not picking up correct sweep.json in demo namespace #655

Closed
opened 2026-03-28 04:27:06 +00:00 by mfreeman451 · 0 comments
Owner

Imported from GitHub.

Original GitHub issue: #2016
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/2016
Original created: 2025-11-25T00:03:33Z


the sweep.json should be generated through integration with serviceradar-sync where it talks to armis (through the faker service, faker emulating armis API) and is configured to generate 50k fake devices. It is supposed to create a new 'sweep.json' that actually lives as an objectstore blob and is referenced in the nats-kv, so the agent basically reads all of that information from the KV instead of the config. This doesn't appear to be happening, I dont see any of the devices generated from the faker service in the inventory, instead we're seeing devices presumably created from the other default sweep.json which I believe have some /16's configured in it or something else for the scan. the agent responds to requests from the poller for the results of the scan and they get sent to the core for processing/running through the device registry. Also the UI is only showing that there are 2 devices total in the stats card in the devices page or the analytics stats cards on the analytics page, even though there are quite a few in the device table list.

Imported from GitHub. Original GitHub issue: #2016 Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/2016 Original created: 2025-11-25T00:03:33Z --- the sweep.json should be generated through integration with serviceradar-sync where it talks to armis (through the faker service, faker emulating armis API) and is configured to generate 50k fake devices. It is supposed to create a new 'sweep.json' that actually lives as an objectstore blob and is referenced in the nats-kv, so the agent basically reads all of that information from the KV instead of the config. This doesn't appear to be happening, I dont see any of the devices generated from the faker service in the inventory, instead we're seeing devices presumably created from the other default sweep.json which I believe have some /16's configured in it or something else for the scan. the agent responds to requests from the poller for the results of the scan and they get sent to the core for processing/running through the device registry. Also the UI is only showing that there are 2 devices total in the stats card in the devices page or the analytics stats cards on the analytics page, even though there are quite a few in the device table list.
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#655
No description provided.