My log checkers trip several times a day by an innocuous level 1 syslog message from Samba, which otherwise has impeccable logging behaviour:
May 16 09:20:10 kcrias01 samba[13709]: [2016/05/16 09:20:10.462432, 1] ../source4/dsdb/kcc/kcc_deleted.c:105(kccsrv_check_deleted)
May 16 09:20:10 kcrias01 samba[13709]: Doing a full scan on DC=ForestDnsZones,DC=my,DC=domain and looking for deleted object
May 16 09:20:10 kcrias01 samba[13709]: [2016/05/16 09:20:10.465093, 1] ../source4/dsdb/kcc/kcc_deleted.c:105(kccsrv_check_deleted)
May 16 09:20:10 kcrias01 samba[13709]: Doing a full scan on DC=DomainDnsZones,DC=my,DC=domain and looking for deleted object
May 16 09:20:10 kcrias01 samba[13709]: [2016/05/16 09:20:10.472267, 1] ../source4/dsdb/kcc/kcc_deleted.c:105(kccsrv_check_deleted)
May 16 09:20:10 kcrias01 samba[13709]: Doing a full scan on CN=Configuration,DC=my,DC=domain and looking for deleted object
May 16 09:20:10 kcrias01 samba[13709]: [2016/05/16 09:20:10.535309, 1] ../source4/dsdb/kcc/kcc_deleted.c:105(kccsrv_check_deleted)
May 16 09:20:10 kcrias01 samba[13709]: Doing a full scan on DC=my,DC=domain and looking for deleted object
Looking at the source in source4/dsdb/kcc/kcc_deleted.c, the message is emitted whenever the execution path goes through kccsrv_check_deleted() to "check to see if any deleted objects need scavenging". At that point everything is hunky-dory, so the message debug level should not be 1.
Otherwise: sincere compliments for Samba's excellent run-time debug logging support!