This page provides you with instructions on how to extract data from Heroku and analyze it in Power BI. (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 Power BI?
Power BI is Microsoft’s business intelligence offering. It's a powerful platform that includes capabilities for data modeling, visualization, dashboarding, and collaboration. Many enterprises that use Microsoft's other products can get easy access to Power BI and choose it for its convenience, security, and power.
With high-value use cases across analysts, IT, business users, and developers, Power BI offers a comprehensive set of functionality that has consistently landed Microsoft in Gartner's "Leaders" quadrant for Business Intelligence.
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="18.104.22.168" 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="22.214.171.124" 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 126.96.36.199 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 Power BI
You can analyze any data in Power BI, as long as that data exists in a data warehouse that's connected to your Power BI account. The most common data warehouses include Amazon Redshift, Google BigQuery, and Snowflake. Microsoft also has its own data warehousing platform called Azure SQL Data Warehouse.
Connecting these data warehouses to Power BI is relatively simple. The Get Data menu in the Power BI interface allows you to import data from a number of sources, including static files and data warehouses. You'll find each of the warehouses mentioned above among the options in the Database list. The Power BI documentation provides more details on each.
Analyzing data in Power BI
In Power BI, each table in the data warehouse you connect is known as a dataset, and the analyses conducted on these datasets are known as reports. To create a report, use Power BI’s report editor, a visual interface for building and editing reports.
The report editor guides you through several selections in the course of building a report: the visualization type, fields being used in the report, filters being applied, any formatting you wish to apply, and additional analytics you may wish to layer onto your report, such as trendlines or averages. You can explore all of the features related to analyzing and tracking data in the Power BI documentation.
Once you've created a report, Power BI lets you share it with report "consumers" in your organization.
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 Power BI is to store that data inside a data warehousing platform alongside data from your other databases and third-party sources. You can find instructions for doing these extractions for leading warehouses on our sister sites Heroku to Redshift, Heroku to BigQuery, Heroku to Azure SQL Data Warehouse, Heroku to PostgreSQL, Heroku to Panoply, and Heroku to Snowflake.
Easier yet, however, is using a solution that does all that work for you. Products like Stitch were built to move data from Heroku to Power BI 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 Power BI.