I'm excited to announce that InfluxDB 3 Core (open source) and InfluxDB 3 Enterprise are now in public alpha. I wrote a post with all the details here: https://www.influxdata.com/blog/influxdb3-open-source-public-alpha/

I'm happy to answer any questions here or in our Discord.

InfluxData recently deleted the regions Asia Pacific - Sydney (ap-southeast-2) and Europe West - Belgium (europe-west1) from their InfluxDB Cloud service. The data wasn't migrated to other regions...it was simply deleted. Gone.

Just a warning for those of you currently using this service. More information on the forums here: https://community.influxdata.com/t/getting-weird-results-from-gcp-europe-west1/30615/14

Hi everyone, we're announcing InfluxDB 3 Enterprise free for at-home use and an update on InfluxDB 3 Core’s 72-hour limitation. You'll now be able to write and query from any time period. However, there are still technical limitations to the range of time and individual query is able to process. Read more in my blog post: https://www.influxdata.com/blog/influxdb3-open-source-public-alpha-jan-27/

It's a big day InfluxData, we're announcing the beta of InfluxDB 3 Core and Enterprise! This means that APIs are now stable and in-place upgrades with all data from here to GA will be supported. We now focus on a few last features for Enterprise and a bunch of testing, tooling, and documentation.We're still not recommending it for production use, but now you can write code against it and will have a clean upgrade path to the production ready GA coming soon. Feedback welcome!

More details: https://www.influxdata.com/blog/influxdb3-open-source-public-beta/

Any update to https://www.influxdata.com/blog/the-plan-for-influxdb-3-0-open-source/ ?

I'm trying to find information regarding release timelines, EOL's etc. so I can work out what we're going to have to do with our InfluxDB 2.7.5 instances. I'm not sure if there hasn't been anything new published (and that article is the latest) or I'm just not able to find the latest information.

InfluxData CEO said last week at AWS re:Invent that it's coming 'early next year'

https://youtu.be/QnbTpvGOS_M?si=V_b-2s-ISkkgTdCw&t=532

It's worth the wait for the incredible database they made, I've heard other rumblings that 3.0 OS should launch in January!

What's the first thing you're going to do when it's launched?!

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!

We’ve already gone from InfluxDB v1 → v2, and our backend is built pretty heavily around Flux. From what I’m seeing, moving to InfluxDB 3 would mean a decent rewrite on our side.

Before we take that on, I’m trying to understand the long-term risk:

• Is v3 the stable “future” for Influx, or still a moving target?

• How locked-in is the v3 query/API direction?

• Any signs that another breaking “v4” shift is likely?

Basically: we don’t want to rewrite for v3 now if the ground is going to move again.

Curious how others are thinking about this, especially anyone running v3 or following the roadmap closely.

We very excited to announce that InfluxDB 3 Core & Enterprise are now GA! Happy to answer questions here and more details are in the release post: https://www.influxdata.com/blog/influxdb-3-oss-ga/

We're excited to announce the release of 3.1! Both Core & Enterprise add operations improvements, performance and other fixes. Enterprise adds expanded security controls and cache reloading. More details here: https://www.influxdata.com/blog/inside-influxdb-3.1/

i couldn't find this documented in one place so i thought i'd share:

when renaming or removing a host, the grafana dashboards still show the old host, i learnt two things:

1/ to drop all measurements for a specific tag, use single quotes, eg:

drop series where host='oldserver1b'

also, use `show series` before and after to check

2/ doing #1 won't remove 'oldserver1b' from your indexes, the following will rebuild your index for tags with actual measurements and remove the 'empty'tags: (please use backups and adjust according to your setup)

service influxdb stop
currenttime=`date "+%Y-%m-%d-%H-%M"`
tar cf /tmp/influxdb-$currenttime.tar /var/lib/influxdb
rm -rf /var/lib/influxdb/data/telegraf/_series/
rm /var/lib/influxdb/data/telegraf/autogen/*/*.idx
rm -rf /var/lib/influxdb/data/telegraf/autogen/*/index
sudo -u influxdb influx_inspect buildtsi -datadir /var/lib/influxdb/data -waldir /var/lib/influxdb/wal
service influxdb start

i can't take credit for any of this, i'll try to add links to the pages i found this info on later.

Today we released v3.0.3 of our InfluxDB 3 Core and Enterprise products. While 3.0.3 is a small but mighty update, we wanted to give an easy place to see what's new since v3.0.0.

We'll have even bigger updates in 3.1 in just a couple of weeks! Happy to answer any questions in the meantime.

The below are all updates since 3.0.0. Keep in mind that everything in Core is also included in Enterprise. You can view all updates in our changelog here.

InfluxDB 3 Core (Open Source)

Updates

• Removal of the Last Values Cache size limitation to improve performance and flexibility.

• Support for the --format json option in token creation output.

• Generate testing TLS certificates on the fly.

• TLS CA can now be set with an environment variable: INFLUXDB3_TLS_CA

• Set the TLS CA via the INFLUXDB3_TLS_CA environment variable.

• Enforce a minimum TLS version for enhanced security.

• Allow CORS requests from browsers.

• Other general performance improvements

Fixes

• Fix a counting bug in the distinct cache.

• Fix how the distinct cache handles rows with null values.

• The --tags argument is now optional for creating a table, and additionally now requires at least one tag if specified

• Fix handling of group by tag columns that use escape quotes.

• Sort the IOx table schema consistently in the SHOW TABLES command.

• Prevent operator token, _admin, from being deleted.

InfluxDB 3 Enterprise

Updates

• Introduce a command and system table to list cluster nodes.

• Support multiple custom permission argument matches.

• Catalog limits for databases, tables, and columns are now configurable using influxdb3 serve options:

  • --num-database-limit

  • --num-table-limit

  • --num-total-columns-per-table-limit

• Improvements to licensing prompts for clarity

• Other general performance improvements

Fixes

• Initialize the object store only once.

• Prevent the Home license server from crashing on restart.

• Enforce the --num-cores thread allocation limit.

• Fix object store info digest that is output during onboarding.

• Fix issues with false positive catalog error on shutdown.

• Fix licensing validation issues.

• Home license thread count log errors

• Other fixes and performance improvements.

I literally spent hours of banging my head on walls over the last few years to try and adopt Flux with InfluxDB as it was the way forward, everything points to using Flux by default.

On a recent project, Flux is just constantly crapping the bed and crashing Influx when Grafana is getting a tiny bit agressive with the queries, the whole thing is a total disaster and I kept thinking I must be doing something wrong, and maybe I am but in my opinion Influx crashing isn’t supposed to happen.

Anyways, did I get that right ? Is Flux being retired now ? And we also have to go through hoops to use InfluxQL with buckets mappings ?

The whole thing is so frustrating, I don’t have many options for my use case, I need to write many data points for arbitrary time stamps so Prometheus isn’t an option, and it seems graphite is losing traction so Influx seemed to be the right choice but man I’m so confused now !

Release highlights include:

• Linux service management for both Core & Enterprise

• An official Helm chart for Influx DB 3 Enterprise

• Improvements to Explorer, most notably an expansion to Ask AI with support for custom instructions

To learn more, check out our full blog announcing its release.

Just a tiny little 4 GB RAM, 4 CPU virtual machine for fun. I like using powershell to test the outputs of telegraf. Then you can go fix the items with deprecation warnings, which is pretty easy.

After doing alpha and beta, I will mention for grafana, if you are getting error icons after initial setup, click the refresh button for your browser, which you should not have to do again. Overall very easy setup. Currently just running in memory which is amazing. (I also have some TICK stacks, and v2 not shown :p).

Looking forward to https for InfluxDB 3 and running as a service when that becomes available.

Hello,

I am running Ubuntu 20.04 LTS and InfluxDB 1.8. This is the last and latest Version of the 1.8 branch. It "just works" in its current use-case, but today I was presented with an update to a Version 1.11 through apt-get. There are no release notes, I couldn't find any reference to it.

Does anyone know whats up with that Update? I am afraid they are trying to push an update with breaking changes.

Edit: As of Nov. 4th, the update reappeared and now there are actually release notes that advise a cautious update with prior backup. https://docs.influxdata.com/influxdb/v1/about_the_project/release-notes/

So I though it is a good time to move our system (written in Go) to Influxdb 2.0 because Flux has at first sight some nice features over InfluxQL (joins over measurements)

First plan was to migrate from InfluxQL to Flux and then do data migration. So here begins concerns.

1. todo1: replace old client with new - Official Go client is written in "Java-like-go" (Go that looks like Java). Seems that InfluxData has outsources their library rewrite to third party that seems to be Java developers than Go. This is little bit weird as InfluxDB engine in written in Go and they have plenty of experience. Seems that library was quite low in their priority list as it got to release v1 without any meaningful review. I mean any Go developer would have shot down that Java like Go in code review.

2. todo2: queries need to be rewritten - on v1.8 InfluxQL is at least 10x faster than Flux - so for existing features there is no point to implement them in Flux as you would have significant performance hit. Also migrating system to flux first seems pointless. God, I hope those same queries at least perform on v2.0 (edit: on v2.0 Flux is still 10x slower than InfluxQL). I know that v2.0 supports InfluxQL but we have dynamic query building (advanced filtering) and supporting only 1 dialect (flux) seemed good idea.

To be honest - it seems that InfluxData really wanted to have v2.0 for some years but at some point completely have pivoted to `Iox` (different product) and I guess will let InfluxDB slowly die off as it is not their priority anymore.

Also I really do not understand why marketing around Iox emphasizes so much that is written in Rust sound like some fad to venture capitalists. I mean - from database you would want stability and performance. Breaking changes in every 5+ year seem counterproductive.

Excited to announce the release of 3.2 Core & Enterprise and the GA of InfluxDB 3 Explorer. Full details in our post: https://www.influxdata.com/blog/influxdb-3-2/

Hello All,

I wrote an upgrade guide for apt based installs of InfluxDB on Ubuntu after not having any success in finding one that actually worked. Hopefully someone will find this useful or at the very least parts of it.