data-source/influxdb

34 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Plugin health check failed or 'error occurred within plugin' errors

When all InfluxDB panels return 'An error occurred within the plugin' or adding a new InfluxDB data source fails with 'Plugin health check failed', check for platform outages on the Grafana Cloud status page, verify authentication credentials haven't expired, wait a few minutes and retry Save & test for transient network issues, and check network connectivity between Grafana and InfluxDB.

Failed to connect to InfluxDB error solutions

When Grafana returns error messages 'error performing influxQL query', 'error performing flux query', or 'error performing sql query', verify the InfluxDB URL is correct and includes the protocol (http:// or https://), confirm InfluxDB is running and accessible, check the port is correct (default API port is 8086), ensure no firewall rules block the connection, and for Grafana Cloud configure Private data source connect (PDC) if InfluxDB is not publicly accessible.

PDC connection fails with 'no such host' error

When using Private data source connect (PDC) and receiving error 'socks connect tcp ... -> influxdb.host:8086: dial tcp: lookup ... no such host', do not use 127.0.0.1 or localhost as the InfluxDB URL because PDC tunnels traffic over a SOCKS proxy that cannot resolve loopback addresses. Use the machine's LAN IP address or a resolvable hostname instead, verify the hostname is resolvable from the network where the PDC agent is running, and check the Grafana Cloud status page for active incidents if the error appeared suddenly.

Request timeout errors when connecting to InfluxDB

When receiving error messages 'context deadline exceeded', 'request timeout', or 'dial tcp <IP>:<port>: i/o timeout', verify network connectivity from Grafana to InfluxDB including DNS resolution and firewall rules, confirm the InfluxDB host IP or hostname hasn't changed (especially after infrastructure migrations or Grafana upgrades), check network latency, verify InfluxDB is not overloaded, increase the timeout setting in data source configuration under Advanced HTTP Settings, and reduce the time range or query complexity.

401 Unauthorized authentication errors in InfluxDB

When receiving '401 Unauthorized' or 'authorization failed' errors, verify that the token or password is correct in the data source configuration, ensure Flux and SQL tokens have not expired, for InfluxQL with InfluxDB 2.x verify the token is set as an Authorization header with value 'Token <your-token>', for InfluxDB 1.x verify username and password are correct, and check that the token has required permissions to access the specified bucket or database.

403 Forbidden access denied errors in InfluxDB

When receiving '403 Forbidden' or 'access denied' errors, verify the token has read access to the specified bucket or database, check the token's permissions in the InfluxDB UI under API Tokens, ensure the organization ID is correct for Flux queries, and for InfluxQL with InfluxDB 2.x verify the DBRP mapping is configured correctly.

URL not configured error in InfluxDB data source

When receiving error 'missing URL from datasource configuration', open the data source configuration in Grafana and enter the full URL of the InfluxDB instance in the URL field including the protocol and port (for example, http://localhost:8086), then click Save & test to verify the connection.

InfluxDB version and query language configuration

For unknown influx version errors, verify that a valid query language is selected: Flux, InfluxQL, or SQL. For InfluxDB 1.x use InfluxQL (Flux is available from 1.8+ but InfluxQL is primary). For InfluxDB 2.x OSS/Cloud use Flux (InfluxQL is available via v1 compatibility API requiring DBRP mapping). For InfluxDB 3.x, Cloud Dedicated, or Cloud Serverless use SQL or InfluxQL (Flux is not supported). Each query language uses a different API endpoint; selecting the wrong language causes health checks and queries to fail.

Invalid data source info received error

When receiving 'invalid data source info received' error, the data source configuration is incomplete or corrupted. Delete and recreate the data source. Ensure all required fields are populated based on query language: Flux requires URL, Organization, Token, Default Bucket; InfluxQL requires URL, Database, User, Password; SQL requires URL, Database, Token.

DBRP mapping required for InfluxQL on InfluxDB 2.x

When receiving 'database not found' or queries return no data with InfluxQL on InfluxDB 2.x, InfluxQL queries require a Database and Retention Policy (DBRP) mapping. Create a DBRP mapping in InfluxDB using the CLI or API by referring to the InfluxDB documentation for Manage DBRP Mappings, and verify the database name in Grafana matches the DBRP mapping.

Browser access mode disabled error in InfluxDB

When receiving error 'Direct browser access in the InfluxDB datasource is no longer available. Switch to server access mode.', the data source is configured for direct browser access which is no longer supported. Open the data source configuration and change the access mode to Server (default), then click Save & test to verify.

Content Security Policy violation with InfluxDB plugin

When observing CSP violation errors in browser console referencing the InfluxDB plugin, net::ERR_ABORTED on proxy requests, or the plugin attempting direct browser-to-InfluxDB connections, you are running an outdated Grafana version. Browser access mode was removed in Grafana 9.2.0. Upgrade to Grafana 12.3.0 or later, then verify the data source access mode is set to Server (default).

Flux health check error 'error performing flux query'

When the health check query 'buckets()' fails with 'error performing flux query', verify the InfluxDB URL is correct and reachable, check that the token is valid and has not expired, and ensure the organization ID is correct.

Flux health check error 'error reading buckets'

When the buckets() query executes but returns error with message 'error reading buckets', verify the token has permission to list buckets and check that the organization ID matches the token's organization.

Flux health check error 'error getting flux query buckets'

When the buckets() query executes without error but returns no data with message 'error getting flux query buckets', verify the token has permission to list buckets, check that the organization ID is correct, and ensure InfluxDB is running and accessible.

InfluxQL health check error 'error performing influxQL query'

When the health check query 'SHOW MEASUREMENTS' fails with 'error performing influxQL query', verify the InfluxDB URL is correct and reachable, check the username and password (or token for InfluxDB 2.x), and verify the database name exists.

InfluxQL health check error 'error reading influxDB'

When the 'SHOW MEASUREMENTS' query executes but returns error with message 'error reading influxDB', verify the database name is correct, check that the user has permission to run SHOW MEASUREMENTS, and for InfluxDB 2.x verify DBRP mapping is configured.

InfluxQL health check error 'error connecting InfluxDB influxQL'

When the health check completes but the response cannot be processed with message 'error connecting InfluxDB influxQL', verify the database name is correct, check that the user has permission to run SHOW MEASUREMENTS, ensure the database exists and contains measurements, and for InfluxDB 2.x verify DBRP mapping is configured.

SQL health check error 'error performing sql query'

When the health check query 'select 1' fails with 'error performing sql query', verify the InfluxDB URL is correct (SQL health check connects via gRPC FlightSQL), check the token is valid and has required permissions, if using TLS verify certificate configuration and toggle Insecure Connection if connecting without TLS, and ensure the InfluxDB 3.x instance is running with accessible FlightSQL endpoint.

0 measurements found health check result

When health check returns message 'datasource is working. 0 measurements found', the connection is successful but the database contains no measurements. Verify you are connecting to the correct database, check that data has been written to the database, and if the database is new add some test data to verify the connection.

Query syntax error in InfluxDB

When receiving error messages 'error parsing query: found THING' or 'failed to parse query: found WERE, expected ; at line 1, char 38', check query syntax for typos or invalid keywords. For InfluxQL verify the query follows correct syntax: SELECT <field> FROM <measurement> WHERE <condition>. For SQL verify the query uses standard SQL syntax supported by InfluxDB 3.x, ensuring InfluxQL-specific syntax like GROUP BY time() is not used in SQL mode. For Flux ensure proper pipe-forward syntax and function calls. Test the query directly in the InfluxDB UI or CLI.

Query timeout limit exceeded error

When receiving 'query-timeout limit exceeded' error, reduce the time range of the query, add more specific filters to limit data scanned, increase the query timeout setting in InfluxDB if you have administrator access, and optimize the query to reduce complexity.

Too many series or data points error in InfluxDB

When receiving 'max-series-per-database limit exceeded' or 'A query returned too many data points and the results have been truncated', reduce the time range, add filters to limit series returned, increase the Max series setting in data source configuration under Advanced Database Settings, use aggregation functions to reduce data points, for SQL use $__dateBin(time) to aggregate into time buckets, and for Flux use aggregateWindow() to downsample data.

FlightSQL error codes and solutions

SQL (FlightSQL) backend errors prefixed with 'flightsql:' include: InvalidArgument (SQL query syntax is invalid - check query for syntax errors), PermissionDenied (token lacks access to requested resource - verify token has read access to database), NotFound (requested table or database doesn't exist - check database and table names in query), Unavailable (InfluxDB server unreachable - verify InfluxDB running and URL correct), Unauthenticated (token missing, invalid, or expired - update token in data source configuration).

No time column found error in InfluxDB queries

When receiving 'no time column found' error, the query result doesn't include a time column which is required for time-series visualization. Ensure the query includes a time field, for Flux verify the query includes _time in the output, for SQL ensure the query returns a timestamp column, and check that the time field is not being filtered out or excluded.

Query missing in annotation definition error

When an InfluxDB annotation returns 'Query missing in annotation definition', the annotation query field is empty. Navigate to the dashboard, click Edit, click the Dashboard options icon, expand Annotations section, select the InfluxDB annotation, click Open query editor, and enter a valid query in the InfluxQL Query field. The query must include WHERE $timeFilter, for example: SELECT title, description FROM events WHERE $timeFilter ORDER BY time ASC

Flux requires standard annotation query error

When a Flux data source returns 'Flux requires the standard annotation query', the data source is using the legacy InfluxQL annotation editor instead of the standard Flux query editor. Delete the existing annotation query, create a new annotation query selecting your Flux-configured InfluxDB data source, and write a Flux query returning data frames with time and text fields, for example: from(bucket: "events") |> range(start: v.timeRangeStart, stop: v.timeRangeStop) |> filter(fn: (r) => r["_measurement"] == "deployments")

Annotations not appearing on dashboard graph

When annotations are configured but not visible on the dashboard, verify the annotation query returns data by testing it in Explore, check the dashboard time range covers the annotation event time period, ensure the annotation toggle is enabled in the dashboard (check the annotation icon in top menu bar), for InfluxQL confirm the query includes WHERE $timeFilter, and if the query returns multiple columns verify the field mappings (Text, Tags, TimeEnd) are set correctly.

Data source was not found error

When dashboard panels display 'data source <UID> was not found' or manually re-running queries in the panel editor works after selecting the data source again, panels reference an old or deleted data source UID. This happens when a data source is deleted and recreated, since the new data source gets a different UID. Edit each affected panel and reselect the correct InfluxDB data source from the drop-down, click Apply to save each panel. To avoid this issue, update existing data sources instead of deleting and recreating them.

404 Not Found when sending Telegraf metrics to Grafana Cloud

When Telegraf writes to the Grafana Cloud InfluxDB-compatible endpoint and returns '404 Not Found', the Telegraf influxdb_v2 output plugin is not compatible with the Grafana Cloud metrics endpoint. This occurs when using PrivateLink or the standard InfluxDB-compatible write endpoint. Switch the Telegraf output plugin from influxdb_v2 to influxdb (v1) in the Telegraf configuration, ensure the endpoint URL and credentials match those shown in Grafana Cloud InfluxDB configuration page, and restart Telegraf after making the change.

Empty query results in InfluxDB

When queries return no data, verify the time range includes data in the database, check that measurement and field names are correct (for SQL, table names in InfluxDB 3.x are case-sensitive), test the query directly in the InfluxDB UI or CLI, ensure filters are not excluding all data, for SQL verify the $__timeFilter(time) macro is included so the query uses dashboard time range, and for InfluxQL verify the retention policy contains data for the selected time range.

Slow query performance in InfluxDB

When queries take a long time to execute, reduce the time range, add more specific filters to limit data scanned, increase the Min time interval setting to reduce data points, check InfluxDB server performance and resource utilization. For SQL use $__dateBin(time) with aggregation functions to downsample data and add WHERE clauses to narrow query scope. For Flux use aggregateWindow() to downsample data before visualization. Consider using continuous queries or tasks to pre-aggregate data.

Data appears delayed or missing recent points in InfluxDB

When the visualization doesn't show the most recent data, check the dashboard time range and refresh settings, verify the Min time interval is not set too high, ensure InfluxDB has finished writing the data, and check for clock synchronization issues between Grafana and InfluxDB.

Enable debug logging for InfluxDB troubleshooting

To capture detailed error information for troubleshooting, set the Grafana log level to debug in the configuration file under [log] section with level = debug. Review logs in /var/log/grafana/grafana.log (or your configured log location). Look for InfluxDB-specific entries that include request and response details. Reset the log level to info after troubleshooting to avoid excessive log volume.

Give your agent this brain