We’re pleased to announce that InfluxDB Cloud is now on Azure East US, based in Virginia. With this expansion, our time series data platform is now on Microsoft Azure on two continents — Europe and North America — and runs in five locations across all three major cloud providers.
This brings InfluxDB Cloud’s effortless scaling, flexible usage-based pricing, and Azure time series data integration to customers that want time series data storage in the United States.
Where InfluxDB Cloud runs
Where does InfluxDB run? Here’s a list of all the locations as of when this post was written. Here is the current list of InfluxDB Cloud Regions.
|Microsoft Azure||East US||Virginia, United States|
|Microsoft Azure||West Europe||Amsterdam, Netherlands|
|AWS||us-west-2||Oregon, United States|
|Google Cloud||us-central1||Iowa, United States|
As you can see, InfluxDB Cloud is now broadly distributed across North America and Europe:
How to access InfluxDB Cloud on Azure East US
Here’s a step-by-step guide on how to get InfluxDB Cloud on Azure East US:
First, visit cloud2.influxdata.com and sign up for a free InfluxDB Cloud account. You can do 1-click signup with your Google account, or enter your details.
Once you hit the Create Account button, check your email for a message that looks like this:
Click Verify Your Email, and you’ll see the following page asking you where to store your data.
Once you select Microsoft Azure, choose Virginia, and you’ll use that instance of InfluxDB Cloud.
There are a few more steps that are self-explanatory, but one thing I want to point out is the InfluxDB Cloud URL for Azure East US:
This is the endpoint of the InfluxDB Cloud API that you’ll be using when you interact with the InfluxDB API, InfluxDB client libraries, influx CLI, and Telegraf. Here is our documentation page with a complete list of InfluxDB Cloud URLs if you are running on a different region.
Customized code snippets for Azure US East
Speaking of our documentation, here’s a handy trick to customize all our code samples to use the Azure East US URL. In the InfluxDB Cloud documentation, click on the gear icon in the upper right corner:
Then specify that you’re running in Azure East US:
And now code samples in our documentation, such as on this page, will have the correct InfluxDB Cloud URL already inserted so you have one less step to have to worry about. See the first line of the curl command below:
Integrate InfluxDB Cloud with Microsoft Azure
InfluxDB Cloud has a broad range of integration points with Azure, and Microsoft products in general. Before we dive in, it’s helpful to think of our time series data platform as doing three main things:
- Accumulating time series data by ingesting it from numerous locations
- Analyzing that data, for visualization, anomaly detection, and alerting
- Acting on that data, by sending to alerting systems, custom applications, or third-party tools
To accumulate time series data, InfluxDB provides a number of options for data ingest, but I’d like to focus on two: Telegraf and Flux. Telegraf, our open source server agent for collecting metrics, can pull data from the following Microsoft technologies:
- Azure IoT Hub, using the Telegraf plugins for Azure Event Hub, AMQP, MQTT, and HTTPS, to collect IoT device telemetry data.
- Windows servers, using the Telegraf Windows Performance Counter plugin and Windows Services plugin, to ensure that your Windows servers are performant.
- GitHub, using the Telegraf plugin and InfluxDB Template for GitHub, to track stats for each of your repositories, such as the number of forks, open issues, etc.
- Azure Storage Queues, using the eponymous Telegraf plugin, to track queue sizes.
- SQL Server, using the Telegraf plugin and InfluxDB Template for SQL Server, to track the health and performance of your databases.
Telegraf has over 200 plugins, covering technologies that aren’t Microsoft-specific but which you might find on Azure, such as Docker and Kubernetes. You can also pull in data from over 700 FluentD plugins, thanks to the Telegraf FluentD plugin.
Also, our Flux data scripting and query language has a SQL library that lets you enrich your time series telemetry with metadata from relational databases, including SQL Server. This metadata can include IoT asset information — for example, the year, make, and model of a piece of IoT equipment. The specific Flux function you use to do this is called sql.from().
The analyze piece of the equation is handled by InfluxDB itself. As mentioned, InfluxDB Cloud runs on Azure infrastructure running in the West EU region in Amsterdam, and by early September, East US in Virginia.
Additionally, when you analyze your data using Flux from within the InfluxDB UI, you do so in an embedded Monaco editor that delivers an experience that is similar to Microsoft Visual Studio Code with capabilities like autocompletion, syntax validation and highlighting, variable references and renaming, and more. There’s also a Flux plugin for VS Code, for developers building applications on top of InfluxDB. If you have features you’d like us to add, file an issue on the Flux LSP repo.
These editors are two of many ways we sweat the details to ensure that you have a great experience working with InfluxDB, and is part of our time to awesome mantra.
Flux provides a broad range of functions for statistical analysis and forecasting, such as:
- Calculating percentiles to detect SLA compliance failures
- Windowing and aggregating data to pick out insights from noisy data sets
- Enriching monitoring data with business data in SQL databases — like account name, type or size — to detect anomalies by business measures
- Forecasting with Holt-Winters to predict outages and capacity issues
- Geographically tracking monitoring metrics to better determine which regions are experiencing problems
- Sophisticated anomaly detection, using techniques like Median Absolute Deviation (MAD) and Balanced Iterative Reducing & Clustering (BIRCH), to help you find and fix problems faster and reduce your mean time to resolution (MTTR)
To act on time series data, you can
- Send alerts to Microsoft Teams, PagerDuty, Slack, Discord, Telegram, Pushbullet, and via webhooks.
The diagram below sums up these points of integration. Purple boxes are technologies provided by InfluxDB, blue boxes are provided by Microsoft, and grey boxes are third-party technologies such as Grafana or PagerDuty.
Up next: Azure Marketplace billing, more regions
In the coming months, you’ll see InfluxDB Cloud in the Azure Marketplace, allowing you to put your InfluxDB Cloud charges straight onto your Azure bill. This lets you consolidate all your Azure expenses, providing simpler administration, easier expense tracking, and streamlined purchasing. Plus, it lets you take advantage of any committed use discounts that you have arranged with Microsoft. We’ve already done this for InfluxDB Cloud and AWS Marketplace and Google Cloud Marketplace, and we’re looking forward to bringing it to our customers on Azure.
Also, you’ll see InfluxDB Cloud on additional regions, based on input that customers like you have provided us. If you’d like to provide us with input on where we launch future InfluxDB Cloud instances, please fill in this short form. Your vote will help us best serve our entire customer base.
If you’d like to check out InfluxDB Cloud for yourself, sign up for a free InfluxDB Cloud account, and feel free to ask any questions in our ever-helpful InfluxDB community and community Slack channel. Enjoy!