esend7881 commented on PR #5088: URL: https://github.com/apache/nifi/pull/5088#issuecomment-1090499587
> @esend7881 - I think there is a confusion here. > > * GetSNMP/SetSNMP processors are meant to be used for interacting with an external SNMP server to retrieve/set values for given OIDs. > * ListenSNMPTrap does not connect to anything. It's starting a listener on the NiFi node so that external systems can send SNMP traps to the NiFi node. NiFi is playing the role of an SNMP server in some ways. > > There is no way to specify the host for ListenSNMPTrap simply because it's a listener processor. It's just like ListenHTTP or ListenTCP processors. @pvillard31 - I follow the logic. My understanding of SNMP Traps is they are UDP based notifications that come from an SNMP Agent. The listener is whoever is attached to the `host:port` that the SNMP Agent broadcasts to. I already have the SNMP Agent (separate application) which broadcasts traps when a change notification happens. I have been experimenting with [Apache Camel's SNMP trap listener](https://camel.apache.org/components/3.15.x/snmp-component.html) and it picks up those events. But, we are more interested in using Apache NiFi over Camel because of GUI based configuration. A couple follow up questions- - Do you know if anyone has a fleshed out example of using ListenSNMPTrap, including that middle-ware receiver that gets the actual trap events and flows the data into NiFi via ListenSNMPTrap? - Is there any thought one how NiFi itself could listen to those broadcasted TRAP events from the SNMP Agent, without any middle-ware? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
