Different options for "Delete Instances..."
Recently had this discussion with a customer and it was brought to my attention to raise a feature request for this.
Customer is requesting that there are more than two options for deleting instances in a module.
Instead of "delete immediately" or "delete after 30 days", they are suggesting a few more options such as "delete after 7 days" or "delete after 14 days".
Elisa Olivieri
Posted 2 years ago·Last reply 1 year ago
7 comments
lucjad
·1 year agoIs there solutions to this yet?
I'm having trouble with the Auto Delete option. I need certain jobs to persist so their alert thresholds remain intact, but they're being removed automatically. On top of that, I’m dealing with AG replicas that fail over along with the jobs, which leaves behind failed job warnings on the previous replica if the auto delete is off.
pgordon
·1 year agoI would love if my custom setting for this option (whatever that happens to be) could be preserved when doing module upgrades.
I also love the idea of stop alerting after a certain number of days, regardless of what the deletion setting is set to
Patrick Rouse
·1 year agoWe are currently testing this in non-production portals.
LM User
·2 years agoDon't forget that " delete instances " doesn't actually delete instances or prevent them from being deleted. All it does is maintain the historical data. What would really be nice is if the instance was still visible, but set to not alert after a certain amount of time, then got deleted.
It would be really nice if delete instances actually didn't delete them, but showed that they were marked for deletion before finally hiding them. The problem is some things go down and get deleted before the alert showing that it went down is generated. We have quite a few data sources where cannot use auto delete (so it's all manual and tedious), because if they do, we miss the alert saying that it went down. This is because the alert generates at the same time that the instance is deleted. And no alert actually happens.
LM User
·2 years agoFor us, it would be perfect if we could say "mute alerts after X collection cycles after it disappears from discovery". This way, the alert would still get generated, the instance would hang out while we fixed it, and if we didn't fix it the instance would eventually delete, cleaning it up automatically.