[jira] [Commented] (NIFI-987) Add Processor for Writing Events to Riemann

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962670#comment-14962670 ] 

ASF GitHub Bot commented on NIFI-987:
-------------------------------------

Github user joewitt commented on the pull request:

    https://github.com/apache/nifi/pull/91#issuecomment-149060879
  
    Ricky,
    
    Sorry for the delay in providing feedback.  Can you look into why the branch has conflicts?  Perhaps I'm misunderstanding what I'm seeing from github.  Also, the PR doesn't appear to address the necessary changes to the nifi-assembly/NOTICE and provide one for the nar itself so that we ensure the EPL 1.0 dependency is properly annotated.  I haven't checked what dependencies it pulls in yet but wanted to put that out there first.
    
    Thanks
    Joe


> Add Processor for Writing Events to Riemann
> -------------------------------------------
>
>                 Key: NIFI-987
>                 URL: https://issues.apache.org/jira/browse/NIFI-987
>             Project: Apache NiFi
>          Issue Type: New Feature
>            Reporter: Ricky Saltzer
>            Assignee: Ricky Saltzer
>         Attachments: Sample Riemann Dataflow .png
>
>
> Riemann (http://riemann.io) is a new framework for monitoring distributed systems. It's particular useful for sending ad-hoc events such as, heartbeats and metrics. It would be nice if NiFi had a PutRiemann processor for writing events using the NiFi expression language.
> A simple use case would be a data flow that repeatedly checks specific services over TCP, HTTP, etc and checks into Riemann. Another example would be detecting a blip in events coming down a stream using a simple event heartbeat mechanism. I'll post a couple visuals to help make these examples more concrete.
> I have an initial PutRiemann processor made. I will post the patch via a Github pull request later today.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)