[
https://issues.apache.org/jira/browse/MINIFI-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16158863#comment-16158863
]
ASF GitHub Bot commented on MINIFI-339:
---------------------------------------
Github user phrocker commented on the issue:
https://github.com/apache/nifi-minifi-cpp/pull/134
@achristianson MiNiFi adheres to a protocol defined by Garcon. I think we
should add documentation to the c2 server or Apache wiki ( or both ? ) and link
to it from here. In the interest of getting something here, which was a point
discussed yesterday, I'll add an item on the apache docs and reference them
from here. I plan to follow that up with an E-mail the dev list asking for
input from the larger group as a whole. The same will follow suit for other
protocol implementations. Does that make sense to you or do you feel we should
put that documentation here? Thanks!
> Begin building controlling API to facilitate control of agents
> --------------------------------------------------------------
>
> Key: MINIFI-339
> URL: https://issues.apache.org/jira/browse/MINIFI-339
> Project: Apache NiFi MiNiFi
> Issue Type: New Feature
> Components: C++
> Reporter: marco polo
> Assignee: marco polo
> Priority: Critical
> Labels: Durability, Reliability, Statistics
>
> Begin building the controlling API in MiNiFi C++. This API will evolve and
> likely have public and private elements. As development progresses we may
> want more capabilities.
> What I want to create as a straw man will be basic control and metrics
> gathering
> -- Start
> -- Stop
> -- Pause
> -- Gather metrics
> ** Throughput of of flow components
> ** Execution time ( run time minus sleep time )
> ** Memory consumption
> -- Drain repositories
> -- Switch repository types.
> Better employ update listener within this controlling API
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
