SNMP Trap Agent
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 17
- Forks
- 20
- Avg merge
- 1h 22m
- Merged PRs (30d)
- 2
Description
After working with SNMP on the M1000 Agent, it has become evident that it might make sense to have a single SNMP Trap agent, meant to catch all SNMP traps, rather than introduce trap functionality to each Agent that uses SNMP to interface with a piece of hardware. This might eventually make sense to move upstream to the ocs repo as a core OCS Agent, but let's start here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests. Start by reviewing the existing M1000 Agent and the repository's agent conventions, then clarify the trap collection, configuration, and placement scope before implementation. Done should be a defined single SNMP Trap agent with agreed tests and documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100