Hi community.
Suppose I set the start of my flow to 8 o'clock. Now I shut down the
container between 7:59 and 8:01 and restart it afterwards. Will my flow
start at 8:02?
If the flow is not triggered afterwards, several things will get
complicated. I would have to inform all users during upgrades a
Sure not a problem! Hopefully below thoughts can help you get started:
As you may know the PrometheusReportingTask is a bit different from other
tasks in that it actually exposes an endpoint for Prometheus to scrape (vs.
pushing data directly to Prometheus). When the task is started the
endpoint
Yeah, there's no global proxy configuration that can be applied to all
processors and controller services that use HTTP in some way.
On Tue, Mar 3, 2020 at 1:14 PM Utsuk Prani wrote:
> Hi Mike, thanks for your response. It does work when I connect from my
> home and when I am not behind a proxy.
Yes, exactly! Reporting Task -> Prometheus -> Grafana for keeping an eye
on things running in NiFi.
If you have any hints/tips on getting things working, I'd be grateful.
On Tue, Mar 3, 2020 at 12:35 PM Yolanda Davis
wrote:
> Hi Eric,
>
> Were you looking to use the Prometheus Reporting Task
Hi Eric,
Were you looking to use the Prometheus Reporting Task for making metrics
available for Prometheus scraping? I don't believe any documentation
outside of what is in NiFi exists just yet, but I'm happy to help answer
questions you may have (I've used this task recently).
-yolanda
On Tue,
Hi Mike, thanks for your response. It does work when I connect from my home
and when I am not behind a proxy.
But I was hoping that the proxy setting should be supported as it is
normally in most of the web frameworks / apps.
On Mon, Mar 2, 2020 at 10:34 PM Mike Thomsen wrote:
> The properties y
Is there a guide to setting up Nifi and Prometheus anywhere? The nar docs
are a little vague.
Thanks,
Eric Ladner
Hello,
after we upgraded from Nifi 1.10 to 1.11.3 our pipeline containing a
LookupRecord processor using the IPLookupService started to fail. If we use a
CSVRecordLookupService then everything works, so I assume the problem is the
IPLookupService and not LookupRecord.
The IPLookupService is se
