[
https://issues.apache.org/jira/browse/MINIFICPP-490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mr TheSegfault updated MINIFICPP-490:
-------------------------------------
Description:
Have building blocks defined so that we can easily chain functions to build out
a 'recipe'
Ideas:
1) Gather logs from device, transmit to nifi through site to site (highest need
)
1.a) Search logs for trigger keywords , transmit a flowfile with attributes
reflecting when/how that trigger occurred.
2) capture packets on a device, analyze statistics about packets, transmit to
nifi ( lower need )
a) Types of packets
b) Number of packets
c) Packets received over time ( effective speed )
( Attributes are bags of words )
3) Ability to perform numeric analysis ( counts, sum, mean, average, --
aggregating information from flow files, etc ) on attributes, transmitting
results to NiFi
Key: Packets received Value: 1 across a time span, you want to know
how many packets received
Returns single flow file with combined or aggregated information
* On vehicle, want to count the number of times speed exceeds 80 km/h –
only shipped once a day
4) Explore persisting ( FlowFiles and content ) when the capability exists and
the consumer of the API wants to
5) Gather in memory data from device, transmit to nifi through site to site
Exists as an API component to give users the ability to store data
already captured and ship with guarantees
was:
Have building blocks defined so that we can easily chain functions to build out
a 'recipe'
Ideas:
1) Gather logs from device, transmit to nifi through site to site
1.a) Search logs for trigger keywords , transmit a flowfile with attributes
reflecting when/how that trigger occurred.
2) capture packets on a device, analyze statistics about packets, transmit to
nifi
( Attributes are bags of words )
3) Ability to perform numeric analysis ( counts, sums, aggregation, etc ) on
attributes, transmitting results to NiFi
4) Explore persisting ( FlowFiles and content ) when the capability exists and
the consumer of the API wants to
5) Gather in memory data from device, transmit to nifi through site to site
> Create common recipes based on the C & C2 api
> ---------------------------------------------
>
> Key: MINIFICPP-490
> URL: https://issues.apache.org/jira/browse/MINIFICPP-490
> Project: NiFi MiNiFi C++
> Issue Type: Sub-task
> Reporter: Mr TheSegfault
> Priority: Major
> Labels: CAPI
>
> Have building blocks defined so that we can easily chain functions to build
> out a 'recipe'
> Ideas:
>
> 1) Gather logs from device, transmit to nifi through site to site (highest
> need )
> 1.a) Search logs for trigger keywords , transmit a flowfile with
> attributes reflecting when/how that trigger occurred.
> 2) capture packets on a device, analyze statistics about packets, transmit to
> nifi ( lower need )
> a) Types of packets
> b) Number of packets
> c) Packets received over time ( effective speed )
> ( Attributes are bags of words )
> 3) Ability to perform numeric analysis ( counts, sum, mean, average, --
> aggregating information from flow files, etc ) on attributes, transmitting
> results to NiFi
> Key: Packets received Value: 1 across a time span, you want to know
> how many packets received
> Returns single flow file with combined or aggregated information
> * On vehicle, want to count the number of times speed exceeds 80 km/h
> – only shipped once a day
> 4) Explore persisting ( FlowFiles and content ) when the capability exists
> and the consumer of the API wants to
> 5) Gather in memory data from device, transmit to nifi through site to site
> Exists as an API component to give users the ability to store data
> already captured and ship with guarantees
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
