Wiring up a rest client to make a rest request to the NIFI API, seems the
following three are possible candidates:
GET /controller-services/{id} Gets a controller service
GET /controller-services/{id}/references Gets a controller service
GET /controller-services/{id}/state Gets the state for a
controller service
I’ll do some initial tests with Postman to see what is returned in response
json payload (and if 200 means up and running, or just a successful API request)
Sounds good
John
> On Feb 1, 2021, at 4:46 PM, Joe Witt <[email protected]> wrote:
>
> John,
>
> You're using a vendor distribution of NiFi. You should contact the vendor.
>
> You can certainly monitor the state of a controller service via the REST API.
> They should either be enabled or not enabled.
>
> Thanks
>
> On Mon, Feb 1, 2021 at 5:39 PM jgunvaldson <[email protected]
> <mailto:[email protected]>> wrote:
> Hi All,
>
> Root level (canvas) Controller Services - We tend to setup several Root level
> Controller services for developers that are typically DBCPConnectionPools and
> DistributedMapCacheClientService and maybe a few other. MOST importantly,
> these controller services cannot be down and cannot be disabled - must remain
> Enabled at all times.
>
> We have now had a few outages where upon examination a Controller Service has
> encountered “something” that caused it to be Disabled or Down.
>
> Is there a standard practice we can use to “Monitor” the controller services
> and ensure we get alerted if any one of them goes into a Disable state?
>
> What do folks generally think is a good monitoring practice?
>
> We are on
>
> HDF Version 3.4.1.1.
>
> Powered by Apache NiFi Version 1.9.0
> 1.9.0.3.4.1.1-4 built 05/01/2019 02:15:30 UTC
> Tagged nifi-1.9.0-RC2
> From 7410fa4 on branch UNKNOWN
>
>
