+1 informative logs are helpful to find causes for issues On 23 Feb 2015 22:36, "Lahiru Sandaruwan" <[email protected]> wrote:
> Agree. We need to increase the information at this log. We have a lot of > places to increase the level of information in logs, and fixed some lately. > > Thanks. > > On Mon, Feb 23, 2015 at 9:29 PM, Imesh Gunaratne <[email protected]> wrote: > >> Hi Devs, >> >> I think we need to do $subject, current I only see the below logs when >> taking a scaling up decision: >> >> [2015-02-23 20:55:35,782] INFO >> {org.apache.stratos.autoscaler.monitor.cluster.ClusterMonitor} - Executing >> scaling rule as statistics have been reset >> [2015-02-23 20:55:35,801] INFO >> {org.apache.stratos.autoscaler.rule.RuleLog} - [scale-up] Partition >> available, hence trying to spawn an instance to scale up! >> >> IMO this info message is not correct. We do not need to scale up just >> because there is a partition available. >> >> [2015-02-23 20:55:35,803] INFO >> {org.apache.stratos.autoscaler.client.CloudControllerClient} - Trying to >> spawn an instance via cloud controller: [cluster] tomcat-1.tomcat.domain >> [partition] partition-1 [network-partition-id] network-partition-1 >> [2015-02-23 20:55:35,819] INFO >> {org.apache.stratos.cloud.controller.iaases.kubernetes.KubernetesIaas} - >> Starting container: [application] tomcat [cartridge] tomcat [member] >> tomcat-1.tomcat.domain4dd97cbc-0a4d-40f9-b01a-894b3b27d6e8 >> >> Thanks >> >> >> -- >> Imesh Gunaratne >> >> Technical Lead, WSO2 >> Committer & PMC Member, Apache Stratos >> > > > > -- > -- > Lahiru Sandaruwan > Committer and PMC member, Apache Stratos, > Senior Software Engineer, > WSO2 Inc., http://wso2.com > lean.enterprise.middleware > > email: [email protected] blog: http://lahiruwrites.blogspot.com/ > linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 > >
