Debug Logging of GossipStatus

[netclectic]

• Which Akka.Net version you are using
  1.3.9

• On which platform you are using Akka.Net
  Windows 10 64Bit

When I have loglevel set to DEBUG, but with actor and cluster debug options set to off, I still continuously receive some cluster gossip debug log messages, like:

 [Uninitialized] Received Akka.Cluster.InternalClusterAction+Subscribe

 [TryingToJoin] Received Akka.Cluster.InternalClusterAction+Welcome

 [Initialized] Received Akka.Cluster.GossipEnvelope

 [Initialized] Received GossipStatus(from=UniqueAddress: (akka.tcp://migrationarchitect@127.0.0.1:4053, 410406129), version=VectorClock(E5C3551E85FDF0DE5C54487E6B71E9A9->6))
 [Initialized] Received GossipStatus(from=UniqueAddress: (akka.tcp://system@127.0.0.1:4053, 410406129), version=VectorClock(E5C3551E85FDF0DE5C54487E6B71E9A9->6))

 [Initialized] Received Akka.Cluster.InternalClusterAction+ExitingConfirmed

The GossipStatus message repeats every second or so, from each node in the cluster, while the others are just at startup / shutdown.

My hocon is as follows:

	akka {
		loggers=["Akka.Logger.Serilog.SerilogLogger, Akka.Logger.Serilog"]
		log-config-on-start = off
		loglevel = DEBUG
		stdout-loglevel = INFO

		actor {
			provider = cluster			
			debug {
				receive = off
				autoreceive = off
				lifecycle = off
				event-stream = off
				unhandled = off
			}			
		}
	
		remote {
			log-remote-lifecycle-events = INFO
			dot-netty.tcp {
				hostname = "127.0.0.1"
				port = 0
			}
		}            

		cluster {
			seed-nodes = ["akka.tcp://system@127.0.0.1:4053"]			
			debug {
				verbose-heartbeat-logging = off
				verbose-receive-gossip-logging = off
			}                    
		}
	}

I would expect the GossipStatus messages to be covered by the 'verbose-receive-gossip-logging' setting in the config and not be sent when it is set to 'off'.

Is there some other config setting that would disable these messages?

[Aaronontheweb]

This is definitely a bug, and there's an opportunity for a massive user experience improvement here too. Going to get this patched before we push 1.3.10.