You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@nifi.apache.org by Pavel S <pa...@gmail.com> on 2020/06/01 21:10:13 UTC
Prometheus reporting task
Hello
I have upgraded Nifi to version 1.10.0 just to be able to enable Prometheus
Reporting Task. Enabling the task was easy and installing Prometheus itself
was easy and pointing it to Nifi to scrape. I have number of processors
running in my Nifi. However, the metrics that get exposed only are bound to
one of those processors and no matter what I try to do it is always that
same processor that gets exposed. What am I doing wrong? How do I get all
of my processors to expose? Is there a configuration that I am missing
somewhere?
Re: Prometheus reporting task
Posted by Pavel S <pa...@gmail.com>.
Interesting observation, I set it to "All Process groups" and in Prometheus
metrics only came up this one specific process, that same process that
comes up for All Components. It's almost as if other processes are not
matching whatever criteria the Task reports on.
On Mon, Jun 1, 2020 at 5:56 PM Andy LoPresto <al...@apache.org> wrote:
> At a quick glance it does not look like there is much logging. Perhaps
> Matt Burgess can offer more context around this?
>
> Andy LoPresto
> alopresto@apache.org
> *alopresto.apache@gmail.com <al...@gmail.com>*
> He/Him
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
>
> On Jun 1, 2020, at 2:45 PM, Pavel S <pa...@gmail.com> wrote:
>
> Yes I did enable it on "All Components". I will check it again, I wish
> there was more documentation on this. Is there a log anywhere that I can
> see about what the reporting task is doing?
>
> On Mon, Jun 1, 2020 at 5:19 PM Andy LoPresto <al...@apache.org> wrote:
>
>> Yolanda replied to a similar question a while ago with some good notes on
>> setting this up [1]. Specifically, you should be able to configure the
>> reporting task to be scoped to the root process group, a specific process
>> group, or the entire canvas.
>>
>> [1]
>> http://apache-nifi-users-list.2361937.n4.nabble.com/Metrics-via-Prometheus-tp9102p9107.html
>>
>> Andy LoPresto
>> alopresto@apache.org
>> *alopresto.apache@gmail.com <al...@gmail.com>*
>> He/Him
>> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
>>
>> On Jun 1, 2020, at 2:10 PM, Pavel S <pa...@gmail.com>
>> wrote:
>>
>> Hello
>>
>> I have upgraded Nifi to version 1.10.0 just to be able to enable
>> Prometheus Reporting Task. Enabling the task was easy and installing
>> Prometheus itself was easy and pointing it to Nifi to scrape. I have number
>> of processors running in my Nifi. However, the metrics that get exposed
>> only are bound to one of those processors and no matter what I try to do it
>> is always that same processor that gets exposed. What am I doing wrong? How
>> do I get all of my processors to expose? Is there a configuration that I am
>> missing somewhere?
>>
>>
>>
>
Re: Prometheus reporting task
Posted by Andy LoPresto <al...@apache.org>.
At a quick glance it does not look like there is much logging. Perhaps Matt Burgess can offer more context around this?
Andy LoPresto
alopresto@apache.org
alopresto.apache@gmail.com
He/Him
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
> On Jun 1, 2020, at 2:45 PM, Pavel S <pa...@gmail.com> wrote:
>
> Yes I did enable it on "All Components". I will check it again, I wish there was more documentation on this. Is there a log anywhere that I can see about what the reporting task is doing?
>
> On Mon, Jun 1, 2020 at 5:19 PM Andy LoPresto <alopresto@apache.org <ma...@apache.org>> wrote:
> Yolanda replied to a similar question a while ago with some good notes on setting this up [1]. Specifically, you should be able to configure the reporting task to be scoped to the root process group, a specific process group, or the entire canvas.
>
> [1] http://apache-nifi-users-list.2361937.n4.nabble.com/Metrics-via-Prometheus-tp9102p9107.html <http://apache-nifi-users-list.2361937.n4.nabble.com/Metrics-via-Prometheus-tp9102p9107.html>
>
> Andy LoPresto
> alopresto@apache.org <ma...@apache.org>
> alopresto.apache@gmail.com <ma...@gmail.com>
> He/Him
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
>
>> On Jun 1, 2020, at 2:10 PM, Pavel S <pavel.sapozhnikov82@gmail.com <ma...@gmail.com>> wrote:
>>
>> Hello
>>
>> I have upgraded Nifi to version 1.10.0 just to be able to enable Prometheus Reporting Task. Enabling the task was easy and installing Prometheus itself was easy and pointing it to Nifi to scrape. I have number of processors running in my Nifi. However, the metrics that get exposed only are bound to one of those processors and no matter what I try to do it is always that same processor that gets exposed. What am I doing wrong? How do I get all of my processors to expose? Is there a configuration that I am missing somewhere?
>
Re: Prometheus reporting task
Posted by Pavel S <pa...@gmail.com>.
Yes I did enable it on "All Components". I will check it again, I wish
there was more documentation on this. Is there a log anywhere that I can
see about what the reporting task is doing?
On Mon, Jun 1, 2020 at 5:19 PM Andy LoPresto <al...@apache.org> wrote:
> Yolanda replied to a similar question a while ago with some good notes on
> setting this up [1]. Specifically, you should be able to configure the
> reporting task to be scoped to the root process group, a specific process
> group, or the entire canvas.
>
> [1]
> http://apache-nifi-users-list.2361937.n4.nabble.com/Metrics-via-Prometheus-tp9102p9107.html
>
> Andy LoPresto
> alopresto@apache.org
> *alopresto.apache@gmail.com <al...@gmail.com>*
> He/Him
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
>
> On Jun 1, 2020, at 2:10 PM, Pavel S <pa...@gmail.com> wrote:
>
> Hello
>
> I have upgraded Nifi to version 1.10.0 just to be able to enable
> Prometheus Reporting Task. Enabling the task was easy and installing
> Prometheus itself was easy and pointing it to Nifi to scrape. I have number
> of processors running in my Nifi. However, the metrics that get exposed
> only are bound to one of those processors and no matter what I try to do it
> is always that same processor that gets exposed. What am I doing wrong? How
> do I get all of my processors to expose? Is there a configuration that I am
> missing somewhere?
>
>
>
Re: Prometheus reporting task
Posted by Andy LoPresto <al...@apache.org>.
Yolanda replied to a similar question a while ago with some good notes on setting this up [1]. Specifically, you should be able to configure the reporting task to be scoped to the root process group, a specific process group, or the entire canvas.
[1] http://apache-nifi-users-list.2361937.n4.nabble.com/Metrics-via-Prometheus-tp9102p9107.html <http://apache-nifi-users-list.2361937.n4.nabble.com/Metrics-via-Prometheus-tp9102p9107.html>
Andy LoPresto
alopresto@apache.org
alopresto.apache@gmail.com
He/Him
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
> On Jun 1, 2020, at 2:10 PM, Pavel S <pa...@gmail.com> wrote:
>
> Hello
>
> I have upgraded Nifi to version 1.10.0 just to be able to enable Prometheus Reporting Task. Enabling the task was easy and installing Prometheus itself was easy and pointing it to Nifi to scrape. I have number of processors running in my Nifi. However, the metrics that get exposed only are bound to one of those processors and no matter what I try to do it is always that same processor that gets exposed. What am I doing wrong? How do I get all of my processors to expose? Is there a configuration that I am missing somewhere?