Missing features in IOx backed InfluxDB Cloud

I’ve recently migrated from the TSM engine InfluxDB Cloud to the new IOx. However, in the process I seem to have lost the Notebooks, Dashboards, Tasks and Alerts features from the web UI, as well as Variables and Templates from under Settings. Are these features not supported in the IOx engine, or is there something else going on?

Those features aren’t supported in InfluxDB 3.0 (previously known as IOx). They use the Flux language which is only supported on the Cloud2 platform (the TSM backed version). We will be adding functionality over time, but for the time being we’re recommending that users looking for Tasks and Alerts functionality use AWS Lambda or some equivalent paired with an InfluxDB3 client library (the Python one works well).

For the other UI features, we have a limited UI for version 3.0 for the moment. Our focus is mostly on the core of the database. For users looking for a richer UI, they can pair InfluxDB 3.0 with Grafana, Apache Superset, Tableau, and (soon) PowerBI.

Grafana and Superset also have alerting features that can be used with InfluxDB 3.0.

Thanks for the clarification, @pauldix!

1 Like

I have read the document. May I ask if version 2.0 is still running, and are versions 3.0 and 2.0 running separately? In the document, the website address of influxdb cloud tsm is cloud2.influxdata.com, I can’t find Notebooks, Dashboards, Tasks, and Alerts. May I ask why the website address in tsm’s document also lost functions such as Dashboards, Tasks, and Alerts? Is there a 2.0 cloud service version that allows me to use these features?

Cloud2 is still running for customers that signed up before January 28th, 2023. For customers that signed up after that time (our Cloud Serverless platform), those features are not available. While the API for Flux and Tasks remain in the Cloud Serverless platform, we intend to remove those as they are deprecated in 3.0 for the time being. We found that the Flux compatibility bridge that we built for 3.0 didn’t have the kind of performance that users required so we are focusing on SQL and InfluxQL for now.