This page provides you with instructions on how to extract data from Webhooks and analyze it in Grafana. (If the mechanics of extracting data from Webhooks 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 are webhooks?
A webhook is a way for one application to provide other applications with real-time information. Webhooks send data through user-defined HTTP POST callbacks, which means an application that uses webhooks can POST data when an event occurs to a specified endpoint (web address).
What is Grafana?
Grafana is an open source platform for time series analytics. It can run on-premises on all major operating systems or be hosted by Grafana Labs via GrafanaCloud. Grafana allows users to create, explore, and share dashboards to query, visualize, and alert on data.
Getting data out of webhooks
Different applications have different ways to set up webhooks. Often, you can use a management console to define the webhook and specify the endpoint to which you want data delivered. You must make sure that the specified endpoint exists on your server.
What does webhook data look like?
Webhooks post data to your specified endpoints in JSON format. It's up to you to parse the JSON objects and decide how to load them into your data warehouse.
Loading data into Grafana
Analyzing data in Grafana requires putting it into a format that Grafana can read. Grafana natively supports nine data sources, and offers plugins that provide access to more than 50 more. Generally, it's a good idea to move all your data into a data warehouse for analysis. MySQL, Microsoft SQL Server, and PostgreSQL are among the supported data sources, and because Amazon Redshift is built on PostgreSQL and Panoply is built on Redshift, those popular data warehouses are also supported. However, Snowflake and Google BigQuery are not currently supported.
Analyzing data in Grafana
Grafana provides a getting started guide that walks new users through the process of creating panels and dashboards. Panel data is powered by queries you build in Grafana's Query Editor. You can create graphs with as many metrics and series as you want. You can use variable strings within panel configuration to create template dashboards. Time ranges generally apply to an entire dashboard, but you can override them for individual panels.
Keeping data from webhooks up to date
Once you've set up the webhooks you want and have begun collecting data, you can relax – as long as everything continues to work correctly. You have to keep an eye on any changes your applications make to the data they deliver. You should also watch out for cases where your script doesn't recognize a new data type. And since you'll be responsible for maintaining your script, every time your users want slightly different information, you'll have to modify the script.
From Webhooks to your data warehouse: An easier solution
As mentioned earlier, the best practice for analyzing Webhooks data in Grafana 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 Webhooks to Redshift, Webhooks to BigQuery, Webhooks to Azure SQL Data Warehouse, Webhooks to PostgreSQL, Webhooks to Panoply, and Webhooks 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 Webhooks to Grafana automatically. With just a few clicks, Stitch starts extracting your Webhooks data via the API, structuring it in a way that's optimized for analysis, and inserting that data into a data warehouse that can be easily accessed and analyzed by Grafana.