I’ve stopped using alert feature long ago due to volume of false positives and failure to self-resolve and preferably disappear (could just be in a log)

This is a great idea. The current work around of closing tickets after X-hours isn't sufficient and doesn't address the problem directly.

I just post a suggestion litle different than you but with the same meaning...

To planify the monitoring and exclude some periods to the monitoring to avoid fake alert due to a planned reboot

I think our ideas have the same meeaning eventought your apporch is a good way too.

I just think we need to avoding the alert before his generating and not treat it after... But i aggreed in some case for a non planified task an auto closing ticket when are solved can be a good way..
I think our ideas have the same meeaning eventought your apporch is a good way too.

I just think we need to avoding the alert before his generating and not sovled it after... But i aggreed in some case for a non planified task... Auto closing ticket when are solved can be a good way..

Look for the subject : Suspending monitoring for planned tasks

This would be super helpful

Can you also add the option to auto-resolve different types of alerts or not. We should be able to see an alert history. They can fall down below into an inactive status or change color but seeing history helps us identify trends and quickly see what's happened recently.

instead of Quick Connect, Manage will be more useful in my opinion.

Tickets generatet by Alerts from Thresholds where perfect to Close Automatic after the Thresholds is normal again.

Self-heal - if the threshold returns to normal where perfect to auto close the ticket.

Please let us know if this feature is available as we are also looking for this.

Came here to add this, see it's already a thing, big yes please to time-based automation; I'd like my agents to be able to change a ticket to Resolved and have that automatically trigger a rule that the ticket automatically closes in say five hours but would use this for other things as well - such as follow ups etc

When alerts are created, I would like to see the amount of time between ticket creation and when the the issue was resolved. When it is resolved, I would like the ticket to close automatically. This would save lots of time spent manually closing all tickets that have already been taken care of.

If a Critical ticket is opened , that's good thats what we want but if it then auto-heals itself, it should update and close the ticket and not open itself again later on.

We were advise on the alerts, within admin console, you can tick for auto ticket creation, whenever we do that we get bombarded with alerts, it doesn't self heal. and then it gets another tickets. it causes absolute hell when we turn it on. Keeps creating brand new tickets, it doesn't update the original one.

Even if we say it in the 15 interval, problem is if that self heals and then it will create another ticket, it will keep on logging tickets until it is resolve.

When a technician change the ticket status in Resolved/Closed the relative alert would be solved automatically.

When a ticket is created for an alert the following features would be amazing.

1. Self-heal - If the threshold returns to normal the ticket auto closes.

2. Quick Connect - On an alert ticket having a shortcut to the affected device with the ability to click the shortcut and go straight to the machine.

Add automation rule to close a ticket. If you configure automation rules to open a ticket you should also be able to automate closing a ticket. An example being, if you have an availability monitor set up and the alert opens a new ticket but that alert gets resolved a few minutes later you should be able to automate closing the ticket as well.