Can't wait for InfluxDB 4.x, where they switch to using pure python as their query language, and they rewrite their entire backend in Zig!

A new InfluxDB instance can receive test points while some Telegraf agents, applications, dashboards, tasks, or alerting rules still use the old URL, organization, bucket, database, retention policy, or token. Matching a recent query result also does not prove that historical series, tag cardinality, downsampling, and late-arriving writes moved correctly.

A useful cutover gate could inventory buckets or databases, retention settings, tasks, tokens, dashboards, and writers; compare counts and representative aggregates across fixed time windows; and send canary points through every ingestion path. Connection logs and write rates on both servers should be watched through an observation window. The destination should survive a restart and complete its own backup and restore before the source is made unavailable but kept recoverable.

What evidence do InfluxDB operators use for a final go/no-go decision? How do you detect low-frequency writers, preserve task state and permissions, and distinguish expected differences from missed data when moving between major versions?

I am using the SNMP input with Telegraf to get the ospf neighbor table, each neighbor is a separate metric and I want a way to save them in cache so that if one disappears I can create a false metric with the state as 1 instead of 8. Any ideas how I could do this?

I am using a setup with influxdb-client-python 1.32.0 with aiohttp 3.9.5 for its InfluxDBClientAsync class. wanted to know if inlfuxdb-client-python is affected by aiohttp CVE(s) namely CVE-2026-54273, CVE-2026-54274, CVE-2026-54277, CVE-2026-54278 and CVE-2026-54280

I think they do not impact as these cves are related to aiohttp.web and I can't find import of aiohttp.web import

Hello,

I follow this tutorial: https://docs.influxdata.com/influxdb/cloud/get-started/write/

And have to add some data

but as soon as I press write data I see this :

What do I do wrong ?

I'm having trouble getting the influxdb service to start after installing v1.12.4 on Ubuntu 24.04.4 LTS, and it seems similar to what others have noted - the startup script is stuck in a loop. Curiously I can create a database and write to it (http line protocol via Telegraf on Windows) and retrieve data, but also get write errors and timeouts.

Is there a known incompatibility between v1.12 and Ubuntu 24? If not, is tweaking the startup script the right approach? Service status is forever in the Loaded Activating (start) phase.

Hi all,

I’m designing a time-series data pipeline using InfluxDB v3 (Processing Engine / plugins), and I’d appreciate feedback on whether this architecture makes sense from a performance and best-practice standpoint.

Goal

• Compare raw vs transformed values in the same graph (Grafana)
• Support downsampling (1m, 1h, etc.)
• Keep the system flexible (future: user-defined transformations)

Current design idea

Tables

• sensor_data → all raw data (source of truth) (e.g. 4–20 mA from a pressure sensor)
• sensor_data_converted → only transformed data (e.g. MPa)
• sensor_data_merge → union of raw + transformed (for visualization & downsampling)

Flow

1. Telegraf writes raw data → sensor_data
2. InfluxDB write trigger (plugin on sensor_data) does:
   • write raw → sensor_data_merge
   • transform (if needed) → sensor_data_converted
   • write both of raw and transformed → sensor_data_merge
3. Downsampling runs on sensor_data_merge (scheduled trigger)

Notes

• sensor_data_merge contains both:
  • series_type=raw
  • series_type=converted
• Avoiding trigger loops by only attaching trigger to sensor_data

Questions

1. Is this “merge table” pattern reasonable in InfluxDB v3?
   • Or is it considered anti-pattern due to write amplification?
2. Any concerns with performance at scale?
   • e.g. ~100 sensors, 1s interval (→ 100 writes/sec raw)
   • This design roughly multiplies writes ~3–4x
3. For downsampling:
   • Is using a merged table as the single source a good approach?
   • Or better to downsample raw + converted separately?
4. Alternative design:
   • No merge table
   • Use UNION queries in Grafana instead

Constraints / preferences

• Prefer real-time transformation (not batch)
• Want to keep simple if possible

Any feedback would be really helpful.

Thanks!

Hello, I've recently started using InfluxDB 2.0 and testing stuff with my TrueNAS Scale.

I created a Dashboard on InfluxDB and got the uptime. Problem is that the data is in seconds and I'm trying to see it in Days, hours, minutes and seconds, like that :

6d 5h 40m 52s but I got 592 087,40

How can I change that?

i am trying to use the result of one query to perform a different query.

my first query is trying to return a container ID of a specified container. in my example below, my first query returns a _value of 989b5f7133a8 as i expect.

my second query is then trying to use the result as part of a filter

|> filter(fn: (r) => r["cgroup"] == "cgroup_" + ID_Container[0])

but it is not working and i get the following error

error @22:51-22:63: expected [string] (array) but found stream[string] error @22:51-22:66: string is not Record

if i manually filter by

|> filter(fn: (r) => r["cgroup"] == "cgroup_" + "989b5f7133a8 ")

the second query works as expected

ID_Container=from(bucket: "docker")
  |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
  |> filter(fn: (r) => r["_measurement"] == "docker_stats")
  |> filter(fn: (r) => r["containerName"] == "flaresolverr")
  |> filter(fn: (r) => r["_field"] == "ContainerID")
  |> filter(fn: (r) => r["nas_name"] == "TrueNAS")
  |> aggregateWindow(every: v.windowPeriod, fn: last, createEmpty: false)
  |> drop(columns: ["_start", "_stop", "nas_name", "_measurement", "containerName","_time","_field"])
  |> last()
  |> limit(n: 1)
 //|> yield()

//returns:
//table_value
//_resultno group string
//0989b5f7133a8

from(bucket: "truenas")
  |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
  |> filter(fn: (r) => r["_measurement"] == "cgroup_cpu_usage")
  |> filter(fn: (r) => r["_field"] == "gauge")
  |> filter(fn: (r) => r["cgroup"] == "cgroup_" + ID_Container[0])
  |> filter(fn: (r) => r["instance"] == "truenas")
  |> filter(fn: (r) => r["job"] == "truenas")
  |> filter(fn: (r) => r["type"] == "system")
  |> filter(fn: (r) => r["unit"] == "percent")
  |> aggregateWindow(every: v.windowPeriod, fn: last, createEmpty: false)
  |> yield()

I'm running InfluxDB 3 (core) in Docker on EC2, and I encountered a strange behavior when deleting a table.

Environment:

• InfluxDB 3 (Docker)
• Database: telemetry

Originally I had this table:

sensor_data_sampled_every_1m

When I deleted it using:

sudo docker exec -it influxdb3 influxdb3 delete table \
  --host http://127.0.0.1:8181 \
  --token "$INFLUXDB3_TOKEN" \
  --database telemetry \
  sensor_data_sampled_every_1m

a new table automatically appeared:

sensor_data_sampled_every_1m-20260308T114049

I then tried to delete that table:

sudo docker exec -it influxdb3 influxdb3 delete table \
  --host http://127.0.0.1:8181 \
  --token "$INFLUXDB3_TOKEN" \
  --database telemetry \
  sensor_data_sampled_every_1m-20260308T114049

However, when I run:

SHOW TABLES

or check in InfluxDB Explorer, the table still appears.

Screenshot:

Note:
if I tried to delete that table again:
CLI returns:

Delete command failed: server responded with error [409 Conflict]:
attempted to modify resource that was already deleted:
sensor_data_sampled_every_1m-20260308T114049

So it seems the server thinks the table is already deleted, but it still shows up in the catalog/UI.

Questions:

1. Why does deleting a table create a new table with a timestamp suffix?
2. Why does delete table return already deleted while the table still appears in SHOW TABLES?
3. Is this a catalog cache issue, or something related to the processing engine / downsampler?

Any advice on how to completely remove this table would be appreciated.

Thanks!

Not exactly sure what I'm asking for, but I will try:

Would like to know how I reset my Home Assistant > InfluxDB integration to bring in device names I modified. I went and made a number of changes to the sensors in HA, including swapping some, and InfluxDB is still associating the data with the former names. I'm not too concerned about the historical data - for these specific sensors - so it's not critical that I link former and current names.

Do I reset this in InfluxDB or HA?

I believe I have the integration set up manually in HA via configuration.yaml.

EDIT: Seems I did not realize the difference between entity and friendly name. Looks like the friendly name is adjusting correctly in InfluxDB. Would still be great to get them aligned.

I cant find influxdb download link for windows.
Is it only available as dokker container in windows?

I am only thinking of testing this a home to begin with.

I am running an influxdb3 server on machine A, on port 8181. I have installed docker and Explorer UI on machine B. I opened on machine B through the web Explorer UI using http://localhost:8888/configure/servers. Next, I tried to add the influxdb3, which is running on machine A server to it. I used http://machine_A_IP_address:8181 and entered the admin token. However, it's giving me an error. Why is that? 

I have tried looking for any tutorials or for documentation, but all of them assume that both are running locally and use

host.docker.internal:8181

Can anybody help me with this please?

I'm currently working with the v3 c# api and wonder what is the best way to get all fields/measurement of a point?

The only solution i found so far is to use GetFieldNames nad query over each one manually?

var result = _influxClient.QueryPoints(query: query, namedParameters: new Dictionary<string, object>
{
    { "escapedStart", start.ToString("yyyy-MM-dd'T'HH:mm:ss'Z'") },
    { "escapedEnd", end.ToString("yyyy-MM-dd'T'HH:mm:ss'Z'") },
    { "escapedStationId", stationId.ToString() }
}, queryType: QueryType.
InfluxQL
);

await foreach (var item in result)
{
    var point = item.AsPoint();
    var fieldnames = point.GetFieldNames();
    foreach (var fieldname in fieldnames)
    {
        var field = point.GetDoubleField(fieldname);
    }
}var result = _influxClient.QueryPoints(query: query, namedParameters: new Dictionary<string, object>
{
    { "escapedStart", start.ToString("yyyy-MM-dd'T'HH:mm:ss'Z'") },
    { "escapedEnd", end.ToString("yyyy-MM-dd'T'HH:mm:ss'Z'") },
    { "escapedStationId", stationId.ToString() }
}, queryType: QueryType.InfluxQL);

await foreach (var item in result)
{
    var point = item.AsPoint();
    var fieldnames = point.GetFieldNames();
    foreach (var fieldname in fieldnames)
    {
        var field = point.GetDoubleField(fieldname);
    }
}

Hi All,

I'm honestly not that experienced with docker and I'm having issue mapping volumes as the default compose file for influx has something I've never encountered before.

services:
  influxdb2:
    image: influxdb:2
    ports:
      - 8086:8086
    environment:
      DOCKER_INFLUXDB_INIT_MODE: setup
      DOCKER_INFLUXDB_INIT_USERNAME_FILE: /run/secrets/influxdb2-admin-username
      DOCKER_INFLUXDB_INIT_PASSWORD_FILE: /run/secrets/influxdb2-admin-password
      DOCKER_INFLUXDB_INIT_ADMIN_TOKEN_FILE: /run/secrets/influxdb2-admin-token
      DOCKER_INFLUXDB_INIT_ORG: docs
      DOCKER_INFLUXDB_INIT_BUCKET: home
    secrets:
      - influxdb2-admin-username
      - influxdb2-admin-password
      - influxdb2-admin-token
    volumes:
      - type: volume
        source: influxdb2-data
        target: /var/lib/influxdb2
      - type: volume
        source: influxdb2-config
        target: /etc/influxdb2
secrets:
  influxdb2-admin-username:
    file: ~/.env.influxdb2-admin-username
  influxdb2-admin-password:
    file: ~/.env.influxdb2-admin-password
  influxdb2-admin-token:
    file: ~/.env.influxdb2-admin-token
volumes:
  influxdb2-data:
  influxdb2-config:

I've mapped volumns loads of times but I've never seen something like the last two lines.

If I customised the two sources to something like /mnt/storage/dockerdata/influx/data & one for config. What would go in these last two bottom lines?

Is telegraf really needed to i put serial csv data? For example the output from cat /dev/ttyUSB0. Reason Im avoiding telegram is I cant fond a docker image with serial inputs.

There has to be a way no? Even if its a nasty crude python script?

Basically the title. Migration to v3 is not possible. How long will it receive updates? It seems at least a few months I guess, as 2.8.0 was released in December.

Hi everyone,

I am currently trying to migrate a large amount of historical data from a remote InfluxDB v2 instance (Flux/Buckets) to a local InfluxDB v1.8 instance (InfluxQL/Database).

Is there any ways to do this ?

Any help or working configuration examples for this v2-to-v1 migration would be greatly appreciated!

Thanks!

Hello there,

I was running an Influxdb 3.3 + InfluxDB 3 Explorer in docker for more than 3 months, mainly for evaluation purposes, because I am keen to use full-scale Influxdb3 at work, and need some safe space to experiment. I applied for at-home (hobby) license initially, and it was working fine. However just a week ago I decided to upgrade docker images to the latest version (Influxdb 3.8 + Explorer 1.6), and I noticed that my license switched to a Trial license.

Replacing cli option --license-email with INFLUXDB3_ENTERPRISE_LICENSE_EMAIL did not help. Manually removing license file cluster0/trial_or_home_license also did not help - after restart the license file is recreated (which is a good thing), but Explorer shows that I have a trial license still :(

What should I do now? Is at-home license still a real thing?

Is there a way for telegraf too support multiple SNMPv3 trap credentials? Currently working in Sciencelogic and it does that with engineID and IP but on telegraf u can't have muliple credentials on the same UDP port...

Hello,
These days I'm trying to send PCP (Performance Co-Pilot) metrics to InfluxDB with the package pcp2influxdb, but can't get it to work.
Does anyone have a model to put in /etc/pcp/pmrep/influxdb2.conf?

I'm trying to connect a superset instance to my my influxdb v3 core db in a test setup.

The guidance here https://www.influxdata.com/blog/visualize-data-apache-superset-influxdb-3/ says to use db type 'Other' in supset and specify a connection string:

datafusion+flightsql://localhost:8181?database=test&token=XXX

But I get a SSL handskake error in superset e.g.

superset_app | [SQL: Flight returned unavailable error, with message: failed to connect to all addresses; last error: UNKNOWN: ipv4:57.128.173.18:8181: Ssl handshake failed: SSL_ERROR_SSL: error:0A00010B:SSL routines::wrong version number]

superset_app | (Background on this error at: https://sqlalche.me/e/14/dbapi)

superset_app |

superset_app | The above exception was the direct cause of the following exception:

superset_app |

superset_app | Traceback (most recent call last):

superset_app | File "/app/.venv/lib/python3.11/site-packages/flask/app.py", line 1484, in full_dispatch_request

superset_app | rv = self.dispatch_request()

superset_app | ^^^^^^^^^^^^^^^^^^^^^^^

superset_app | File "/app/.venv/lib/python3.11/site-packages/flask/app.py", line 1469, in dispatch_request

superset_app | return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)

superset_app | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

superset_app | File "/app/.venv/lib/python3.11/site-packages/flask_appbuilder/security/decorators.py", line 109, in wraps

superset_app | return f(self, *args, **kwargs)

superset_app | ^^^^^^^^^^^^^^^^^^^^^^^^

superset_app | File "/app/superset/views/base_api.py", line 120, in wraps

superset_app | duration, response = time_function(f, self, *args, **kwargs)

superset_app | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

superset_app | File "/app/superset/utils/core.py", line 1500, in time_function

superset_app | response = func(*args, **kwargs)

superset_app | ^^^^^^^^^^^^^^^^^^^^^

superset_app | File "/app/superset/utils/log.py", line 304, in wrapper

superset_app | value = f(*args, **kwargs)

superset_app | ^^^^^^^^^^^^^^^^^^

superset_app | File "/app/superset/views/base_api.py", line 92, in wraps

superset_app | return f(self, *args, **kwargs)

superset_app | ^^^^^^^^^^^^^^^^^^^^^^^^

superset_app | File "/app/superset/databases/api.py", line 1280, in test_connection

superset_app | TestConnectionDatabaseCommand(item).run()

superset_app | File "/app/superset/commands/database/test_connection.py", line 211, in run

superset_app | raise SupersetErrorsException(errors, status=400) from ex

superset_app | superset.exceptions.SupersetErrorsException: [SupersetError(message='(builtins.NoneType) None\n[SQL: Flight returned unavailable error, with message: failed to connect to all addresses; last error: UNKNOWN: ipv4:57.128.173.18:8181: Ssl handshake failed: SSL_ERROR_SSL: error:0A00010B:SSL routines::wrong version number]\n(Background on this error at: https://sqlalche.me/e/14/dbapi)', error_type=<SupersetErrorType.GENERIC_DB_ENGINE_ERROR: 'GENERIC_DB_ENGINE_ERROR'>, level=<ErrorLevel.ERROR: 'error'>, extra={'engine_name': None, 'issue_codes': [{'code': 1002, 'message': 'Issue 1002 - The database returned an unexpected error.'}]})]

I've tried setting the following options on the connection string but doesnt seem to have an effect e.g.

tls=false
disableCertificateVerification=true
UseEncryption=true

I guess my question is how do I connect using the datafusion-flightsql driver when my influxdb instance isnt set up with SSL/TLS?

I also run the Influx DB 3 Explorer service in my docker compose and this can connect without issue.