Scott,
Glad to hear it! Please let me know if you have any questions or if
issues arise. One thing I forgot to mention is that I think
backpressure prediction is disabled by default due to the extra
consumption of CPU to do the regressions, make sure the
"nifi.analytics.predict.enabled" property
Excellent! Very much appreciate the help and for setting me on the right
path. I'll give the queryNiFiReportingTask code a try.
Scott
On Wed, Jul 21, 2021 at 3:26 PM Matt Burgess wrote:
> Scott et al,
>
> There are a number of options for monitoring flows, including
> backpressure and even
Scott et al,
There are a number of options for monitoring flows, including
backpressure and even backpressure prediction:
1) The REST API for metrics. As you point out, it's subject to the
same authz/authn as any other NiFi operation and doesn't sound like it
will work out for you.
2) The
Scott
Check out this from Pierre: https://pierrevillard.com/tag/reporting-task/
We monitor all parameters from NiFi via Reporting Tasks. We send all parameters
via MQTT to InfluxDB and monitor that via Grafana.
There we can then start alerts when the levels reach a critical value.
If that
Scott
Nifi supports both push and pull. Push via reporting tasks and pull via
rest api.
Are you needing a particular impl of a reporting task?
You are right this is a common need. Solved using one of these methods.
Thanks
On Wed, Jul 21, 2021 at 2:58 PM scott wrote:
> Great comments all. I
Great comments all. I agree with the architecture comment about push
monitoring. I've been monitoring applications for more than 2 decades now,
but sometimes you have to work around the limitations of the situation. It
would be really nice if NiFi had this logic built-in, and frankly I'm
surprised
Thanks for the follow up! Saved me some investigation :)
-joey
> On Jul 21, 2021, at 11:11 AM, Juan Pablo Gardella
> wrote:
>
>
> Please ignore, my error during applying the patch (see below).
> +joey.fra...@icloud.com worked fine the patch! Thank you!!
>
> It works fine! I copied the
In general, it is a bad architecture to do monitoring via pull request. You
should always push. I recommend a look at the book "The Art of Monitoring" by
James Turnbull.
I also recommend the very good articles by Pierre Villard on the subject of
NiFi monitoring at
Please ignore, my error during applying the patch (see below).
+joey.fra...@icloud.com worked fine the patch!
Thank you!!
It works fine! I copied the patched in different location:
COPY --chown=nifi:nifi start.sh /opt/nifi/scripts/scripts/start.sh
COPY --chown=nifi:nifi secure.sh
Can't you leverage some of the recent nifi features and basically run sql
queries over NiFi metrics directly as part of the flow? Then act on it with
a full flexibility of the flow. Kinda like a push design.
Andrew
On Tue, Jul 20, 2021, 2:31 PM scott wrote:
> Hi all,
> I'm trying to setup some
Hi Chris, thank you for your quick response
I tried the flow with 1.13.2 and 1.13.1, and 1.14.0 just before the first
RC and it still had the problem, so I am not sure if this is related to the
session handling you pointed out, that has been fixed in 1.13.2
Le mer. 21 juil. 2021 à 16:22, Chris
1.13.1 was known to have problems with session handling - see the Release
Note "lowlights" for 1.13.1 [1]
It is recommended to upgrade to version 1.13.2 (or the latest 1.14.0). If
you can't upgrade then 1.13.0 would be better than 1.13.1.
[1]
Hi all,
Currently using NiFi 1.11.4, we face a blocking issue trying to switch to
NiFi 1.13.1+ due to the VolatileContentRepository : some processors we use
(and probably others that we didn't try) were not able to process
flowfiles, such as MargeRecord, QueryRecord or SplitJson (logs are in the
Hi,
I tried the patch by adjusting the image, and it seems it is not working if
it is running behind a proxy.
COPY --chown=nifi:nifi start.sh /opt/nifi/scripts/scripts/start.sh
COPY --chown=nifi:nifi secure.sh /opt/nifi/scripts/scripts/secure.sh
Nifi starts but I am unable to access it when it
Hi Etienne,
I have also have similar usecase of using sensitive parameter context in a
non sesitive property like in ExecuteSql's " sql select query " property
field.
Did u find any way of doing that?
Any other suggestion from anyone is really appriciated.
Thanks,
Sanjeet
On Mon, 19 Jul 2021,
15 matches
Mail list logo
