Auto clearing notifications

Comments: 15

• 17 Nov, '20
  Mike W Merged

  Automatically remove outdated notifications... Examples:
  - When all updates are applied, delete update notifications
  - When disk space returns to above 15% delete low disk space notification
  
  Notifications should have option to be more of a current status than moment in time

• 22 Dec, '20
  Marius Mihalec Admin

  "Auto Clear Notifications" (suggested by Mike W on 2020-11-17), including upvotes (2) and comments (0), was merged into this suggestion.

• 22 Feb, '21
  Martin

  This is by far the most requested feature, and has been for quite some time now. Less wanted features seems to be added, but what's the current status of this one? The software will be improved immensely when we get rid of all the notification white noise.

• 23 Feb, '21
  Marius Mihalec Admin

  One way to solve this right now is by using automation workflows - any notification handled by a workflow will not be raised but handled automatically. You can decide to raise it later in the workflow if needed.

• 05 Mar, '21
  Darien Allen

  oh god please yes! I've emailed support about this myself! Marius using workflow would basically require us to redo all of the polices, etc that we have in place instead replacing them with Workflows. With all due respect that's not a real solution for someone who has had their instance up and running for quite awhile.

• 19 Mar, '21
  Nathan Scott

  Yes please on this feature request!

• 23 Mar, '21
  Vojtech Pilar

  @Marius
  It could be possible way if it would be possible to filter out notifications. But now workflows do not support that.
  I would love to see this implemented with different levels of resolving (auto delete, change priority), and possibly way to remove really outdated notifications.

• 28 Apr, '21
  Ben

  The only evident way to clear an Alert badge on a system is by deleting the notification from the system or possibly through an Automation Workflow (like Marius suggested). Since there is some benefit to retain a history of notifications per system, I would ideally like to see a few options available to deal with this, for example:
  
  1. Mark Alert as cleared when condition no longer exists (as originally suggested by Greg)
  2. Ability to manually clear Alerts
  3. Alert badge on System should reflect the cleared status of Alerts, i.e. if Critical Alert cleared, remove Critical badge from System, but retain alert for historical purpose
  4. Move cleared Alerts into a cleared category within Alerts and log how it was cleared (automatically by Pulseway or manually by user)

• 27 May, '21
  Henrik B Christnesen

  I've created a workflow for automatic Windows Updates and reboot in Maintenance mode.
  But when the updates have been applied, and all is good - the autoclearing of the notification would really help out.
  
  As it is right now, I have to manually remove them.
  
  In this scenario it even seems a little silly given that should the update have somehow failed - the notification automatically pops up again anyway.

• 01 Jun, '21
  Jan Carsten Nielsen

  “Auto reset” for notification that is not a problem anymore (CPU, RAM, Disk Space) – if the threshold is not an issue, the Notification is the problem (specially on CPU and RAM that goes up and down without fixing it)

• 07 Jun, '21
  Darien Allen

  To my knowledge, the Executive Report (though it only goes back 30 days) will give you a history of notification on machine regardless of whether the alert has been cleared or not.

• 11 Jun, '21
  Adam at PI

  This is the most time consuming thing to have to manually clear notifications for conditions that have been resolved. I would like to see a the auto-cleared notifications still listed in a notification history tab on the device screen.

• 16 Oct, '21
  Mark G

  Since this is currently in development, I hope the mark isn't missed here. ALL notification types should have some sort of options or custom settings to allow them to be cleared. Essentially allowing us to "rearm" the alert. This should include custom event log alerts as well. If I generate a custom event log alert as an error, when the "script" runs that generated that alert, generates a success, I should be able to clear the past alert.
  
  Adding 1 more comment to this to be clear. If I have a native alert for 90% CPU over 10 minutes, I should be able to select when I want to clear/rearm it. Maybe I want to confirm the issue is gone so I want to wait 10 minutes of it being below 90% to clear, or maybe 60 minutes, etc. I hope it's not going to just be an option to "auto clear" and then the second/minute the condition doesn't exist, it clears. That could result in a lot of noise for no reason.

• 16 Oct, '21
  Mark G

  Remove - Duplicate post.

• 05 Nov, '21
  Louis Videc

  is there an estimated release date for this feature?