nifi-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Gilman <matt.c.gil...@gmail.com>
Subject Re: Nifi connection queue monitoring.
Date Tue, 03 Nov 2015 18:33:42 GMT
Phil,

Yes, everything performed in the UI is done through the REST API. Check out
the developer tools in your browser to see the requests/responses in
action. Thanks!

Matt

On Tue, Nov 3, 2015 at 2:21 AM, <philippe.gibert@orange.com> wrote:

> Hello
>
> I would like to know if a basic or complex  nifi workflow of processors
> can be built  just with REST API calls ie by-passing  the GUI.
>
> More generally if the functional perimeter offered by REST API calls
> covers the same perimeter than the one offered by the GUI ?
>
>
>
> Phil
>
> Thanks
>
>
>
> *De :* Chakrader Dewaragatla [mailto:Chakrader.Dewaragatla@lifelock.com]
> *Envoyé :* mardi 3 novembre 2015 01:13
> *À :* users@nifi.apache.org
> *Objet :* Re: Nifi connection queue monitoring.
>
>
>
> Thanks Matt, this should help us find the stats.
>
>
>
> Thanks,
>
> -Chakri
>
>
>
> *From: *Matt Gilman <matt.c.gilman@gmail.com>
> *Reply-To: *"users@nifi.apache.org" <users@nifi.apache.org>
> *Date: *Monday, November 2, 2015 at 4:39 PM
> *To: *"users@nifi.apache.org" <users@nifi.apache.org>
> *Subject: *Re: Nifi connection queue monitoring.
>
>
>
> Chakri,
>
>
>
> The configuration and the status are decoupled from one another so we
> don't need to pull back the entire configuration when a user wants to
> refresh the statistics frequently. Currently, the only endpoint available
> for retrieving status is based on a Process Group. That end point is
>
>
>
>
> https://{host}:{port}/nifi-api/controller/process-groups/{process-group-id}/status?recursive={true|false}
>
>
>
> If you want to get the status of every component, you can use the alias
> "root" for the top most process group id and set recursive to TRUE. If you
> want a specific connection, you can use the process group id of the Process
> Group that connection resides in. The best way to see these requests in
> action is to open up your Developer Tools in your browser and watch the
> requests the UI makes.
>
>
>
> Let me know if you have any more questions. Thanks!
>
>
>
> Matt
>
>
>
> On Mon, Nov 2, 2015 at 6:11 PM, Chakrader Dewaragatla <
> Chakrader.Dewaragatla@lifelock.com> wrote:
>
>  Hi,
>
> Does nifi has any REST api to monitor the queue size for a connection ?
>
>  I am trying to query a connection to see if it has any data
> queued/backlogged. I will use the backlog queue size to determine a
> workflow is chocking with massive incoming data or one of the downstream
> processor stopped processing.
>
>
>
>   Following api show the connection status, not queue size.
>
>
>
>   /controller/process-groups/{process-group-id}/connections/{id}
>
>
>
>   Thanks,
>
>   -Chakri
> ------------------------------
>
> The information contained in this transmission may contain privileged and
> confidential information. It is intended only for the use of the person(s)
> named above. If you are not the intended recipient, you are hereby notified
> that any review, dissemination, distribution or duplication of this
> communication is strictly prohibited. If you are not the intended
> recipient, please contact the sender by reply email and destroy all copies
> of the original message.
> ------------------------------
>
>
> ------------------------------
>
> The information contained in this transmission may contain privileged and
> confidential information. It is intended only for the use of the person(s)
> named above. If you are not the intended recipient, you are hereby notified
> that any review, dissemination, distribution or duplication of this
> communication is strictly prohibited. If you are not the intended
> recipient, please contact the sender by reply email and destroy all copies
> of the original message.
> ------------------------------
>
> _________________________________________________________________________________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou
privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message
par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques
etant susceptibles d'alteration,
> France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme
ou falsifie. Merci
>
> This message and its attachments may contain confidential or privileged information that
may be protected by law;
> they should not be distributed, used or copied without authorization.
> If you have received this email in error, please notify the sender and delete this message
and its attachments.
> As emails may be altered, France Telecom - Orange shall not be liable if this message
was modified, changed or falsified.
> Thank you.
>
>

Mime
View raw message