Troubleshoot the Vercel data source
This document provides solutions to common issues you might encounter when you configure or use the Vercel data source. The sections follow the order you typically move through when you set up the plugin: enabling and licensing it, keeping it up to date, authenticating, and running queries. For configuration instructions, refer to Configure the Vercel data source.
License and setup errors
The Vercel data source is a Grafana Enterprise plugin in public preview. Most setup problems occur because your account hasn’t licensed or enabled the plugin.
The plugin isn’t available or won’t install
Symptoms:
- The Vercel plugin doesn’t appear when you search the plugin catalog.
- The Install button is missing on the plugin page.
- Save & test returns a generic
Plugin health check failederror.
Possible causes and solutions:
Version and upgrade guidance
An outdated plugin version causes many Vercel data source issues. Before deeper troubleshooting, confirm you’re on the latest version, because upgrading resolves a wide range of problems.
Note
On Grafana Cloud, Grafana manages the Vercel plugin, and it updates automatically. On self-managed Grafana, you must update Enterprise plugins manually. In other managed environments, such as Azure Managed Grafana, the platform provider controls the plugin version, which can lag behind the latest release.
Check and update the plugin version
- Navigate to Connections > Plugins and data > Plugins.
- Search for the Vercel plugin and open its page.
- Review the installed version and the latest available version.
- If an update is available and you’re on self-managed Grafana, click Update.
Authentication errors
These errors occur when the access token is invalid, missing, or doesn’t have the required scope.
“invalid/empty bearer token”
Symptoms:
- Save & test fails with an authentication error.
- Queries return no data or an authorization error.
Possible causes and solutions:
Team-scoped token without a matching Team ID
Symptoms:
- Save & test fails, or queries return empty results even though data exists in Vercel.
Solutions:
- Confirm whether you scoped the token to a team on the Vercel account tokens page.
- If the token is team-scoped, enter the matching team in the Team ID field.
- Verify the Team ID matches the scope of the token, then select Save & test.
If Save & test succeeds but queries still return nothing, refer to Query errors.
Query errors
These errors occur after the connection succeeds but a query doesn’t return the results you expect.
“No data” or empty results
Symptoms:
- A query runs without error but returns no data.
- Panels show a No data message.
Possible causes and solutions:
Vercel runtime or application logs aren’t available
Symptoms:
- You expect application or request logs but only see deployment and build data.
- The log drain actions return drain configurations instead of log content.
Cause:
The Vercel data source queries the Vercel REST API, which exposes deployment, build, and configuration data. It doesn’t stream Vercel runtime or application logs.
Solution:
To bring runtime logs into Grafana, configure a Vercel log drain to forward logs to Loki, then query them with a Loki data source. This is a separate setup from the Vercel data source.
Enable debug logging
To capture detailed error information for troubleshooting:
Set the Grafana log level to
debugin the configuration file:[log] level = debugReview logs in
/var/log/grafana/grafana.log, or your configured log location.Look for entries related to the
grafana-vercel-datasourceplugin that include request and response details.Reset the log level to
infoafter troubleshooting to avoid excessive log volume.
Get additional help
If you’ve tried the solutions on this page and still encounter issues:
- Check the Grafana community forums for similar issues.
- Consult the Vercel REST API documentation for service-specific guidance.
- Create a support ticket through your Grafana Enterprise support channel. When you report an issue, include:
- Your Grafana version and Vercel plugin version.
- Error messages, with sensitive information redacted.
- Steps to reproduce the issue.
- Relevant configuration, with credentials redacted.


