Forum Discussion
Don'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.
For 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.
Related Content
- 2 years agoAnonymous