This page provides you with instructions on how to extract data from Heroku and analyze it in Looker. (If the mechanics of extracting data from Heroku seem too complex or difficult to maintain, check out Stitch, which can do all the heavy lifting for you in just a few clicks.)
What is Heroku?
Heroku is a cloud platform that lets companies build, deploy, monitor, and scale apps.
What is Looker?
Looker is a powerful, modern business intelligence platform that has become the new standard for how modern enterprises analyze their data. From large corporations to agile startups, savvy companies can leverage Looker's analysis capabilities to monitor the health of their businesses and make more data-driven decisions.
Looker is differentiated from other BI and analysis platforms for a number of reasons. Most notable is the use of LookML, a proprietary language for describing dimensions, aggregates, calculations, and data relationships in a SQL database. LookML enables organizations to abstract the query logic behind their analyses from the content of their reports, making their analytics easy to manage, evolve, and scale.
Getting data out of Heroku
You can extract the data you want from Heroku's servers using the Heroku API. A common use case for extracting Heroku data is retrieving server logs or other event logs. There are some API endpoints related to logs, as well as command-line tools like the logs command that let you retrieve this data.
Sample Heroku data
Here's an example set of commands and responses you might see when interacting with the
logs command-line tool.
$ heroku logs --ps router 2012-02-07T09:43:06.123456+00:00 heroku[router]: at=info method=GET path="/stylesheets/dev-center/library.css" host=devcenter.heroku.com fwd="220.127.116.11" dyno=web.5 connect=1ms service=18ms status=200 bytes=13 2012-02-07T09:43:06.123456+00:00 heroku[router]: at=info method=GET path="/articles/bundler" host=devcenter.heroku.com fwd="18.104.22.168" dyno=web.6 connect=1ms service=18ms status=200 bytes=20375 $ heroku logs --source app 2012-02-07T09:45:47.123456+00:00 app[web.1]: Rendered shared/_search.html.erb (1.0ms) 2012-02-07T09:45:47.123456+00:00 app[web.1]: Completed 200 OK in 83ms (Views: 48.7ms | ActiveRecord: 32.2ms) 2012-02-07T09:45:47.123456+00:00 app[worker.1]: [Worker(host:465cf64e-61c8-46d3-b480-362bfd4ecff9 pid:1)] 1 jobs processed at 23.0330 j/s, 0 failed ... 2012-02-07T09:46:01.123456+00:00 app[web.6]: Started GET "/articles/buildpacks" for 22.214.171.124 at 2012-02-07 09:46:01 +0000 $ heroku logs --source app --ps worker 2012-02-07T09:47:59.123456+00:00 app[worker.1]: [Worker(host:260cf64e-61c8-46d3-b480-362bfd4ecff9 pid:1)] Article#record_view_without_delay completed after 0.0221 2012-02-07T09:47:59.123456+00:00 app[worker.1]: [Worker(host:260cf64e-61c8-46d3-b480-362bfd4ecff9 pid:1)] 5 jobs processed at 31.6842 j/s, 0 failed ...
Preparing Heroku data
This part could be the trickiest: you need to map the data that comes out of each Heroku API endpoint or log extraction into a schema that can be inserted into your destination database. This means that, for each value in the response, you need to identify a predefined datatype (i.e. INTEGER, DATETIME, etc.) and build a table that can receive them. Depending on your log files, you may also opt to break those up into raw logs and more meaningful metadata or log portions.
The Heroku API documentation can give you a good sense of what fields will be provided by each endpoint, along with their corresponding datatypes.
Loading Data into Looker
To perform its analyses, Looker connects to your company's database or data warehouse, where the data you want to analyze is stored. Some popular data warehouses include Amazon Redshift, Google BigQuery, and Snowflake.
Looker's documentation offers instructions on how to configure and connect your data warehouse. In most cases, it's simply a matter of creating and copying access credentials, which may include a username, password, and server information. You can then move data from your various data sources into your data warehouse for Looker to use.
Analyzing Data in Looker
Once your data warehouse is connected to Looker, you can build constructs known as explores, each of which is a SQL view containing a specific set of data for analysis. An example might be "orders" or "customers."
Once you've selected any given explore, you can filter data based on any column available in the view, group data based on certain fields in the view (known as dimensions), calculate outputs such as sums and counts (known as measures), and pick a visualization type such as a bar chart, pie chart, map, or bubble chart.
Beyond this simple use case, Looker offers a broad universe of functionality that allows you to conduct analyses and share them with your organization. You can get started with this walkthrough in Looker's documentation.
Keeping Heroku data up to date
At this point you've coded up a script or written a program to get the data you want and successfully moved it into your data warehouse. But how will you load new or updated data? It's not a good idea to replicate all of your data each time you have updated records. That process would be painfully slow and resource-intensive.
Instead, identify key fields that your script can use to bookmark its progression through the data and use to pick up where it left off as it looks for updated data. Auto-incrementing fields such as updated_at or created_at work best for this. When you've built in this functionality, you can set up your script as a cron job or continuous loop to get new data as it appears in Heroku.
And remember, as with any code, once you write it, you have to maintain it. If Heroku modifies its API, or the API sends a field with a datatype your code doesn't recognize, you may have to modify the script. If your users want slightly different information, you definitely will have to.
From Heroku to your data warehouse: An easier solution
As mentioned earlier, the best practice for analyzing Heroku data in Looker is to store that data inside a data warehousing platform alongside data from your other databases and 3rd party sources. You can find instructions for doing these extractions for leading warehouses on our sister sites Heroku to Redshift, Heroku to BigQuery, and Heroku to Snowflake.
Easier yet, however, is using a solution that does all that work for you. Products like Stitch were built to solve this problem automatically. With just a few clicks, Stitch starts extracting your Heroku data via the API, structuring it in a way that is optimized for analysis, and inserting that data into a data warehouse that can be easily accessed and analyzed by Looker.