Release Announcement: InfluxDB Enterprise 1.9
A new feature-bearing release for InfluxDB Enterprise is now available.
- InfluxDB Enterprise 1.9.2 — release notes
This is the first official release of InfluxDB Enterprise on the 1.9 line.
Key highlights for this InfluxDB Enterprise release include:
- Flux Advancement
- Flux query management controls, which are similar to the existing InfluxQL query management controls, have been added. This allows you to control the behavior of the Flux query engine and tune limits based on your use case, available machine resources and more.
- Flux has advanced significantly. InfluxDB Enterprise 1.8 included Flux 0.65, and we’ve been advancing the capabilities of the language significantly since then. This latest update moves Flux up to 0.113. Subsequent maintenance releases will continue to advance Flux forward from here and align with the latest capabilities available which appear first via InfluxDB Cloud.
- Performance improvements have also been added for last(), min(), and max() functions. Additional performance enhancements will also be part of subsequent maintenance releases.
- Operational Metrics Expansion
- Significant performance improvements have been made to SHOW SERIES CARDINALITY and SHOW SERIES CARDINALITY from <measurement> InfluxQL queries. These queries now return a cardinality estimation column header where before they returned count.
- Starting with InfluxDB 1.8.5, the ability to find which measurements or shards are contributing to disk size was available via the new influx_inspect report-disk command. This is tremendously useful for capacity planning and managing storage requirements.
- Information about license expiration has been added to the /debug/vars metrics output. This enables customers to configure alerts about upcoming license expiration.
- There are two optional metrics which can now be exposed and which shed light on data arrival and where it lands within InfluxDB. The first allows collection of statistics for points, values and new series written per measurement. Previously, points and values were reported only available at a database level. But the addition of new series and the ability to group these metrics by measurement provides additional insight and depth for operators. The second allows for collection of statistics of points, values and new series written by user credentials (login). This can be particularly useful in tracking down the source of data arriving. These metrics are exposed for each data node, and operators can use these to aggregate the write requests across the entire cluster to gain a detailed understanding of the growth of series within a measurement and what user credentials are being used to write data to the cluster and more!
- For those customers using LDAP with InfluxDB Enterprise, Kapacitor can now leverage that integration for authentication against InfluxDB Enterprise using LDAP credentials.
- Node Labels
- Node labels let you assign arbitrary key-value pairs to meta and data nodes in a cluster. For instance, an operator might want to label nodes with the availability zone in which they’re located. While this is only for informational purposes at this time, we plan to leverage this feature in future release for determining shard placement. Such a feature would allow for data center, availability zone or rack awareness and allow for higher levels of cluster availability.
There is no corresponding InfluxDB OSS 1.9 release. While we continue to make improvements to the InfluxDB 1.x code line and these are being included in InfluxDB Enterprise, we are guiding our community users to InfluxDB 2.x at this time. Of course, you can always build InfluxDB 1.x from source code, if necessary. InfluxDB 2.x does include 1.x compatible interfaces to allow for reads and writes using the 1.x API. The latest open source release can be found on our downloads page.
Sponsored by InfluxData.