Yes I will also consider a listener and a sender for SNMP traps.

2016-02-18 22:17 GMT+01:00 Simon Ball <[email protected]>:

> Have you considered a trap listener, that would make a nice addition to
> the bundle.
>
> Simon
>
> -
> Simon Elliston Ball
> Product Solutions Architect
> Hortonworks - Powering the future of data
>
>
> On 18 Feb 2016, at 20:29, Pierre Villard <[email protected]
> <mailto:[email protected]>> wrote:
>
> I created a JIRA (https://issues.apache.org/jira/browse/NIFI-1537). Will
> work on it soon.
>
> 2016-02-18 21:07 GMT+01:00 Pierre Villard <[email protected]
> <mailto:[email protected]>>:
>
> Hi Joe,
>
> I do see use cases where interactions with SNMP could be useful. I
> preferred to ask because, to be honest, I am going to join the French team
> at Hortonworks in about 2 months, and I am eager to collaborate in a useful
> manner. Well... at least I'll do my best! So if there are improvements I
> may be able to implement, I'd be happy to spend some of my spare time on
> it!
>
> Pierre
>
> 2016-02-18 19:56 GMT+01:00 Joe Witt <[email protected]<mailto:
> [email protected]>>:
>
> Pierre,
>
> In my view the best and first test of interest is your own.  If you
> see that you could use it then there is a good shot others will as
> well.  I think interaction with SNMP makes sense and look forward to
> checking it out if you do find time to contribute that.
>
> Thanks
> Joe
>
> On Thu, Feb 18, 2016 at 1:29 PM, Pierre Villard
> <[email protected]<mailto:[email protected]>> wrote:
> Hi,
>
> Would that be of any interest to have processors for SNMP exchanges
> using
> snmp4j?
>
> I was thinking about something like:
>
> GetSNMP
> possibility to do a SNMP get or a SNMP walk, the flow file would not
> have
> any content, just attributes with key = requested oid and value =
> requested
> value.
>
> SetSNMP
> do a SNMP set according to flow file / processor properties. There are
> multiple options there, don't know what sounds best.
>
> If you think it could be useful, I will have a look developing that.
>
> Pierre
>
>
>
>

Reply via email to