You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Aldrin Piri (JIRA)" <ji...@apache.org> on 2016/10/05 13:43:20 UTC

[jira] [Resolved] (MINIFI-92) Create ExecuteProcess processor for NiFi-MiNiFi-cpp

     [ https://issues.apache.org/jira/browse/MINIFI-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aldrin Piri resolved MINIFI-92.
-------------------------------
       Resolution: Duplicate
    Fix Version/s: 0.1.0

> Create ExecuteProcess processor for NiFi-MiNiFi-cpp
> ---------------------------------------------------
>
>                 Key: MINIFI-92
>                 URL: https://issues.apache.org/jira/browse/MINIFI-92
>             Project: Apache NiFi MiNiFi
>          Issue Type: Bug
>          Components: C++, Core Framework
>            Reporter: Randy Gelhausen
>              Labels: C++, cpp, nifi-minifi-cpp
>             Fix For: 0.1.0
>
>
> Instrumenting application servers/devices with (Mi)NiFi agents gives ops teams the ability to add arbitrary system check and metrics.
> NiFi proper's ExecuteProcess lets you use the wide variety of existing Linux tools and data gatherers, but MiNiFi-cpp lacks this today. Thus servers/containers need to be configured during build time (for example: https://github.com/randerzander/TechOps/blob/master/containers/base/scripts/nmon.sh), which is tedious and error prone compared to being able to have the MiNiFi agent invoke processes at will.
> ExecuteProcess in MiNiFi-cpp would significantly improve the value of the agent for server/container instrumentation.



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