feat(sdk): create device records from plugins/integrations #922
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#922
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: #2620
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/2620
Original created: 2026-01-30T18:28:17Z
Is your feature request related to a problem?
We should devise a way that plugins/plugin authors, leveraging the Go or Rust serviceradar plugin SDKs, can easily create
Device Recordsin ServiceRadar. This would allow us to move our integration layer (armis, netbox, etc) to be just another WASM plugin and would make it easier for the community or users to develop integrations on their own.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 GitHub comment.
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/2620#issuecomment-3825101381
Original created: 2026-01-30T18:35:11Z
Not sure if we could still use this for 2-way integrations, where we need to make an SRQL query to get some data and then push it to a 3rd party API. For Armis, we pull devices, and we also come back and update the Armis API, enriching an Armis device record by updating a tag (based on an ICMP/TCP availability check done by SR, we update a tag in Armis indicating if the device is available or not)
Imported GitHub comment.
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/2620#issuecomment-3825142973
Original created: 2026-01-30T18:45:25Z
we could possibly make SRQL available via GRPC queries from agents, need to think more about security implications here/data leak potential/etc