When a node is in a scheduled outage where notifications are being suppressed, the notice still gets created, causing the overall notification count to increase.

Note that it doesn't get sent - i.e. no one actually gets notified - but you can end up with tens of thousands of notices (see attached example) which can be very annoying.

Here is an example log:

2016-06-28 15:43:20,338 DEBUG [Notifd:BroadcastEventProcessor-Thread] o.o.n.c.NotificationManager: Exact match using notification UEI uei.opennms.org/generic/traps/SNMP_Cold_Start for event UEI: uei.opennms.org/generic/traps/SNMP_Cold_Start
2016-06-28 15:43:20,338 DEBUG [Notifd:BroadcastEventProcessor-Thread] o.o.n.f.JdbcFilterDao: Filter.isRuleMatching((((IPADDR IPLIKE ...)) & (nodeId == 143) & (ipAddr == '172.20.1.15')))
2016-06-28 15:43:20,338 DEBUG [Notifd:BroadcastEventProcessor-Thread] o.o.n.f.JdbcFilterDao: Filter.isRuleMatching((((IPADDR IPLIKE ...)) & (nodeId == 143) & (ipAddr == '172.20.1.15'))): SQL statement: SELECT DISTINCT ipInterface.ipAddr FROM ipInterface JOIN node ON (ipInterface.nodeID = node.nodeID) WHERE (((IPLIKE(ipInterface.IPADDR, '...'))) AND (node.nodeId = 143) AND (ipInterface.ipAddr = '172.20.1.15')) LIMIT 1
2016-06-28 15:43:20,340 DEBUG [Notifd:BroadcastEventProcessor-Thread] o.o.n.f.JdbcFilterDao: isRuleMatching: rule "(((IPADDR IPLIKE ...)) & (nodeId == 143) & (ipAddr == '172.20.1.15'))" matches an entry in the database
2016-06-28 15:43:20,340 DEBUG [Notifd:BroadcastEventProcessor-Thread] o.o.n.c.NotificationManager: Event uei.opennms.org/generic/traps/SNMP_Cold_Start matched notice Just Testing
2016-06-28 15:43:20,343 DEBUG [Notifd:BroadcastEventProcessor-Thread] o.o.n.n.BroadcastEventProcessor: destination : Email-Tarus
2016-06-28 15:43:20,343 DEBUG [Notifd:BroadcastEventProcessor-Thread] o.o.n.n.BroadcastEventProcessor: text message: Testing Cold Start
2016-06-28 15:43:20,343 DEBUG [Notifd:BroadcastEventProcessor-Thread] o.o.n.n.BroadcastEventProcessor: num message : Testing Cold Start
2016-06-28 15:43:20,343 DEBUG [Notifd:BroadcastEventProcessor-Thread] o.o.n.n.BroadcastEventProcessor: subject : Notice #182845: Cold Start
2016-06-28 15:43:20,343 DEBUG [Notifd:BroadcastEventProcessor-Thread] o.o.n.n.BroadcastEventProcessor: node : 143
2016-06-28 15:43:20,343 DEBUG [Notifd:BroadcastEventProcessor-Thread] o.o.n.n.BroadcastEventProcessor: interface : 172.20.1.15
2016-06-28 15:43:20,343 DEBUG [Notifd:BroadcastEventProcessor-Thread] o.o.n.n.BroadcastEventProcessor: service : null
2016-06-28 15:43:20,343 INFO [Notifd:BroadcastEventProcessor-Thread] o.o.n.n.BroadcastEventProcessor: Inserting notification #182845 into database: Notice #182845: Cold Start
2016-06-28 15:43:20,351 DEBUG [Notifd:BroadcastEventProcessor-Thread] o.o.n.c.BasicScheduleUtils: isTimeInOutage: checking for time '2016-06-28T15:43:20.351-0400' in schedule 'JustATest'
2016-06-28 15:43:20,351 DEBUG [Notifd:BroadcastEventProcessor-Thread] o.o.n.c.BasicScheduleUtils: isTimeInOutage: checking begin/end time...
current: 2016-06-28T15:43:20.351-0400
begin: 2016-06-28T00:00:00.000-0400
end: 2016-06-28T23:59:59.000-0400
2016-06-28 15:43:20,351 DEBUG [Notifd:BroadcastEventProcessor-Thread] o.o.n.n.BroadcastEventProcessor: scheduledOutage: configured outage 'JustATest' applies, notification for interface 172.20.1.15 on node 143 will not be sent

Note that the check is done after the notice is created.