> On 18. Aug 2017, at 11:15, Gijs Rijnders <gijs.rijnd...@surfnet.nl> wrote: > > Dear Icinga2 users, > > I'm running Icinga2 and I'm posting SNMP traps to it. They are submitted > to a passive check service in Icinga2, which in turn should send > notifications about these to Slack. I'm using the > 'icinga2-slack-notifications' package for the Slack notifications > ( > https://exchange.icinga.com/richardhauswald/icinga2-slack-notifications > ). > > It all works great, except I'm having trouble limiting the number of > notifications. I don't want to be flooded with notifications. I tried > the 'interval = 3h' setting to see if Icinga2 will refrain from sending > more than one notification every 3 hours. However, that does not work.
How does the configuration for these notification objects look like? Please add all relevant objects (host, service, user, notification command) too. Further, add the output of “icinga2 —version” here too. Since you say “flooded”, enabling the debug log and extracting the logged messages for notifications will certainly be helpful too (more on that in the troubleshooting docs). Kind regards, Michael > > I have one alarm/service for all SNMP traps that are sent by a specific > host. For example, traps from BGP and link up/down events are sent to > the same alarm. Does the interval setting not work because the messages > are different every time? How can I configure it such that the > notifications are limited? > > Thanks in advance! > > Kind Regards, > > Gijs Rijnders > > <0x94093C428E8F59E6.asc>_______________________________________________ > icinga-users mailing list > icinga-users@lists.icinga.org > https://lists.icinga.org/mailman/listinfo/icinga-users _______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
