#928 [HHQ-1672] Resource Alert Trigger State Should Be Cached

[Hyperic Team]

http://jira.hyperic.com/browse/HHQ-1672
We have noticed at larger customer installations having complex alerts requiring trigger state evaluation that alert processing can be slow. In addition, these installations have a remote HQ database instance and suspect network problems.

We need to evaluate whether or not trigger event state caching is effective, so we're going to enable it for 3.2.1, then review the ehcache dignostics for this cache region after running on demo for a few days. If we have a high cache hit ratio, then we will keep the trigger state caching. Otherwise, we will consider dropping the trigger state caching.