As all Papertrail fans know, sending logs to Papertrail using syslog is quick and easy. Generating and transmitting syslog packets usually involves just 2 – 4 lines of code, and you can see your logs flowing into Papertrail in minutes. There are times, however, when you just can’t use syslog or install a remote_syslog2 daemon. This is where the new support for sending logs via HTTP comes in. And the best news is, it’s just as quick and easy to set up.

Isn’t all logging pretty much the same? Logs appear by default, like magic, without any further intervention by teams other than simply starting a system… right? While logging may seem like simple magic, there’s a lot to consider. Logs don’t just automatically appear for all levels of your architecture, and any logs that do automatically appear probably don’t have all of the details that you need to successfully understand what a system is doing.

In this tutorial, we will be using Heroku to deploy our Node.js application through CircleCI using Docker. We will set up Heroku Continuous Integration and Deployment (CI/CD) pipelines using Git as a single source of truth. Containerization allows developers to create and deploy applications faster with a wide range of other benefits like increased security, efficiency, agility to integrate with DevOps pipelines, portability, and scalability.

We’re excited to announce the first version release of our new dashboard framework: Dashboard (New). Built on top of a scalable, flexible, and extensible charting system, the new dashboards provide customers with deep control over their visuals, enable metadata rich workflows, and create dashboards in a dashboard first GUI.