You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@nifi.apache.org by christoffer <Ch...@uninett.no> on 2018/09/10 07:20:56 UTC

Monitoring expiration of flowfiles

What is the best method for monitoring expiration of flow files and obtain
statistics regarding how many flow files that are dropped? I can’t find a
suitable command for this purpose in the NiFi Rest Api. 



--
Sent from: http://apache-nifi-users-list.2361937.n4.nabble.com/

Re: Monitoring expiration of flowfiles

Posted by Pierre Villard <pi...@gmail.com>.
I definitely agree that it should be added in the connection statistics so
that you can get it through the SiteToSiteStatusReportingTask.
Would be useful and I can take a look at it. Let me know if you create a
JIRA for that or if you want to contribute it ;)

Pierre

Le mar. 11 sept. 2018 à 18:00, Sebastien Cognet <
sebastien.cognet@privitar.com> a écrit :

> Christoffer,
> Have seen good input on this topic in this blog:
> https://pierrevillard.com/
> Sebastien
>
> On Tue, 11 Sep 2018 at 17:24, Mark Payne <ma...@hotmail.com> wrote:
>
>> Christoffer,
>>
>> FlowFile expiration isn't really something that's available in the stats
>> currently.
>> There is an EXPIRE Provenance Event that is emitted whenever a FlowFile
>> gets expired, so you could make use of the
>> SiteToSiteProvenanceReportingTask,
>> if you wanted to, in order to glean this information, but it's not as
>> straight forward
>> as getting the info from the stats.
>>
>> That said, I do think it's a reasonable ask, so feel free to file a JIRA
>> to improve the stats
>> so that Connections provide this information in their stats history.
>>
>> Thanks
>> -Mark
>>
>>
>> > On Sep 10, 2018, at 3:20 AM, christoffer <
>> Christoffer.ottesen@uninett.no> wrote:
>> >
>> > What is the best method for monitoring expiration of flow files and
>> obtain
>> > statistics regarding how many flow files that are dropped? I can’t find
>> a
>> > suitable command for this purpose in the NiFi Rest Api.
>> >
>> >
>> >
>> > --
>> > Sent from: http://apache-nifi-users-list.2361937.n4.nabble.com/
>>
>>
>
> --
> Sebastien Cognet
> Senior Sales Engineer
> M: +33 6 08 52 77 22
> <https://www.linkedin.com/company/9200631/>
> <https://twitter.com/privitarglobal>
> <https://www.privitar.com/>Privitar | France
>
> This email is confidential, if you are not the intended recipient please
> delete it and notify us immediately by emailing the sender. You should not
> copy it or use it for any purpose nor disclose its contents to any other
> person. Privitar Limited is registered in England with registered number
> 09305666. Registered office Salisbury House, Station Road, Cambridge,
> CB12LA.

Re: Monitoring expiration of flowfiles

Posted by Sebastien Cognet <se...@privitar.com>.
Christoffer,
Have seen good input on this topic in this blog: https://pierrevillard.com/
Sebastien

On Tue, 11 Sep 2018 at 17:24, Mark Payne <ma...@hotmail.com> wrote:

> Christoffer,
>
> FlowFile expiration isn't really something that's available in the stats
> currently.
> There is an EXPIRE Provenance Event that is emitted whenever a FlowFile
> gets expired, so you could make use of the
> SiteToSiteProvenanceReportingTask,
> if you wanted to, in order to glean this information, but it's not as
> straight forward
> as getting the info from the stats.
>
> That said, I do think it's a reasonable ask, so feel free to file a JIRA
> to improve the stats
> so that Connections provide this information in their stats history.
>
> Thanks
> -Mark
>
>
> > On Sep 10, 2018, at 3:20 AM, christoffer <Ch...@uninett.no>
> wrote:
> >
> > What is the best method for monitoring expiration of flow files and
> obtain
> > statistics regarding how many flow files that are dropped? I can’t find a
> > suitable command for this purpose in the NiFi Rest Api.
> >
> >
> >
> > --
> > Sent from: http://apache-nifi-users-list.2361937.n4.nabble.com/
>
>

-- 
Sebastien Cognet
Senior Sales Engineer
M: +33 6 08 52 77 22
<https://www.linkedin.com/company/9200631/>
<https://twitter.com/privitarglobal>
<https://www.privitar.com/>Privitar | France

-- 
This email is confidential, if you are not the intended recipient please 
delete it and notify us immediately by emailing the sender. You should not 
copy it or use it for any purpose nor disclose its contents to any other 
person. Privitar Limited is registered in England with registered number 
09305666. Registered office Salisbury House, Station Road, Cambridge, 
CB12LA.

Re: Monitoring expiration of flowfiles

Posted by Mark Payne <ma...@hotmail.com>.
Christoffer,

FlowFile expiration isn't really something that's available in the stats currently.
There is an EXPIRE Provenance Event that is emitted whenever a FlowFile
gets expired, so you could make use of the SiteToSiteProvenanceReportingTask,
if you wanted to, in order to glean this information, but it's not as straight forward
as getting the info from the stats.

That said, I do think it's a reasonable ask, so feel free to file a JIRA to improve the stats
so that Connections provide this information in their stats history.

Thanks
-Mark


> On Sep 10, 2018, at 3:20 AM, christoffer <Ch...@uninett.no> wrote:
> 
> What is the best method for monitoring expiration of flow files and obtain
> statistics regarding how many flow files that are dropped? I can’t find a
> suitable command for this purpose in the NiFi Rest Api. 
> 
> 
> 
> --
> Sent from: http://apache-nifi-users-list.2361937.n4.nabble.com/