Documentation Plugins Snowflake Troubleshooting

Troubleshoot Snowflake data source issues

This document provides solutions to common issues you may encounter when configuring or using the Snowflake data source. For configuration instructions, refer to Configure the Snowflake data source.

Authentication errors

These errors occur when credentials are invalid, missing, or don’t have the required permissions.

“Incorrect username or password”

Symptoms:

• Save & test fails with authentication errors
• Error message mentions incorrect credentials

Possible causes and solutions:

“Invalid private key”

Symptoms:

• Save & test fails when using Key Pair authentication
• Error message mentions private key issues

Solutions:

1. Verify the private key is unencrypted. The plugin does not support encrypted private keys.
2. Ensure the private key is in PEM format and includes the header and footer lines:
   Copy

   -----BEGIN RSA PRIVATE KEY-----
   ...
   -----END RSA PRIVATE KEY-----

3. Verify the corresponding public key is correctly configured in Snowflake for your user.
4. Regenerate the key pair if necessary. Refer to Snowflake Key Pair authentication.

“Role not granted to user”

Symptoms:

• Save & test fails with role-related errors
• Queries fail with permission errors

Solutions:

1. Verify the role is granted to the user:
   SQL Copy

   SHOW GRANTS TO USER <username>;

2. Grant the role if missing:
   SQL Copy

   GRANT ROLE <role_name> TO USER <username>;

3. If the role field is left empty, the user’s default role is used. Verify the default role has the necessary permissions.

Connection errors

These errors occur when Grafana cannot reach Snowflake endpoints.

“Connection refused” or timeout errors

Symptoms:

• Data source test times out
• Queries fail with network errors

Solutions:

1. Verify network connectivity from the Grafana server to Snowflake endpoints.
2. Check firewall rules allow outbound HTTPS (port 443) to *.snowflakecomputing.com.
3. Verify the Account field is correct, including region and platform if applicable.
4. For Grafana Cloud, ensure your Snowflake account allows connections from Grafana Cloud IP ranges.

“Invalid account identifier”

Symptoms:

• Save & test fails with account-related errors
• Error message mentions invalid account

Solutions:

1. Verify the account identifier format. The account name should be the entire string to the left of snowflakecomputing.com in your Snowflake URL.
2. Include the region if not in us-west-2. Example: xyz123.us-east-1
3. Include the platform if not on AWS. Example: xyz123.us-east-1.gcp or xyz123.east-us-2.azure

Query errors

These errors occur when executing queries against the data source.

“No data” or empty results

Symptoms:

• Query executes without error but returns no data
• Charts show “No data” message

Possible causes and solutions:

Query timeout

Symptoms:

• Query runs for a long time then fails
• Error mentions timeout or query limits

Solutions:

1. Narrow the time range to reduce data volume.
2. Add LIMIT clauses to reduce the result set.
3. Optimize your query with appropriate WHERE clauses.
4. Check if the Snowflake warehouse is suspended and needs to resume.
5. Consider using a larger warehouse size for complex queries.

“Object does not exist”

Symptoms:

• Error message mentions table, schema, or database not found

Solutions:

1. Verify the object name is spelled correctly.
2. Check that the database and schema are specified in your query or in the data source configuration.
3. Verify the user’s role has access to the object.
4. Object names in Snowflake are case-sensitive when quoted. Ensure consistent casing.

Template variable errors

These errors occur when using template variables with the data source.

Variables return no values

Solutions:

1. Verify the data source connection is working (test it in the data source settings).
2. Check that the variable query returns results when run directly in Snowflake.
3. Verify the user’s role has permissions to query the tables referenced in the variable query.
4. For cascading variables, ensure parent variables have valid selections.

Variables are slow to load

Solutions:

1. Set variable refresh to On dashboard load instead of On time range change.
2. Add LIMIT clauses to variable queries to reduce the number of returned values.
3. Use more specific WHERE clauses to filter variable results.

Enable debug logging

To capture detailed error information for troubleshooting:

1. Set the Grafana log level to debug in the configuration file:

   ini Copy

   [log]
   level = debug

2. Review logs in /var/log/grafana/grafana.log (or your configured log location).

3. Look for Snowflake-specific entries that include 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 above and still encounter issues:

1. Check the Grafana community forums for similar issues.
2. Review the Snowflake plugin GitHub issues for known bugs.
3. Consult the Snowflake documentation for service-specific guidance.
4. Contact Grafana Support if you’re a Grafana Cloud Pro, Cloud Contracted, or Enterprise customer.

When reporting issues, include:

• Grafana version
• Snowflake plugin version
• Error messages (redact sensitive information)
• Steps to reproduce
• Relevant configuration (redact credentials)