Paul Dix
@pauldix.bsky.social
Cofounder & CTO InfluxData, makers of InfluxDB, the open source time series database. Founder of NYC Machine Learning Meetup. Former Ruby on Rails developer and enthusiast (still a fan).
We realize that not all use cases will fit into what InfluxDB Core is able to do. It is meant to be scoped for data collection, processing, shipping, and query against short time ranges. It is constrained to this by technical limitations and architectural design.
January 29, 2025 at 7:22 PM
We realize that not all use cases will fit into what InfluxDB Core is able to do. It is meant to be scoped for data collection, processing, shipping, and query against short time ranges. It is constrained to this by technical limitations and architectural design.
You can configure the file limit to whatever you want it to be. 7 days is 980 files. If you have enough RAM, it'll work. It just won't be very fast. If that capability is vital to your use case, then you should consider another solution or becoming a customer of InfluxDB 3 Enterprise.
January 29, 2025 at 7:22 PM
You can configure the file limit to whatever you want it to be. 7 days is 980 files. If you have enough RAM, it'll work. It just won't be very fast. If that capability is vital to your use case, then you should consider another solution or becoming a customer of InfluxDB 3 Enterprise.
#InfluxDB 3 Core can now receive data from any time period and you'll be able to query any point in time. However, there is still a technical limitation to the range of time a single query will be able to process. I cover the technical details in the post.
January 27, 2025 at 7:17 PM
#InfluxDB 3 Core can now receive data from any time period and you'll be able to query any point in time. However, there is still a technical limitation to the range of time a single query will be able to process. I cover the technical details in the post.
We’ll be supporting v2 with security updates for quite some time. Years. We don’t currently have an EOL planned or set.
January 25, 2025 at 9:56 PM
We’ll be supporting v2 with security updates for quite some time. Years. We don’t currently have an EOL planned or set.
ah yes, sorry, busy couple of weeks. Responding now!
January 25, 2025 at 9:27 PM
ah yes, sorry, busy couple of weeks. Responding now!
Is your use case at work or home? We're looking at a free tier for Enterprise, which doesn't have this limitation. For Core, we realize that not all users of v1 and v2 will make the move as it doesn't do everything those do. But it offers features the previous versions don't. So some new audience
January 25, 2025 at 7:18 PM
Is your use case at work or home? We're looking at a free tier for Enterprise, which doesn't have this limitation. For Core, we realize that not all users of v1 and v2 will make the move as it doesn't do everything those do. But it offers features the previous versions don't. So some new audience
Of course, that's why I think we should be able to figure something out for the at-home use cases. Tailscale does a great job of this, I think we should be able to as well.
January 13, 2025 at 11:25 PM
Of course, that's why I think we should be able to figure something out for the at-home use cases. Tailscale does a great job of this, I think we should be able to as well.
For the hobbyist use case, we'll probably want to figure something out. For commercial use, we plan to sell the historical TSDB. Core is mean to be for recent data, which we hope is a use case that many people have and find it a great fit for.
January 13, 2025 at 5:34 PM
For the hobbyist use case, we'll probably want to figure something out. For commercial use, we plan to sell the historical TSDB. Core is mean to be for recent data, which we hope is a use case that many people have and find it a great fit for.
For at home use cases, we may do a freemium tier of the Enterprise server, which has the compactor, which is what is needed for longer time frames. The hobbyist use case is one we'd like to find a way to support for free.
January 13, 2025 at 4:28 PM
For at home use cases, we may do a freemium tier of the Enterprise server, which has the compactor, which is what is needed for longer time frames. The hobbyist use case is one we'd like to find a way to support for free.
What's your use case? We've seen many of our users and customers never query beyond 72h (many not even beyond 24h).
January 13, 2025 at 4:27 PM
What's your use case? We've seen many of our users and customers never query beyond 72h (many not even beyond 24h).
Pat Walsh is our new CMO, he might be the best to intro you to. Shoot me an email and I can forward onto him
January 13, 2025 at 3:12 PM
Pat Walsh is our new CMO, he might be the best to intro you to. Shoot me an email and I can forward onto him
You can also find us on the #InfluxDB community Discord: discord.gg/vZe2w2Ds8B
Join the InfluxDB Discord Server!
Check out the InfluxDB community on Discord - hang out with 26 other members and enjoy free voice and text chat.
discord.gg
January 13, 2025 at 3:10 PM
You can also find us on the #InfluxDB community Discord: discord.gg/vZe2w2Ds8B
You can find the #InfluxDB 3 Core getting started guide here: docs.influxdata.com/influxdb3/co...
InfluxDB 3 Core Documentation
InfluxDB 3 Core is an open source time series database designed and optimized for real-time and recent data (last 72 hours). Learn how to use and leverage InfluxDB 3 in use cases such as edge data col...
docs.influxdata.com
January 13, 2025 at 3:10 PM
You can find the #InfluxDB 3 Core getting started guide here: docs.influxdata.com/influxdb3/co...