---
title: "Instantaneous pulling and dashboard previews | Grafana Cloud documentation"
description: "Instructions for extending Git Sync for real-time notification and image rendering."
---

> For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt).

# Set up instantaneous pulling and dashboard previews in Pull Requests

> Note
> 
> **Git Sync is now GA for Grafana Cloud, OSS and Enterprise.** Refer to [Usage and performance limitations](/docs/grafana-cloud/as-code/observability-as-code/git-sync/usage-limits/) to understand usage limits for the different tiers.
> 
> [Contact Grafana](/help/) for support or to report any issues you encounter and help us improve this feature.

After [setup](/docs/grafana-cloud/as-code/observability-as-code/git-sync/git-sync-setup/), you can optionally extend Git Sync by enabling pull request notifications and image previews of dashboard changes.

Expand table

| Capability                                       | Benefit                                                           | Requires                               |
|--------------------------------------------------|-------------------------------------------------------------------|----------------------------------------|
| A table summarizing changes to your pull request | A convenient way to save changes back to GitHub                   | Webhooks configured                    |
| A dashboard preview image to a PR                | A snapshot of dashboard changes to a pull request outside Grafana | Image renderer and webhooks configured |

## Set up webhooks for real-time notification and pull request integration

Real-time notifications (or automatic pulling) is enabled and configured by default in Grafana Cloud.

In Grafana OSS/Enterprise, Git Sync uses webhooks to enable real-time updates from GitHub public repositories, or to enable pull request integrations. Without webhooks the polling interval is set during configuration, and is 60 seconds by default. You can set up webhooks with whichever service or tooling you prefer: Cloudflare Tunnels with a Cloudflare-managed domain, port-forwarding and DNS options, or a tool such as `ngrok`.

To set up webhooks:

1. Expose your Grafana instance to the public Internet.

<!--THE END-->

- Use port forwarding and DNS, a tool such as `ngrok`, or any other method you prefer.
- The permissions set in your GitHub access token provide the authorization for this communication.

<!--THE END-->

1. After you have the public URL, add it to your Grafana configuration file:

ini ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy

```ini
[server]
root_url = https://<PUBLIC_DOMAIN>
```

1. Replace *`<PUBLIC_DOMAIN>`* with your public domain.

To check the configured webhooks, go to **Administration &gt; General &gt; Provisioning** and click the **View** link for your GitHub repository.

> Note
> 
> If your `[server] root_url` must point at an internal address (for example, when Grafana runs behind a private ingress in a Kubernetes cluster), set the publicly-reachable URL with `[provisioning] public_root_url` instead. This URL is used both to register webhook callbacks with the Git provider and as the base for screenshot images embedded in pull-request comments, which the Git provider’s servers fetch from the public internet.
> 
> ini ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy
> 
> ```ini
> [server]
root_url = http://internal.cluster.local

[provisioning]
public_root_url = https://<PUBLIC_DOMAIN>
> ```
> 
> The per-repository `spec.webhook.baseUrl` field still overrides `public_root_url` for webhook registration; screenshot URLs always use `public_root_url` (or `root_url` when unset).

### Expose necessary paths only

If your security setup doesn’t permit publicly exposing the Grafana instance, you can either choose to allowlist the GitHub IP addresses, or expose only the necessary paths.

The necessary paths required to be exposed are, in RegExp:

- `/apis/provisioning\.grafana\.app/v0(alpha1)?/namespaces/[^/]+/repositories/[^/]+/(webhook|render/.*)$`

## Set up image rendering for dashboard previews

> Caution
> 
> Only available in Grafana OSS and Grafana Enterprise.

Set up image rendering to add visual previews of dashboard updates directly in pull requests. Image rendering also requires webhooks.

To enable this capability, install the Grafana Image Renderer in your Grafana instance. For more information and installation instructions, refer to the [Image Renderer service](https://github.com/grafana/grafana-image-renderer).

## Next steps

To learn more about using Git Sync refer to the following documents:

- [Set up Git Sync](/docs/grafana-cloud/as-code/observability-as-code/git-sync/git-sync-setup/)
- [Export resources](/docs/grafana-cloud/as-code/observability-as-code/git-sync/export-resources/)
- [Work with provisioned repositories](/docs/grafana-cloud/as-code/observability-as-code/git-sync/use-git-sync/)
- [Work with provisioned dashboards](/docs/grafana-cloud/as-code/observability-as-code/git-sync/provisioned-dashboards/)
- [Git Sync deployment scenarios](/docs/grafana-cloud/as-code/observability-as-code/git-sync/scenarios/)