feat: Set vendor field for devices in ocsf_devices table #792

Closed
opened 2026-03-28 04:28:35 +00:00 by mfreeman451 · 3 comments
Owner

Imported from GitHub.

Original GitHub issue: #2393
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/2393
Original created: 2026-01-20T03:03:04Z


Is your feature request related to a problem?

We should be able to probe the device and determine the vendor when we're doing our SNMP mapping/discovery process. Right now we don't populate the vendor column for any devices automatically/correctly in the ocsf_devices schema, this would be an easy way to do so for network devices.

https://github.com/wimark/vendormap

  • get/use sysDescr and other fields in discovery process or map OIDs to vendors, i think there is an OID vendor database somewhere maybe we could scrape / download that
  • look at OIDs
  • look at MACs
  • update serviceradar-agent to set vendor field for servers
  • update network mapper/discovery to set vendor for network devices
  • investigate way to set device vendor w/ devices discovered through integrations
  • investigate way to set device vendor w/ devices discovered through network sweep/scans (fingerprinting, what does that look like when you have 50k-1m+ devices, right now our TCP syn scanner is fast because it doesn't do 3-way handshakes)

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: #2393 Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/2393 Original created: 2026-01-20T03:03:04Z --- **Is your feature request related to a problem?** We should be able to probe the device and determine the vendor when we're doing our SNMP mapping/discovery process. Right now we don't populate the `vendor` column for any devices automatically/correctly in the `ocsf_devices` schema, this would be an easy way to do so for network devices. https://github.com/wimark/vendormap - [x] get/use sysDescr and other fields in discovery process or map OIDs to vendors, i think there is an OID vendor database somewhere maybe we could scrape / download that - [ ] look at OIDs - [ ] look at MACs - [ ] update serviceradar-agent to set vendor field for servers - [ ] update network mapper/discovery to set vendor for network devices - [ ] investigate way to set device vendor w/ devices discovered through integrations - [ ] investigate way to set device vendor w/ devices discovered through network sweep/scans (fingerprinting, what does that look like when you have 50k-1m+ devices, right now our TCP syn scanner is fast because it doesn't do 3-way handshakes) **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.
mfreeman451 added this to the 1.1.1 milestone 2026-03-28 04:28:35 +00:00
Author
Owner

Imported GitHub comment.

Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/2393#issuecomment-3780730508
Original created: 2026-01-21T19:19:14Z


recent changes are now surfacing vendor and model through the mapper/discovery system with ubiquiti devices.

Imported GitHub comment. Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/2393#issuecomment-3780730508 Original created: 2026-01-21T19:19:14Z --- recent changes are now surfacing `vendor` and `model` through the mapper/discovery system with ubiquiti devices.
Author
Owner

Imported GitHub comment.

Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/2393#issuecomment-3789872793
Original created: 2026-01-23T11:45:05Z


we're now setting the vendor but still lacking all of the other fields, moving this to milestone 1.1.1 for now

Imported GitHub comment. Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/2393#issuecomment-3789872793 Original created: 2026-01-23T11:45:05Z --- we're now setting the vendor but still lacking all of the other fields, moving this to milestone 1.1.1 for now
Author
Owner

Imported GitHub comment.

Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/2393#issuecomment-3978687175
Original created: 2026-03-01T00:17:42Z


closing, completed

Imported GitHub comment. Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/2393#issuecomment-3978687175 Original created: 2026-03-01T00:17:42Z --- closing, completed
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#792
No description provided.