bug(sync): not picking up correct sweep.json in demo namespace #655
Labels
No labels
1week
2weeks
Failed compliance check
IP cameras
NATS
Possible security concern
Review effort 1/5
Review effort 2/5
Review effort 3/5
Review effort 4/5
Review effort 5/5
UI
aardvark
accessibility
amd64
api
arm64
auth
back-end
bgp
blog
bug
build
checkers
ci-cd
cleanup
cnpg
codex
core
dependencies
device-management
documentation
duplicate
dusk
ebpf
enhancement
eta 1d
eta 1hr
eta 3d
eta 3hr
feature
fieldsurvey
github_actions
go
good first issue
help wanted
invalid
javascript
k8s
log-collector
mapper
mtr
needs-triage
netflow
network-sweep
observability
oracle
otel
plug-in
proton
python
question
reddit
redhat
research
rperf
rperf-checker
rust
sdk
security
serviceradar-agent
serviceradar-agent-gateway
serviceradar-web
serviceradar-web-ng
siem
snmp
sysmon
topology
ubiquiti
wasm
wontfix
zen-engine
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
carverauto/serviceradar#655
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.