Implement heartbeat from remote servers

[Jeremy Pemberton-Pigott <fu...@gmail.com>]

Does anyone have an idea of how to implement a heartbeat message posted
from remote Nifi servers to another server running Nifi? This is so that I
can tell if within say 1 hour there was no heartbeat received from a known
list it could generate a log message with an error message of the server
that no heartbeat was received from.

Thanks,

Jeremy

Re: Implement heartbeat from remote servers

[Andy LoPresto <al...@apache.org>]

If the NiFi nodes are all in a cluster, the heartbeating is taken care of by the cluster communication. If you are talking about two distinct instances, you could put a GenerateFlowFile processor with arbitrary “heartbeat” data and send it via Site to Site or InvokeHTTP to the “listening” NiFi instance. There you could set a value in the Distributed Map Cache for each server which has pinged in and the timestamp, and then use another processor to check on a determined schedule for the presence/absence of certain values in the cache. 


Andy LoPresto
alopresto@apache.org
alopresto.apache@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

> On Sep 3, 2019, at 2:46 AM, Jeremy Pemberton-Pigott <fu...@gmail.com> wrote:
> 
> Does anyone have an idea of how to implement a heartbeat message posted from remote Nifi servers to another server running Nifi? This is so that I can tell if within say 1 hour there was no heartbeat received from a known list it could generate a log message with an error message of the server that no heartbeat was received from.
> 
> Thanks,
> 
> Jeremy