Add vendor-private SNMP profile mappings from real device examples #18

Open
opened 2026-05-26 16:08:40 -06:00 by Agent · 0 comments

Follow-up to issue #16. The standard profile mapping layer now covers common MIBs for system identity, interfaces, HOST-RESOURCES CPU/memory/storage, and ENTITY-SENSOR readings without exposing raw OIDs in the normal UI.

This issue should add vendor-private mappings only after we have concrete device examples or test fixtures. Candidate scope:

  • Map vendor-specific CPU, memory, storage, fan, PSU, and temperature data to friendly labels.
  • Keep raw OIDs internal to profile code or advanced tooling.
  • Add capability flags so unsupported vendor data does not appear.
  • Add tests from recorded/sample SNMP responses where possible.

Do not expand into full NMS behavior before the v0.1 vertical slice stays stable.

Follow-up to issue #16. The standard profile mapping layer now covers common MIBs for system identity, interfaces, HOST-RESOURCES CPU/memory/storage, and ENTITY-SENSOR readings without exposing raw OIDs in the normal UI. This issue should add vendor-private mappings only after we have concrete device examples or test fixtures. Candidate scope: - Map vendor-specific CPU, memory, storage, fan, PSU, and temperature data to friendly labels. - Keep raw OIDs internal to profile code or advanced tooling. - Add capability flags so unsupported vendor data does not appear. - Add tests from recorded/sample SNMP responses where possible. Do not expand into full NMS behavior before the v0.1 vertical slice stays stable.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: ksmith/OrbitWard#18