Here at Hipmob, we use Heroku for a number of different parts of our communication network. Using multiple loosely-coupled services simplifies scaling (which is handy when trying to providelive chat as a service to mobile apps), but (as with any distributed system with many moving parts) sometimes debugging can be a little challenging. Recently while trying to debug a customer issue we needed to be able to follow some data as it moved from our API service (implemented in NodeJS and deployed on Heroku) through our chat service (implemented in NodeJS and deployed on our own EC2 servers: Heroku, pretty please add Websocket support soon!) and then to our management service (implemented in Python and deployed on Heroku). After scuffling with multiple shell sessions and trying to visually synchronize our logging statements we decided it was finally time to actually investigate centralized logging.