Heroku Blog

Logs tell the story of your app – a continuous, living stream of events, changes and behaviors. Logs let you rapidly identify and act on critical events, debug issues in your code, and analyze trends to make better decisions over time. But log management is increasingly complex. As apps scale across distributed infrastructure, many independent processes must be tracked and made sense of. Numerous components and backing services each produce their own log streams. Multiple developers may be collaborating on your app, and multiple services must consume its logs. And logs must be useful not only to machines and applications,…

On June 27th, our customer advocate team presented the first webcast in a two-part series on running production apps on Heroku. In case you missed it, the recording and slides are below. This first session is designed for an audience familiar with Heroku basics and covers: Production app setup and expectations App production checklist Using Unicorn to increase app performance Using 2X dynos to increase app performance How to configure timeouts to ensure app stability Using log-runtime-metrics for added visibility Running Production Apps on Heroku 6.27.13 from Abe Pursell Resources from the presentation: Log2viz Log-runtime-metrics Getting Started with Unicorn Follower…

Editor's Note: The version of Pipelines described in this blog post has been deprecated and replaced by a new non-labs implementation. Features added through Heroku Labs are experimental and may change or be removed without notice. heroku fork lets you create unique, running instances of existing applications in a single command, making it fast and simple to set up homogenous development, staging and production environments. But have you ever wished you could deploy directly from staging to a production app after testing and validation? Heroku pipelines, now an experimental feature available in Heroku Labs, lets you define the relationship between…

Heroku Add-ons are services exposed through the Heroku platform. They are managed by experts, provisioned and scaled in a single command, and consumed by your application as loosely coupled components. This post provides an overview of Add-ons for logging, persistence, caching and monitoring in production apps. Logging heroku addons:add papertrail Logs provide the foundation for trend analysis, error inspection, performance tuning and other processes critical for running production apps. Heroku routes and collates real-time logs from each part of your app, including running processes, system components, API events… even Add-ons themselves. Heroku presents app logs in a single stream of…

Heroku Fork has been deprecated. See the GitHub repo for the Fork CLI plugin for details. An application is more than source code – it’s executables, generated assets, runtime environments, dependencies, configuration, running processes, backing services and more. What if you could fork your entire app, not just your code? heroku fork lets you create unique, running instances of existing applications right from the command line. These instances are live and available on Heroku immediately so you can change, scale and share them however you want. How It Works You can fork apps you own and apps you’re collaborating on.…

Earlier this month, we quietly rolled out a new design for our monthly invoices. It's a breath of fresh air compared to the previous iteration, and we thought it would be interesting to share what goes into a design like this. At Heroku, billing is complex. Dyno hours are calculated to the second. Add-ons are calculated based on each provider’s pricing plan, which can be monthly or by usage depending on the add-on. There are support expenses, credits, free dyno hours, and packages. This all has to be wrangled into a format that not only makes sense for the back-end…