--- title: "Troubleshoot Sentry data source issues | Grafana Plugins documentation" description: "Troubleshooting guide for the Sentry data source in Grafana." --- > For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt). # Troubleshoot Sentry data source issues This document provides solutions to common issues you may encounter when configuring or using the Sentry data source. For configuration instructions, refer to [Configure the Sentry data source](/docs/plugins/grafana-sentry-datasource/latest/configure/). ## Authentication errors These errors occur when the Sentry authentication token is invalid, missing, or doesn’t have the required permissions. ### “401 Unauthorized” or “Invalid token” **Symptoms:** - Save & test fails with authorization errors - Queries return access denied messages - Project and environment drop-downs don’t populate **Possible causes and solutions:** Expand table | Cause | Solution | |-------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| | Invalid or expired token | Generate a new authentication token in Sentry under **Settings** > **Developer Settings** > **Custom Integrations** and update the data source. | | Insufficient permissions | Verify the internal integration has **Read** permissions for **Project**, **Issue & Event**, and **Organization** in Sentry. | | Wrong organization slug | Verify the **Sentry Org** field matches the slug in your Sentry URL: `https://sentry.io/organizations/{slug}/`. | | Token created with wrong integration type | Ensure you created an **Internal Integration**, not a public integration. Only internal integrations generate auth tokens suitable for this plugin. | ### “0 projects found” on save and test **Symptoms:** - Save & test succeeds but reports “plugin health check successful. 0 projects found.” - No projects appear in the query editor drop-down **Solutions:** 1. Verify the authentication token’s integration has **Read** access to **Project** in Sentry. 2. Confirm the Sentry organization has at least one project. 3. Check that the **Sentry Org** slug matches the organization where projects exist. ## Connection errors These errors occur when Grafana can’t reach the Sentry API. ### “Connection refused” or timeout errors **Symptoms:** - Data source test times out - Queries fail with network errors **Possible causes and solutions:** Expand table | Cause | Solution | |----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Incorrect Sentry URL | Verify the **Sentry URL** field. For hosted Sentry, leave blank or use `https://sentry.io`. For self-hosted instances, enter your Sentry server URL. | | Firewall blocking outbound HTTPS | Ensure firewall rules allow outbound HTTPS (port 443) from the Grafana server to the Sentry API endpoint. | | Self-hosted TLS issues | For self-hosted Sentry with self-signed certificates, enable **Skip TLS Verify** in the data source’s additional settings. | | Network isolation | For Grafana Cloud accessing a private Sentry instance, configure [Private data source connect](/docs/grafana-cloud/connect-externally-hosted/private-data-source-connect/). | ## Query errors These errors occur when executing queries against Sentry. ### “No data” or empty results **Symptoms:** - Query executes without error but returns no data - Charts show “No data” message **Possible causes and solutions:** Expand table | Cause | Solution | |---------------------------------|----------------------------------------------------------------------------------------------------| | Time range doesn’t contain data | Expand the dashboard time range or verify data exists in Sentry for the selected period. | | Wrong project or environment | Verify you’ve selected the correct project and environment in the query editor. | | Query filter too restrictive | Simplify or remove the query filter to verify data exists, then refine the filter. | | Missing field permissions | Verify the authentication token has read access to the data type you’re querying (issues, events). | ### Query timeout **Symptoms:** - Query runs for a long time then fails - Error mentions timeout or rate limits **Solutions:** 1. Narrow the dashboard time range to reduce the volume of data returned. 2. Add project and environment filters to reduce the result set. 3. Reduce the **Limit** value in the query editor. 4. For Events Stats or Spans Stats queries, reduce the number of **Group** fields. ### “unknown query type” error **Symptoms:** - Query fails with the message “unknown query type” **Solutions:** 1. Select a valid query type in the **Query Type** drop-down. This error occurs when no query type is selected or the query configuration is corrupted. 2. If you’re using a query type added in a newer plugin version (for example, Spans requires v2.2.0+, Metrics requires v1.8.0+), update the plugin to the required version. ### “invalid or empty organization slug” error **Symptoms:** - Queries fail with “invalid or empty organization slug” - Save & test may still succeed **Solutions:** 1. Verify the **Sentry Org** field is set in the data source configuration. Refer to [Configure the Sentry data source](/docs/plugins/grafana-sentry-datasource/latest/configure/). 2. Check that the slug doesn’t contain extra spaces or the full URL — only enter the slug portion. ### “404” errors on span queries **Symptoms:** - Spans or Spans Stats queries return 404 errors - Other query types work correctly **Solutions:** 1. Ensure you’re running plugin version 2.2.4 or later, which includes a fix for 404 responses when querying spans with attribute aggregation. 2. Verify your Sentry plan includes access to the spans/tracing API. ### “400” errors with detail message **Symptoms:** - Query fails with a message like “400 Bad Request” followed by a detail message from Sentry (for example, “400 Bad Request Invalid query”) **Solutions:** 1. Review the detail message for specific guidance. Common causes include invalid search syntax in the **Query** field or unsupported field names in **Fields** or **Y-axis**. 2. Test the same query directly in Sentry’s Discover view to verify the syntax is valid. 3. For Events or Spans queries, verify the **Fields** values are valid Sentry field names. ## Annotation errors These errors occur when using Sentry annotations on dashboards. ### Annotations don’t appear **Symptoms:** - Annotation query is configured but no annotations appear on the graph - No error messages are displayed **Possible causes and solutions:** Expand table | Cause | Solution | |---------------------------------|----------------------------------------------------------------------------------------------------------------| | Time range doesn’t contain data | Expand the dashboard time range. Annotations only display for data within the visible time range. | | Query filter too restrictive | Simplify the **Query** filter or remove it temporarily to verify annotations appear. | | Wrong project or environment | Verify the correct project and environment are selected in the annotation query. | | Annotations disabled on panel | Verify annotations are enabled on the panel. Click the panel title and check that the annotation toggle is on. | ### Too many annotations **Symptoms:** - Dashboard is slow or cluttered with annotations - Browser performance degrades **Solutions:** 1. Set a lower **Limit** value in the annotation query to reduce the number of returned results. 2. Add a more specific **Query** filter (for example, `is:unresolved level:error`) to reduce the number of matching issues. 3. Filter by **Projects** or **Environments** to narrow the scope. ## Alerting errors These errors occur when using Grafana alerting with the Sentry data source. ### Alert rule fails to evaluate **Symptoms:** - Alert rule status shows “Error” - Alert notifications are not triggered **Possible causes and solutions:** Expand table | Cause | Solution | |------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Sentry API rate limits | Increase the evaluation interval to reduce the frequency of API calls. Avoid evaluating more frequently than every 5 minutes. | | Authentication token expired | Generate a new token and update the data source configuration. Refer to [Configure the Sentry data source](/docs/plugins/grafana-sentry-datasource/latest/configure/). | | Query returns no data | Verify the query returns data by running it in [Explore](/docs/grafana/latest/explore/) before creating an alert rule. | | Missing Reduce expression | Issues, Events, and Spans queries return tabular data. Add a **Reduce** expression (for example, **Count**) to produce a numeric value for the alert condition. | ### Alert condition not met despite matching data **Symptoms:** - Data appears in Explore but the alert doesn’t fire - Alert preview shows data but condition is never met **Solutions:** 1. Verify the **Reduce** function matches your intent. For example, **Last** returns the most recent value, while **Mean** averages all values in the evaluation window. 2. Check the **Threshold** expression operator and value. Preview the alert rule to see the actual values being compared. 3. For Issues queries, verify the **Limit** is set high enough to capture all matching issues, since the **Count** expression only counts returned rows. ## Template variable errors These errors occur when using template variables with the Sentry data source. ### Variables return no values **Solutions:** 1. Verify the data source connection is working by running **Save & test** in the data source settings. 2. For **Environments** variables, ensure the selected project IDs are valid and the projects have environments configured in Sentry. 3. For **Projects** variables filtered by team, verify the team slug is correct. 4. Check that the authentication token has **Read** permissions for the resources the variable queries. ### Variables are slow to load **Solutions:** 1. Set variable refresh to **On dashboard load** instead of **On time range change**. 2. For **Projects** variables, filter by team slug to reduce the number of results. ## Performance issues These issues relate to slow queries or Sentry API limits. ### API rate limit errors **Symptoms:** - “Rate limit exceeded” or throttling errors - Dashboard panels intermittently fail to load **Solutions:** 1. Reduce the frequency of dashboard auto-refresh. 2. Use larger time intervals in Stats queries to reduce the number of API calls. 3. Reduce the number of panels querying the same Sentry data source on a single dashboard. 4. Enable query caching in Grafana (available in Grafana Enterprise and Grafana Cloud). ## Enable debug logging To capture detailed error information for troubleshooting: 1. Set the Grafana log level to `debug` in the configuration file: ini ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```ini [log] level = debug ``` 2. Review logs in `/var/log/grafana/grafana.log` (or your configured log location). 3. Look for entries containing `sentry` for request and response details. 4. Reset the log level to `info` after troubleshooting to avoid excessive log volume. ## Get additional help If you’ve tried the solutions in this document and still encounter issues: 1. Check the [Grafana community forums](https://community.grafana.com/) for similar issues. 2. Review the [Sentry data source GitHub issues](https://github.com/grafana/sentry-datasource/issues) for known bugs. 3. Consult the [Sentry documentation](https://docs.sentry.io/) for Sentry-specific guidance. 4. Contact Grafana Support if you’re a Cloud Pro, Cloud Contracted, or Enterprise user. 5. When reporting issues, include: - Grafana version and Sentry plugin version - Error messages (redact sensitive information) - Steps to reproduce - Relevant configuration (redact credentials)