Hi Andy,

Thanks for the fast response.  I am trying to supress the standard cluster
heartbeat messages:

2018-06-02 01:03:18,280 INFO [Clustering Tasks Thread-1]
o.a.n.c.c.ClusterProtocolHeartbeater Heartbeat created at 2018-06-02
01:03:18,147 and sent to <node>:<pot> at 2018-06-02 01:03:18,280; send took
133 millis.

I tried adding  <logger name=“org.apache.nifi.cluster.coordination.heartbeat"
level=“WARN”/> but the messages persist.  I also tried <logger
name="org.apache.nifi.cluster" level="WARN"/> and that suppresses the
cluster manager INFO messages but not the heartbeat messages.
Setting <logger name="org.apache.nifi" level="WARN"/> does the trick but I
wanted to go a little less all inclusive than that.

Regards,
Paul

On Fri, Jun 1, 2018 at 6:53 PM, Andy LoPresto <[email protected]> wrote:

> Hi Paul,
>
> Can you provide a specific message you would like to be suppressed? Given
> a quick examination, all the logger messages in
> ClusterProtocolHeartbeatMonitor.java are at DEBUG level, so
> setting <logger name=“org.apache.nifi.cluster.coordination.heartbeat"
> level=“INFO”/> should be sufficient. If this doesn’t solve your problem,
> please let us know which messages specifically (you can redact sensitive
> information like addresses, but provide enough of the message so we can
> locate it in the code) you would like to be suppressed. Thanks.
>
> Andy LoPresto
> [email protected]
> *[email protected] <[email protected]>*
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
> On Jun 1, 2018, at 12:54 PM, Paul Riddle <[email protected]>
> wrote:
>
> Hello NiFi Team,
>
> Is there a setting for controlling the log level of heartbeat messages in
> logback.xml on NiFi 1.6.0?  While adjusting  <logger
> name="org.apache.nifi.cluster" level="WARN"/> , only the cluster
> coordinator messages are affected.  I'd like to be able to silence the
> cluster node heartbeat messages in my app logs without setting the overall
> logging to WARN.
>
> Any help you can provide is greatly appreciated.
>
> Regards,
> Paul
>
>
>

Reply via email to