@Paroles_Paroles InfluxDB 3 Core has a 72 hour query limit, but it does not delete data older than 72 hours. That data still persists. InfluxDB Core’s focus is on real-time and recent data and does not include a compaction service (compactor). Queries against uncompacted data are slower the more data a query loads, so the 72 hour query limit was introduced. The compactor optimizes aging Parquet by combining and “compressing” them and also makes querying historical Parquet files more performant, with the cost of additional overhead to run the compactor.
With that said, this is an alpha and things could change. InfluxDB 3 Core doesn’t delete data older than 72 hours. All data is stored in Apache Parquet format, so you could still access that data using other tools that can query Parquet. But those Parquet files are not compacted. If you were to upgrade to InfluxDB 3 Enterprise, you could then query all of your written data and the compaction service included with Enterprise would begin compacting your historical data.
HI @scott,
When we mention a query limit of 72 hours, does that mean we can only query 72 hours’ worth of data at a time?
Currently, we are using InfluxDB version 2.7. If we plan to upgrade to InfluxDB 3.0 and perform historical queries, are we required to upgrade to the Enterprise version?
No, it means you can’t query data older than 72 hours with InfluxDB 3 Core. For historical queries, you will have to upgrade to InfluxDB 3 Enterprise.
There has been discussion around offering a personal/hobbyist Enterprise license that would give you data compaction, enable historical queries, and possibly grant access to other Enterprise-specific functionality. I don’t have any other details because it’s just been discussion and we’re still in alpha.
I’m a bit confused with all the product names of Influxdb3. (Core, Enterprise, Edge, Community …) Are the advantages/disadvantages of the individual versions known and what the development plans are?
I would also like to know, as the 72 hours in the Core version are not enough for me, how much the Enterprise version will cost later or whether it is better for private users to wait for the Edge/Community version - should it still be available!? Many thanks
@Tundril “Edge,” “Community,” and “Pro” were all working names for the this particular architecture of InfluxDB 3. Community was ultimately dropped and “Edge” was named “Core” and “Pro” was named “Enterprise”.
So the full InfluxDB 3 line of products looks like this:
InfluxDB 3 Core: OSS, real-time or recent data engine, run by a single service
InfluxDB 3 Enterprise: Commercial, real-time, recent, or historical data engine, run by a single process, HA-capable
InfluxDB Clustered: Commercial, self-managed, distributed architecture, designed large write and query workloads on your own infrastructure
InfluxDB Cloud Serverless: Commercial, fully-managed, multi-tenant, distributed architecture, best for small to medium workloads
InfluxDB Cloud Dedicated: Commercial, fully-managed, single-tenant, distributed architecture, designed for large write and query workloads
Pricing is still being finalized, but more information should be available as we prepare for general availability.
The “Community” version is no longer planned, but, as mentioned above, there has been discussion about offering a personal/hobbyist license for InfluxDB 3 Enterprise. No concrete decisions have been made yet since we’re still in early alpha, but it is being considered.
If this 72hour restriction stays and no other hobby/personal edition is offered, most of these users will stay at version 2 or have to look for other option in the market.
You would kill this community, which so far have heavily supported and advertised InfluxDB
First, I have to say I really appreciate the clear separation between OSS and not OSS. Too many companies start as OSS and then end up with conflicts of interest between their OSS stuff and their enterprise stuff. So seeing how you’re doing it is something new for me, and I like it a lot.
That said… I’ve been trying to get a decent monitoring, alerting, and metrics/logs aggregation, tool working at my workplace for years. I thought I was mostly there with a certain other stack, but some things changed that mean we just don’t have the resources (hardware or money) for it.
So I started experimenting with InfluxDB2/Telegraf/Vector/Grafana. At this point I think it will work, but the new info about Core’s 72hr limit gives me pause.
It sounds like the limit is partially to keep queries fast, right? And you’re targeting Core at immediate, mostly real-time, data. Which means they need to be fast. So for the stated purpose of Core, I can’t see it making sense to change that.
What I need is a single node that I can push logs and metrics, query for data, and store as much data as I have the space for. Short term queries, like for the past 30min, need to be fast so I can alert on it, but beyond that speed isn’t really a concern. It’s not mission critical data, so no need for redundancy. The only “enterprise” feature I’d say I’d need is SSO. (IMO, we are far past SSO being just for enterprises, I use it for my personal stuff, and it should just be standard practice in 2025.)
I guess I’ll just end with this: There is a need for long term metric/log aggregation in organizations that can’t afford enterprise level products. So far I have yet to find a solution for that problem. Everything always requires more server resources that we can handle, or has needed (basic) features behind a paywall that is too high. I’d love to see InfluxDB figure out how to fill that need.
In short, the 72-hour restriction has been loosened, but still exists on the query side. Let me explain. InfluxDB 3 Core now allows you to write data from any time period, not just the last 72 hours. We’ve also exposed a new query-file-limit configuration option that lets you set a custom limit for how many Parquet files a query can access. Using the default InfluxDB 3 Core settings, it’s up to 72 hours (both recent and historical data). You can increase this limit, but there are side-effects (see the docs).
Thank you for all the feedback you have provided and continue to provide. We’re listening .
Hello,
The InfluxDB V3 Core news was pretty bad on my side. It is sure at 100% that the current usage I do of InfluxDB V2 is not comparable with the usage I would do of V3 Core and I guess most part of enthusiast home users are/will be in that same situation. Other than remaining indefinitely on V2 OSS, the other option to keep at least the features of V2 OSS would be V3 Enterprise.
So I read the blog post already mentioned here, but I probably missed some points; please apologize me but I am not Anglo/American.
In the blog post it has been said that:
For the users in category 1, we’re announcing a free tier of InfluxDB 3 Enterprise for at-home, non-commercial use. It will be rate limited in some way, but our intention is to give a free option with all the capabilities of Enterprise for these at-home users
First.
It reads “free tier”, which i interpretate as no-cost, free-of-charge, no-fees, am I right? Otherwise “free” would be really misleading in point of view.
At the same time it reads “…will be rate limited…”, which I do not understand at all: could you explain better the scenario?
Second.
Despite the invite to join you at Discord for whom are interested into the Enteprise version, I could not understand if this option to upgrade is subject to any limitations decided by you, is subject to a quality assessment done by you based on the usage a home user will do, or anything else.
Again, I am not a native English spoke person, but I am a little bit confused right now.