ksmith/OrbitWard
1
0
Fork 0
Code Issues 12 Pull Requests Actions Packages Projects Releases Wiki Activity

Add SNMP interface status and traffic collection #15

New Issue
Closed
opened 2026-05-23 15:46:01 -06:00 by Agent · 0 comments
Agent commented 2026-05-23 15:46:01 -06:00
Copy Link
Copy Source

Implemented in fe7157f.

Summary:

  • Worker now includes snmp monitors in the scheduled collection loop.
  • Added an SNMPv2c worker collector for configured discovery selections.
  • SNMP collection loads saved credential profiles server-side and decrypts the community string only for the collection request.
  • Device uptime monitors update status and write uptime metrics.
  • Interface status monitors update status from admin/oper state and write friendly status metrics.
  • Interface traffic monitors collect inbound/outbound octet counters and write metrics.
  • Interface error monitors collect inbound/outbound errors and discards and write metrics.
  • Restarted the local worker and confirmed SNMP monitors were actively checked in logs.

Verified:

  • docker compose -f docker-compose.dev.yml exec -T worker python -m unittest discover -s tests
  • docker compose -f docker-compose.dev.yml exec -T worker python -m compileall app
  • docker compose -f docker-compose.dev.yml exec -T backend python -m pytest tests
Implemented in fe7157f. Summary: - Worker now includes `snmp` monitors in the scheduled collection loop. - Added an SNMPv2c worker collector for configured discovery selections. - SNMP collection loads saved credential profiles server-side and decrypts the community string only for the collection request. - Device uptime monitors update status and write uptime metrics. - Interface status monitors update status from admin/oper state and write friendly status metrics. - Interface traffic monitors collect inbound/outbound octet counters and write metrics. - Interface error monitors collect inbound/outbound errors and discards and write metrics. - Restarted the local worker and confirmed SNMP monitors were actively checked in logs. Verified: - docker compose -f docker-compose.dev.yml exec -T worker python -m unittest discover -s tests - docker compose -f docker-compose.dev.yml exec -T worker python -m compileall app - docker compose -f docker-compose.dev.yml exec -T backend python -m pytest tests
Agent closed this issue 2026-05-24 00:44:17 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
ksmith
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: ksmith/OrbitWard#15
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?