How to Set Up Grafana for Business KPI Monitoring

What Grafana Does for Business Metrics

Grafana is most often associated with DevOps teams monitoring server uptime, but the same tool works just as well for tracking revenue by week, monitoring trial-to-paid conversion rates, or watching churn in real time. The platform connects directly to SQL databases, runs your queries on a schedule, and renders the results as charts, gauges, or tables inside a browser-based dashboard. You write SQL; Grafana handles the visualization and refresh logic.

This guide covers Grafana Cloud, the hosted version. You do not need to install or manage a server. Setup takes under 30 minutes if your database is already accessible from the internet.

What You Need Before You Start

You will need three things: a Grafana Cloud account (free tier works), a PostgreSQL or MySQL database that accepts inbound connections from external IPs, and the connection credentials for that database. If your database only allows connections from within a private network, you will need to use a Grafana private data source connect agent, which the free tier supports with some configuration. This guide assumes a standard internet-accessible PostgreSQL database.

Grafana Cloud's free plan includes three active users, 10,000 series for metrics, 50 GB of log storage, and 14-day data retention for dashboards. For most small teams tracking a handful of KPIs, this is sufficient.

Step 1: Create Your Grafana Cloud Account

Go to grafana.com and click Start for free. Enter your email, choose a subdomain for your workspace (for example, yourcompany.grafana.net), and complete account creation. Grafana will send a confirmation email. After confirming, you land in the Grafana Cloud portal.

From the portal, click Launch in the Grafana section. This opens your Grafana instance, which is the main interface where you build dashboards and manage data sources.

Step 2: Add Your PostgreSQL Database as a Data Source

In the left sidebar, click Connections, then Add new connection. Type PostgreSQL in the search field and select the PostgreSQL data source from the results. Click Add new data source in the top right.

You will see a settings form. Fill in the following fields:

• Host: Your database host and port, for example db.yourcompany.com:5432
• Database: The name of the database you want to query
• User and Password: A read-only database user dedicated to Grafana (always create a read-only user rather than using admin credentials)
• TLS/SSL Mode: Set to require if your database uses SSL, which it should for any production database

Leave the other fields at their defaults. Click Save and test at the bottom. If Grafana returns a green confirmation that the database connection is working, your data source is ready.

Step 3: Write SQL Queries for Your Business Metrics

Grafana runs the SQL you write and maps the results to a visualization. For time-series charts, your query needs to return a timestamp column and a value column. For summary tables, any column structure works.

Here is an example query for a weekly revenue trend, assuming you have an orders table with a created_at timestamp and a revenue column:

SELECT
  date_trunc('week', created_at) AS week,
  SUM(revenue) AS total_revenue
FROM orders
WHERE created_at >= NOW() - INTERVAL '90 days'
GROUP BY week
ORDER BY week;

For conversion rate from trial to paid, assuming a users table with a signed_up_at column and a converted_at column that is null until conversion:

SELECT
  date_trunc('week', signed_up_at) AS cohort_week,
  COUNT(*) AS total_signups,
  COUNT(converted_at) AS conversions,
  ROUND(100.0 * COUNT(converted_at) / COUNT(*), 1) AS conversion_rate_pct
FROM users
WHERE signed_up_at >= NOW() - INTERVAL '12 weeks'
GROUP BY cohort_week
ORDER BY cohort_week;

Grafana also supports template variables, which let dashboard viewers filter by date range, region, or product without editing SQL directly. You define a variable once, reference it in queries with the $variable_name syntax, and Grafana renders a dropdown at the top of the dashboard.

Step 4: Build Your Dashboard

From the left sidebar, click Dashboards, then New, then New dashboard. Click Add visualization. Grafana asks which data source to use; select the PostgreSQL connection you configured in Step 2.

Paste your SQL query into the query editor. In the panel editor on the right, select the visualization type: Time series for trends over time, Stat for a single summary number (total revenue this month, for example), or Table for tabular data. Grafana renders a preview as you type.

Set a meaningful panel title, adjust the Y-axis units if needed (for example, set unit to Currency for revenue panels), and click Apply. Repeat this process for each KPI you want to track. Drag and resize panels on the dashboard canvas to arrange them into a layout that makes sense for your team.

Save the dashboard with a name and optional folder. Dashboards auto-refresh at an interval you control; a 5-minute refresh is appropriate for most business metrics.

Step 5: Set Alerts on KPI Thresholds

Grafana can send an alert when a metric crosses a threshold. In the panel editor, click the Alert tab. Click New alert rule. Define the condition: for example, alert when weekly revenue drops below $10,000. Choose an evaluation interval (every 5 minutes, for instance) and a pending period (how long the condition must be true before an alert fires, to avoid false positives on brief data gaps).

Grafana sends alerts through contact points. Go to Alerting in the left sidebar, then Contact points, and configure email, Slack, or PagerDuty. Map your alert rule to a contact point, and Grafana will notify your team automatically when a KPI falls out of range.

Practical Limits and What to Watch Out For

Grafana executes your SQL against your database every time a dashboard refreshes. On a 5-minute refresh with 10 panels, that is 10 queries every 5 minutes. For large tables without the right indexes, this can create meaningful load on your database. Add indexes on timestamp columns you filter frequently, and consider using materialized views or a read replica for Grafana queries if your database serves production traffic.

Grafana does not transform or store your data. It reads directly from your database on every query. If you need to reshape or aggregate data before it reaches Grafana, do that transformation in your database layer with a view or materialized view, not in the Grafana query editor.

The free tier limits dashboard history to 14 days. Longer retention requires a paid plan starting at around $299 per month for a team of ten.

If your data lives in spreadsheets or CSV exports rather than a live database, setting up Grafana adds overhead that may not be worth it. Tools designed for file-based analysis tend to be faster to get running in that case. VSLZ, for instance, lets you upload a CSV or connect a data source and get charts and summaries from a plain-English prompt, with no SQL required.

Summary

Grafana Cloud gives business teams a free, hosted path to live KPI dashboards backed by their existing SQL database. The setup involves creating an account, adding a PostgreSQL or MySQL data source with a read-only user, writing SQL queries for each metric, and building panels inside a browser-based editor. Alerts notify your team when a KPI moves outside an expected range. The main operational concern is database query load: index your timestamp columns and consider a read replica if Grafana queries compete with production traffic.