If you’re completely new to Heroku logging, be sure to read our guide for beginners.
TL;DR – Coralogix Heroku logging addon: https://elements.heroku.com/addons/coralogix
Coralogix has recently released a logging add-on that forwards all Heroku output to a Coralogix account that you specify.
Alternatively, you can use the CLI with:
heroku addons:create coralogix:test
Within a few seconds, any logs that your application generates will feed right into Coralogix, ready for using our high scale, high-speed search, and analytics. Here’s a basic example that shows that even with a small application generating simple log records, as soon it starts scaling, logs become hard to traverse and understand.
I started with one instance of each, then scaled to three instances. Here are the logs using
heroku logs on one instance.
Here’s an example of mixed logs with messages from Heroku, debug messages, and errors. It’s already getting confusing.
Throw in two more workers and tracking down the source of messages becomes even more confusing. The sample application has two applications running three workers each.
We can do this a lot more efficiently using Coralogix. To begin, open the dashboard page, or use the CLI and check the initial display right after you start sending logs:
After 24 hours, Coralogix’ Loggregation feature will kick in to automatically cluster log entries – which makes finding what you need faster and powers our ML-powered anomalies. In the screenshot below you can see that Loggregation has identified that despite being ‘random’, the CatAPI repeats itself a lot, outputting the same value over 1,000 times. In this case, it’s not important, but in a mission-critical application, this helps you identify patterns clearly.
Errors and broken flows are often introduced by new versions and application builds. The Coralogix Heroku integration includes integration to Heroku Pipelines and offers an automatic status for new Heroku builds (i.e. tags in Coralogix). Coralogix presents the suspicious and common errors introduced since that build as well as the alerts and anomalies which might be related to the new version release, thus allowing you to correlate issues to particular versions and points in time.
After 5 days of learning, Coralogix will start to send a daily report highlighting new anomalies (errors and critical messages), further helping you identify new errors, and not constantly bombard you with logging noise.
In addition to the machine learning aspect, Coralogix offers a complete set of logging capabilities, including Log Query, a centralized live tail, user-defined alerts to email or slack, and a fully hosted Kibana for data slicing and dashboards creation.
Provision the Coralogix addon and start enjoying 3rd generation Log analytics
Private space logging
You may configure your Heroku Shield Private Space to send logs to Coralogix by pointing the heroku log drain to the following URL:
When integrating Coralogix with a private space, the pre-packaged alerts, dashboard, and rules will be provided by Coralogix support. Please contact us through the support chat or send us an email.
How to find Heroku message from a specific app link
Attaching multiple apps to a single Coralogix account
You can add multiple apps to the same Coralogix account you created when provisioning your first Heroku app with the Coralogix add-on. All apps will have a unified billing and you will be able to filter by our tag of “application name”.
To attach multiple apps to the same Coralogix account using CLI, follow this link. Or from your Heroku dashboard: configure addons -> open details for Coralogix -> attach another app.
Removing your parent Heroku app, to which Coralogix was provisioned originally, will remove the Coralogix addon from all other apps that were attached to this Coralogix account in the past.