Pinned topic Why breached service policy not showing up as a runtime task?
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Testing Service Policies during a load test reveals Operation Alerts on the Runtime Operations > reports page consisting of breached service policies. These alerts are repeated on this page but no runtime tasks are generated associated with these alerts on the System Administration > Task Management > Runtime Tasks. For the purpose of this test, the dynamic clusters contain default configuration and are in "supervised" mode. The APC minimum time between placement change was reduced to 2 minutes. Is there some configuration that needs to be performed in order for runtime tasks associated with service policy breaches to appear?
Updated on 2011-12-15T00:09:33Z at 2011-12-15T00:09:33Z by SystemAdmin
Re: Why breached service policy not showing up as a runtime task?2011-12-14T18:41:19ZThis is the accepted answer. This is the accepted answer.ARFM alerts shown in the Runtime operations reports page do not produce runtime tasks. This is the reason why you are not seeing any runtime tasks. When APC decides it needs to start a new server based upon CPU demand, a runtime task will be created.
Re: Why breached service policy not showing up as a runtime task?2011-12-15T00:09:33ZThis is the accepted answer. This is the accepted answer.
- SystemAdmin 110000D4XK