[new-product] InfluxDB #7303
[new-product] InfluxDB #7303
Conversation
|
I made some slight changes. It seems like this is using the commercial support policy and applying that on the open-source product, which doesn't seem right. The upstream states:
But then the support program doc also doesn't mention any security backports or patches, merely SLAs about response and severity levels (none of which mention security). There is also influxdata/influxdb#25045 issue, which I've linked which states v1 as still supported maybe? Would be nice if we can get this reviewed from someone at InfluxDB (and get a clear guarantee on v1 commercially or otherwise). |
Agreed - I used that because that's what the record for Telegraf (also an InfluxData product) has.
Yep, 1.x is a bit more complex - OSS 1.x originally ended at 1.8.10. However there was recently a 1.11 release, though it wasn't tagged in the Github repo. There are tags for 1.12 though.
Let me see whether I can track someone down |
|
Perhaps we should add the clarification to Telegraf as well, in that case. |
|
@captn3m0 I reached out to a contact to see if we could get clarification, but no joy. Do you want to add the clarification to Telegraf, or should I? |
|
Feel free to file a PR. |
|
Done: #7411 |
This is a follow up from the observations made in #7303. It rewords the advice to note that that published link is for commercial support only and that there is no documented EoL policy for Influxdata's OSS products. This PR also removes a note about the page only covering the Telegraf "server" and not plugins - plugins are not independently versioned and are compiled in (i.e. they're part of the release). --------- Co-authored-by: Ben Tasker <[email protected]> Co-authored-by: Marc Wrobel <[email protected]>
This is a follow up from the observations made in endoflife-date#7303. It rewords the advice to note that that published link is for commercial support only and that there is no documented EoL policy for Influxdata's OSS products. This PR also removes a note about the page only covering the Telegraf "server" and not plugins - plugins are not independently versioned and are compiled in (i.e. they're part of the release). --------- Co-authored-by: Ben Tasker <[email protected]> Co-authored-by: Marc Wrobel <[email protected]>
Signed-off-by: Ben Tasker <[email protected]>
Co-authored-by: Marc Wrobel <[email protected]>
Co-authored-by: Marc Wrobel <[email protected]>
| > It includes APIs for storing and querying data, processing it in the background for ETL or | ||
| > monitoring and alerting purposes, user dashboards, and visualizing the data. | ||
|
|
||
| Starting from the release of InfluxDB OSS 3, the product became known as InfluxDB 3 Core and |
There was a problem hiding this comment.
Just read https://en.wikipedia.org/wiki/InfluxDB#InfluxDB_3_changes_open_source_offerings and it states that InfluxDB core is not a replacement for InfluxDB OSS. Looking at the announcement, https://www.influxdata.com/blog/influxdb-3-oss-ga/, it makes sense.
I am not familiar with InfluxDB, so can't really tell whether this is really different or not. WDYT @bentasker ? Is InfluxDB Core 3 on par with InfluxDB OSS 2 in terms of features ?
There was a problem hiding this comment.
Yeah, it's a bit of a weird one.
Officially, InfluxDB 3 is the future, but 3.x is also a very different product in terms of capabilities, features and use-case.
1.x/2.x are full time-series databases with no restriction on how much data you can retain (or how long for). It's not uncommon to see OSS users utilising it for long-term storage (including writing homeassistant data into it etc).
In comparison, 3.x:
- drops support for the Flux query language in favour of SQL
- drops support for flux tasks (though now has the processing engine instead)
- drops the integrated UI
- There are various differences in the tooling, including binary naming (
influxdvsinfluxdb3) - completely reimplements the storage engine: it uses datafusion + parquet rather than TSM (although this might sound like an implementation detail, it has an impact on what good schema design looks like)
- Because of the lack of compactor, OSS has a practical limit on the amount of data that you can query in one go
- (OSS) Limits the number of databases to five
- It also introduces a bunch of new features (Last value cache etc)
Is your line of thinking here that we should perhaps break out into two products/pages? One for InfluxDB 1&2x and one for 3.x/Core?
If so, that would make sense to me. I obviously don't know, but I suspect that 1.x and 2.x will continue to see releases for longer than the support policy implies - 1.x enterprise still gets active development (and there have been a couple of recent bumps in the OSS versions too).
2.x cloud is also still an ongoing thing, so fixes made there (particularly to common elements like Flux) will likely bubble into 2.x OSS.
There was a problem hiding this comment.
Is your line of thinking here that we should perhaps break out into two products/pages? One for InfluxDB 1&2x and one for 3.x/Core?
That would indeed makes things clearer. What I would expect is that if you are using 2.x OSS, an upgrade path to 3.x exists and does not involve subscribing to the enterprise version. For InfluxDB 3 I have the impression this is not the case at all.
There was a problem hiding this comment.
Yep, that's correct.
Influxdata are giving away free enterprise subscriptions to home users but that still entails running non-OSS components.
There's a question on the forum about that license here with the reply also noting
v2 continues to remain supported with security/bug fix updates, and has no EOL planned currently. We do encourage users to move to InfluxDB 3, however, as we’ll be continuing to develop an extensive feature set on our roadmap.
I'll split the pages out and crosslink them to each other
There was a problem hiding this comment.
Changes pushed - I've also added the latest 1.x cycle to influxdb.md
There was a problem hiding this comment.
Oh, maybe I need to take that back out, lint doesn't like it
Product Validator: Invalid releases '1.12' for influxdb.md, expecting release (released on 2025-04-08) to be before 2.7 (released on 2023-04-05).
Lint CI doesn't like the latest minor release of 1.x being more recent than 2.x
Add InfluxDB (2.7.x and 3.0.x are the currently supported versions)
Note: looks like this would also close #6178