Human friendly logging
This enhancement addresses issue #718. It will add logs for mere humans around instance monitoring, failure and scale events. Filter your logs for why:
$ convox logs --app=convox --filter=why --follow=false --since=2h
2016-06-13T20:23:41Z web:20160613194548-monitor/5a0c98f252bf who="EC2/ASG" what="Launching a new EC2 instance: i-a5f0bc3f" why="At 2016-06-13T20:23:03Z an instance was started in response to a difference between desired and actual capacity, increasing the capacity from 3 to 4."
2016-06-13T20:42:54Z agent:0.69/i-a5f0bc3f who="convox/agent" what="marked i-a5f0bc3f unhealthy" why="docker signal: killed"
2016-06-13T20:47:29Z web:20160613194548-monitor/a76ecf0a4d4d who="EC2/ASG" what="Launching a new EC2 instance: i-5a034cc0" why="At 2016-06-13T20:43:33Z an instance was started in response to a difference between desired and actual capacity, increasing the capacity from 2 to 3."
2016-06-13T21:11:47Z web:20160613194548-monitor/a76ecf0a4d4d who="convox/monitor" what="marked instance i-98f86904 unhealthy" why="ECS reported agent disconnected"
2016-06-13T21:12:29Z web:20160613194548-monitor/a76ecf0a4d4d who="EC2/ASG" what="Terminating EC2 instance: i-98f86904" why="At 2016-06-13T21:12:19Z an instance was taken out of service in response to a user health-check."
2016-06-13T21:17:29Z web:20160613194548-monitor/a76ecf0a4d4d who="EC2/ASG" what="Launching a new EC2 instance: i-319f0ead" why="At 2016-06-13T21:12:48Z an instance was started in response to a difference between desired and actual capacity, increasing the capacity from 2 to 3."
For more info see PR #759 - Human friendly logging about why instances are replaced
Improving convox ps reliability
The output of convox ps has been improved, with the goal being to give users accurate and reliable information about running processes. Especially during an application deployment.
For more information see PR #754 - Improving convox ps reliability