feat: snmp/discovery #741

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

Imported from GitHub.

Original GitHub issue: #2291
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/2291
Original created: 2026-01-14T08:27:39Z


Is your feature request related to a problem?

When configuring SNMP polling on a switch/router for a given interface, we currently assume that the operator already knows the OID and OID type before hand and would be able to supply that to create a working configuration. In other words, you have to know everything and basically manually collect that information, go into the ServiceRadar SNMP poller settings UI or wherever you are going to go to configure these settings.. We need to first figure out the flow here for how we're going to easily let a user setup SNMP metrics collection.

  • User adds a network device
  • User elects to configure SNMP metrics collection on device by choosing a device from the device UI and configuring ad-hoc per-device SNMP settings
  • User creates profiles in settings UI using SRQL queries to come up with the target group of devices with pre-configured SNMP metrics polling settings, one could envision a profile for all Cisco Routers, or all Cisco Routers in EMEA, or all Aruba Switches in APAC
  • Each profile would use a different set of SNMP credentials, stored with AshCloak (encrypted at rest)
  • During Profile creation, Operators can choose the schedule
  • Need to re-use the same UI to set all this up for a group of devices, or just one device if a user is 'Editing' a device
  • #2292

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: #2291 Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/2291 Original created: 2026-01-14T08:27:39Z --- **Is your feature request related to a problem?** When configuring SNMP polling on a switch/router for a given interface, we currently assume that the operator already knows the OID and OID type before hand and would be able to supply that to create a working configuration. In other words, you have to know everything and basically manually collect that information, go into the ServiceRadar SNMP poller settings UI or wherever you are going to go to configure these settings.. We need to first figure out the flow here for how we're going to easily let a user setup SNMP metrics collection. - [x] User adds a network device - [x] User elects to configure SNMP metrics collection on device by choosing a device from the device UI and configuring ad-hoc per-device SNMP settings - [ ] User creates profiles in settings UI using SRQL queries to come up with the target group of devices with pre-configured SNMP metrics polling settings, one could envision a profile for all Cisco Routers, or all Cisco Routers in EMEA, or all Aruba Switches in APAC - [x] Each profile would use a different set of SNMP credentials, stored with AshCloak (encrypted at rest) - [x] During Profile creation, Operators can choose the schedule - [x] Need to re-use the same UI to set all this up for a group of devices, or just one device if a user is 'Editing' a device - [x] #2292 **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.0 milestone 2026-03-28 04:28:01 +00:00
Author
Owner

Imported GitHub comment.

Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/2291#issuecomment-3792904038
Original created: 2026-01-23T22:45:12Z


closing as completed

Imported GitHub comment. Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/2291#issuecomment-3792904038 Original created: 2026-01-23T22:45:12Z --- closing as 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#741
No description provided.