> For the complete documentation index, see [llms.txt](https://docs.elastiflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elastiflow.com/trapcoll.md). # NetObserv SNMP Trap NetObserv SNMP Trap is more than a simple trap listener. It has been designed to meet the requirements of the most demanding production environments, with particular attention on the following attributes: #### Turnkey The Trap Input eliminates the need for extensive configuration and manual setup. It includes a comprehensive set of pre-configured trap definitions, making it easy to start capturing and processing SNMP traps from various devices. #### Extensible The Trap Input supports a wide range of network equipment out-of-the-box, and it is straightforward to add new trap definitions or modify existing ones to accommodate custom or rare devices. #### Efficient The Trap Input is optimized to handle high volumes of traps with minimal impact on system resources. It processes traps in real-time, ensuring timely and accurate data collection without overwhelming the network or the collector. #### Adaptive The Trap Input can dynamically adjust to changes in the network environment. It automatically updates its configuration in response to new devices or changes in existing devices, ensuring continuous and accurate trap collection. #### Scalable NetObserv SNMP Trap is built to scale with your network. It can handle a large number of traps from numerous devices, leveraging a pool of concurrent workers to ensure efficient processing and high availability. ### Enabling Trap Collection To enable the Trap Input, refer to the configuration reference [here](/trapcoll/configuration/receiving-traps/input_trap.md). Devices can be added as explained [here](/trapcoll/configuration/receiving-traps/devices.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.elastiflow.com/trapcoll.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.