Topic
  • 2 replies
  • Latest Post - ‏2011-12-15T00:09:33Z by SystemAdmin
SystemAdmin
SystemAdmin
102 Posts

Pinned topic Why breached service policy not showing up as a runtime task?

‏2011-12-08T00:41:18Z |
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
  • SystemAdmin
    SystemAdmin
    102 Posts

    Re: Why breached service policy not showing up as a runtime task?

    ‏2011-12-14T18:41:19Z  
    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.
  • SystemAdmin
    SystemAdmin
    102 Posts

    Re: Why breached service policy not showing up as a runtime task?

    ‏2011-12-15T00:09:33Z  
    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.
    The service policy configuration page contains a time value entry that has the following description: "Specifies the allowable amount of time the service policy goal can be breached before a runtime task is created". Please correct me or confirm what my understanding is here... If you want to have the APC provision another server - generate a runtime task event that indicates a service policy breach, two things need to happen: (1) The service policy is breached and (2) The CPU utilization configured in the ARFM (Maximum CPU usage) has been exceeded. This would also mean that the service policy should be configured as the maximum service time based on the CPU configuration in the ARFM.