I am having issues where some of our Rules are being triggered, but not actually sending alerts to our transport (MSTeams)
We can manually run the alerts in CLI and it works. We get the alert on teams and everything. However if we let alerts generate naturally, it doesn’t ever send it to the transport. Only shows an active rule/alert on the dashboard.
That said our Devices up/down alerts correctly. The ones that seem to not are Sensor over or under limit, and any new rules we make.
If you have a max set with ‘1’, then it will run once and only once. It will only run again after it has been cleared. So if you expect more than one notification for a single alert, then yes, you should change to a higher value, or to -1 for unlimited as @paintballer4lfe wrote .
Just a side note as to why i said set to -1 right out of the gate. I had this very same issue setting it to 1 as you did. Asked some of the guys in the Discord and the only working solution to send 1 alert, let alone many, was to set it to -1 or 5.
It appears the “run once” rule for my Telegram transport did not work unless it was set to multiple or unlimited.
“Device Up/Down” alert rule, is not mapped to specific devices or device groups ?
Correct
I can best describe it as if…everything is working except for the exact moment that a rule should be triggering sending to transport. Manually testing transport, alerts, rules, etc go through fine with no errors. But it appears when an rule is actually triggered it never even tries to send to transport, no matter our max/notification limits/settings.
Hello, I am facing exactly the same issue here. Tests are working fine, transport works when test button is pressed. but it doesn’t when triggered automatically. Were you able to solve this issue?
after checking another post, I have found the issue. When using MSTeams The transports templates must be changed to the MSteams template: https://docs.librenms.org/Alerting/Templates/
