Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alerts Manager - Automation policies - Alerts triggering on not selected checks #1817

1 task done
technoicon opened this issue Mar 29, 2024 · 0 comments
1 task done


Copy link

technoicon commented Mar 29, 2024

Server Info (please complete the following information):

  • OS: Ubuntu 18.04.05
  • Browser: chrome
  • RMM Version (as shown in top left of web UI): 0.17.5

Installation Method:

  • Docker

Agent Info (please complete the following information):

  • Agent version (as shown in the 'Summary' tab of the agent from web UI): Agent v2.6.2
  • Agent OS: Windows Server 2019 Standard, 64 bit v1809 (build 17763.4010)

Describe the bug
Alerts are being sent out via "Channel" [email, dashboard, txt] that is not selected, I've only noticed this with email "channel".

Side Note: Informational alerts are also being sent out as failure alerts with powershell scripts.

To Reproduce
Steps to reproduce the behavior:
email and notifications settings must be setup and working

  1. Create an Automation Policy and add checks. Tick Email alerts on one check, untick email alerts on another check.
  2. Create an Alert Policy.
  3. Under "Check Settings"
  4. Select email, select only email on alerts severity "Error"
  5. Assign this alert template to the automation policy.
  6. Assign this Automation policy to a Client.
  7. Run the checks, have them all fail.
  8. You will receive an email alert from each check, even though the Email Alert checkbox is not ticked.

Expected behavior
Only email on checks and alerts that are "ticked" in the automation policy. Not all checks.




Screenshot 2024-03-29 120638
Screenshot 2024-03-29 120648



Additional context
Add any other context about the problem here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

No branches or pull requests

1 participant