Current situation:
The data retention and averaging functions discard a lot of data that is valuable for alarm/incident response after the data is older than 1 hour. I get notifications regarding datastore or virtual disk latency increasing very high. When I respond 2 or 3 hours later, there is no record to be found any where (except the email alert) that the latency every reached high enough to trigger an alert. The peaks and valleys have all been discarded already.
Feature Request:
I would like to select specific counters that are of higher business importance and select a high resolution (20 second) retention schedule with a longer duration (like 12 or 24 hours instead of just 1 hour)
Support suggested I request a feature request and that I post it in the forums:
Case # 02088050 which is a continuation of Case 01874515.
Hello Paul,
The request makes sense for me, however UI of choosing individual retention for each counter seems crowdy. Anyway, I`ll talk to developers to get more information about ease of implementation.
Thanks for the feedback!
I would accept global option for changing retention duration if doing so on a per counter basis is too complicated. It would use a lot more DB space, but this is important enough to me that I would accept that.
There is such a global option available with help of support team, however long retention of detailed data may result in huge database and slow software performance.
Could you enlighten size of your infrastructure(database, VM, host number)?
Thanks!
