InfluxDB at the Edge

Meet the Developer Series
Mar 1, 2022

Scott Anderson and Alan Pope discuss how InfluxDB helps efficiently collect, store and analyze vast amounts of data commonly associated with IoT and edge devices.

Was this page helpful?

Thank you for your feedback!

Support and feedback

Thank you for being part of our community! We welcome and encourage your feedback and bug reports for and this documentation. To find support, use the following resources:

Customers with an annual or support contract can contact InfluxData Support.

Edit this page Submit docs issue Submit issue

Where are you running InfluxDB?

Select your InfluxDB Cloud region and cluster or your InfluxDB OSS URL and we’ll customize code examples for you. Identify your InfluxDB Cloud cluster.

InfluxDB Cloud
InfluxDB OSS or Enterprise

AWS

US West (Oregon)
- us-west-2-1
- us-west-2-2
US East (Virginia)
EU Frankfurt

GCP

US Central (Iowa)

Azure

West Europe (Amsterdam)
East US (Virginia)

Default

localhost:8086

Custom

For more information, see InfluxDB Cloud regions or InfluxDB OSS URLs.

Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: