InfluxData Blog - Tim Hall

Latest release of InfluxDB Enterprise delivers improvements to Flux, database backup options and audit logging

Tim Hall (InfluxData) — Thu, 17 Feb 2022 08:00:41 -0700

InfluxDB Enterprise 1.9.6 – release notes

Key highlights for this InfluxDB Enterprise release – available here – include:

Flux advancement
- This latest update moves Flux from version 0.131.0 to 0.140.0.
  - Timezone support enhancements including:
    - Added timezone package with fixed offset location.
    - Exposed location functionality to window(), aggregateWindow(), and experimental.window().
    - Added location functionality to the interval package.
    - Added methods to convert time values to and from local clock time.
  - Integration with MQTT Brokers:
    - Added a new mqtt.publish() function.
    - Added a retain parameter to mqtt.to.
  - Notification endpoint enhancements:
    - Added contrib/bonitoo-io/servicenow package and support for ServiceNow events.
    - Added component and customDetails parameters to pagerduty.sendEvent().
  - SQL Integration:
    - Added support for Vertica to the SQL package.
    - Created a BigTable dependency to let Flux mimic or control BigTable API usage.
  - Other enhancements:
    - Added bitwise operations.
    - Added record.get() function to dynamically retrieve record properties.
- Please join the discussion about Flux via InfluxCommunity or Slack.

Backup/Restore improvements
- Estimate the size of a backup (full or incremental) and provide progress messages. A new -estimate option has been added to influxd-ctl backup to allow you to request an estimate for the size of a backup (full or incremental). In addition, this option also provides progress messages while the backup is proceeding. It prints the number of files to back up, the percentage of bytes transferred for each file (organized by shard), and the estimated time remaining to complete the backup.
- Revert damaged meta nodes to a previous state. -meta-only-overwrite-force has been added to influxd-ctl restore to allow you to revert damaged meta nodes in an existing cluster to a previous state when restoring an InfluxDB Enterprise database.

Logging enhancements
- Audit log for meta nodes. When cluster-tracing is enabled as part of the meta node configuration, all API calls to meta nodes are now logged with details providing a detailed audit trail including IP address of caller, specific API being invoked, action being invoked, and more.
- Log active queries when a process is terminated. We've added a new configuration option for logging. The termination-query-log configuration option, when set to true, logs all running queries when a data node process receives a SIGTERM (for example, a Kubernetes process exceeds the container memory limit or the process is terminated).

There is no corresponding InfluxDB OSS 1.9 release. While we continue to make improvements to the InfluxDB 1.x code base – and these are being included within 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 you need to. 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.

For our InfluxDB Enterprise customers, log in to the InfluxDB Enterprise portal and download the binaries from there. If you need more help? Contact support.

If you find issues or have questions, please join our InfluxDB Community Slack, post them in our InfluxDB GitHub Repo or our Community Site and we will take a look. Thank you.

Ops & Security improvements in the new release of Chronograf

Tim Hall (InfluxData) — Wed, 02 Feb 2022 16:06:22 -0700

Chronograf 1.9.3 – Release Notes

This latest release of Chronograf includes the following new improvements and fixes:

Security

Upgraded bluemonday component to resolve CVE-2021-29272.
Ensure enforcement of access to one and only one organization between multiple tabs.

Kapacitor Integration

You can now rename a TICKscript. Chronograf already extracts the TICKscript name from the name variable within the script itself. If no name variable is present, the TICKscript's ID is used as its name. This improvement inserts or modifies the name variable in the script upon a name change. The TICKScript thus must be saved to persist the change. Users are warned about unsaved changes when exiting without saving, which is consistent with all other types of changes on the page (editor, type, database, retention policy, etc.).

Operational Improvements

InfluxDB Query Management

- Two important additions to the InfluxDB Query Management tab have been made:
  1. Query status is now displayed, allowing you to see if a query is running or has been killed.
  2. You can now download the contents of the tab into a CSV.

HTTP Proxy Support

- The HTTP client used by Chronograf now consistently honors the HTTP proxy settings from environment variables. Improvements were made to:
  - Token command within chronoctl
  - OAuth client
  - Kapacitor client
  - Flux client

Enhanced Logging

- Improved logging by capturing the URL of the InfluxDB instance when a ping fails. In the case where Chronograf is connected to multiple InfluxDB instances, it's helpful to identify which connection is having an issue.

Grab the latest bits from our downloads page under “Are you interested in InfluxDB 1.x Open Source?”

If you find issues or have questions, please join our InfluxDB Community Slack, post them in our Chronograf GitHub Repo or our Community Site and we will take a look.

Security and extensibility enhancements are now available in Kapacitor 1.6.3

Tim Hall (InfluxData) — Tue, 25 Jan 2022 10:01:54 -0700

Security and extensibility enhancements are now available in Kapacitor 1.6.3.

Kapacitor 1.6.3 – release notes

Kapacitor 1.6.3 includes the following fixes and improvements:

Security
- We've deprecated ciphers that were identified as "weak" as part of the sweet32 attack.

TICKscript enhancements - additional config options for BigPanda and Alerta

- BigPanda event handler:
  - Added the following configuration options to the handler (per BigPanda Alert specification):
    - host: Identifies the main object that caused the alert
    - attribute: Adds additional attribute(s) to the alert payload
  - Additional configuration options include the following template data in host and attribute value expressions: ID, Message, Level, Time, Duration, Details, Name, TaskName, Group, Tags, Fields.
    - Tags and fields are added to the payload as additional attributes.
    - A new handler configuration option "auto-attributes" has been added to control this behavior. The value can be either tags, fields or both these keywords (comma-separated). For backward compatibility, the default value is tags,fields.
- Alerta event handler: Added support for attributes which is a dictionary of key-value pairs. This allows you to send custom attributes (for example, runBookUrl) to Alerta.

Other - Compatible with new Golang library and more

- Upgraded to the new google.golang protobuf library
- topic-buffer-length - A new configuration parameter has been added to the alert configuration group to allow for adjusting the topic queue length. This is useful if large amounts of alerts must be sent due to scheduled maintenance such as a Windows update.
- Improved error messages associated with Flux-based tasks

Grab the latest bits from our downloads page under “Are you interested in InfluxDB 1.x Open Source?”

If you find issues or have questions, please join our InfluxDB Community Slack, post them in our Kapacitor GitHub Repo or our Community Site, and we will take a look.

Apache log4j Vulnerabilities CVE-2021-44228 and CVE-2021-45046

Tim Hall (InfluxData) — Mon, 13 Dec 2021 14:05:23 -0700

InfluxData is aware of two recently reported Apache log4j (log4j) vulnerabilities CVE-2021-44228 and CVE-2021-45046. We employ rigorous security practices to safeguard our products and their dependencies as well as software used to deliver our cloud services. We want you to be aware that our software does NOT employ log4j, nor is it within our supply chain.

The scope of this statement covers all versions of our services and software including:

InfluxDB OSS
InfluxDB Enterprise
InfluxDB Cloud
Telegraf
Kapacitor
Chronograf

This also includes our official Docker images as well.

InfluxData uses software on backend systems that include log4j. These systems have been patched as of 10 December 2021 and remain isolated from our cloud services infrastructure.

If you have any additional questions or concerns, you may contact us at security@influxdata.com.

Release Announcement: InfluxDB OSS 2.1.0

Tim Hall (InfluxData) — Mon, 08 Nov 2021 10:52:18 -0700

A new feature-bearing release for InfluxDB OSS is available now. We’ve been busy bringing the latest improvements to this release. Some of these have been available within InfluxDB Cloud, and now we are pleased to offer them within the open source offering for those of you developing against the OSS edition on your laptop or deploying this at the edge.

InfluxDB 2.1.0 – release notes

New Packaging

`influx` CLI moved to separate repository

The influx CLI has been moved to its own GitHub repository. You can also download the latest CLI from our downloads page under InfluxDB Cloud CLI.

`influxdb` release artifacts affected

Release artifacts are impacted as follows:

Release archives (.tar.gz and .zip) no longer contain the influx binary.
The influxdb2 package (.deb and .rpm) no longer contains the influx binary. Instead, the package declares a recommended dependency on the new influxdb2-cli package.
The quay.io/influxdb/influxdb image no longer contains the influx binary. We recommend migrating to the influxdb image hosted on DockerHub.

Find supported `influx` CLI commands

With this change, versions of the influx CLI and InfluxDB OSS (influxd) are not guaranteed to exactly match. To check the version of the influxd server, see influxd version in influx

CLI or use the /health endpoint of your InfluxDB server.

The influx CLI documentation has been updated to reflect which influx CLI commands work with which versions and editions of InfluxDB across OSS and Cloud.

Feature Advancement

This release includes the following new features:

Notebooks, annotations, and visualization updates
VS Code Flux Extension
Updates to InfluxQL
API and CLI updates
Token updates
Support for latest Flux and Telegraf releases

Notebooks, annotations, and visualization updates

We’ve added a new developer workbench called InfluxDB Notebooks which allows you to:

Create documents with live code, equations, visualizations, and explanatory notes
Create dashboard cells or scheduled tasks
Build runbooks
Document data processing steps
Collaborate with other developers

The idea behind InfluxDB Notebooks is to provide you with the means to partial or finished artifacts within the platform via the browser. It also allows developers to collaborate with each other through the notebooks themselves using the various panels to support distributed development. Over time, this developer workbench will become the primary means by which all resources are developed through the browser. We appreciate all the feedback that we’ve gotten regarding these key capabilities!

Speaking of collaboration, we have also added the ability to annotate dashboard cells to share insights or activities with others. We’ve also added support for static legends on the dashboard cells to assist with driving more visual clarity when using line graphs and band plots. We also overhauled the raw data view to provide a cleaner tabular visualization of this data, and last but not least, we have an updated set of dashboard auto-refresh options that should allow you to schedule the refresh rate you desire.

VS Code Flux Extension

If you are building an application which leverages InfluxDB and you use Visual Studio Code, check out the Flux Extension. This extension really helps speed the development process by providing autocomplete and syntax checking for your Flux script, allowing you to connect to your InfluxDB instance and interactively test and evaluate results and more.

InfluxQL

Based on community feedback, we’ve enhanced the capabilities of the SHOW MEASUREMENTS meta query. It now supports database and retention policy wildcards. For example, SHOW MEASUREMENTS ON *.* to show all databases and SHOW MEASUREMENTS ON <db>.* to show all retention policies.

API

We’ve made a couple of key improvements to the API and one deprecation.

New parameters have been added to the /users API; specifically GET /users now includes support for: offset, limit, and after.
Added new backup and restore APIs specifically for metadata including both key-value and other metadata.
Deprecation of POST .../secrets/delete. To delete a secret, use the new DELETE .../secrets/{secretID}.

CLI

influxd configuration

We’ve added several new configuration options to influxd. Here are the most important ones:

The influxd recovery command lets you create a recovery operator token in the event that you forget the primary administrator user name/password. This provides you with a secure way to recover access while not losing data or resources stored within the platform.
You can now set the --storage-wal-max-concurrent-writes flag to enable tuning memory pressure under heavy write load.
We've also added --storage-wal-max-write-delay flag to prevent deadlocks when the WAL is overloaded with concurrent writes.
You can now also set the --storage-write-timeout flag to set the duration for write request timeouts.

For more information about all the configuration options and settings, see InfluxDB configuration options.

influxd inspect

The influxd inspect command has been significantly enhanced to allow for a much wider range of operational and administrative reporting and repair capabilities. Many of these existed previously as part of our InfluxDB 1.x tooling:

build-tsi - allows you to rebuild the index in the case of failure or corruption
delete-tsm - bulk deletes measurements from a raw Time-Structured Merge Tree (TSM) file.
dump-tsi - dumps low-level details about Time Series Index (TSI) files which is useful for supportability and determining if there are issues with the index.
dump-tsm - dumps low-level details about TSM files which is useful for supportability and determining if there are issues with the actual files where data is stored.
dump-wal - dumps low-level details about write ahead log (WAL) files which is useful for supportability and determining if there are issues with the write ahead log.
report-tsi - analyzes TSI within a specified bucket and reports the cardinality of data stored in the bucket segmented by shard and measurement.
report-tsm - analyzes TSM files within a storage engine directory and reports the cardinality within the files and the time range the data covers.
verify-seriesfile - verifies the integrity of series files.
verify-tombstone - verifies the integrity of the tombstone files.
verify-tsm - verifies the integrity of the TSM files within the storage engine.
verify-wal - verifies the integrity of the write ahead log.

influxd downgrade

A new influxd downgrade command has been added to isolate and ease the process of downgrading (if necessary) from newer versions to older ones.

Tokens

We’ve made a couple of improvements to token and token handling.

Based on community feedback, we've added support for standard Bearer token syntax. Now you can specify token credentials as: Authorization: Bearer xxxxxxxx.
Also, if you are restoring a backup that overwrites the Operator token, the new token value is returned to you after you trigger the restore.

Flux

We’ve advanced Flux to v0.139.0. This update enables a number of key capabilities such as:

Dynamic modification of time offsets based on your specified timezone. You can also specify fixed time offsets relative to UTC.
Enables writing to remote hosts using the Flux to() and experimental.to() functions. This allows you to selectively send data to InfluxDB Cloud or other InfluxDB OSS instances.
Query and write to Vertica SQL databases. This allows you to join your time series data with relational data stored within Vertica.
Perform bitwise operations on integers and unsigned integers.
A new hex package for working with hexadecimal string values. Allows you to convert string values encoded in hexadecimal format to numerical values.

Telegraf Configuration Support

The Load Data page now contains all of the configuration options for all input plugins available with Telegraf 1.20. For more information about the available plugins, see Telegraf plugins within the documentation.

Bug Fixes

If all of that feature advancement isn’t enough, there are a handful of bug fixes which also have been addressed. Check out the release notes for all the details or if you are looking for a specific fix.

If you find issues or have questions, please join our InfluxDB Community Slack, post them in our InfluxDB GitHub Repo or our Community Site, and we will take a look.

By Developers, for Developers: New Offerings Announced at InfluxDays North America

Tim Hall (InfluxData) — Tue, 26 Oct 2021 04:00:07 -0700

By developers, for developers – this has always been InfluxData’s approach when building new tools for users, and it’s certainly the case as we roll out the newest round of features and capabilities at this year’s InfluxDays North America. We know that application building isn’t easy and that development cycles are precious. That’s why we focus everything we do around delivering developer happiness.

For example, at InfluxData, we talk a lot about meeting developers where they are. What we mean by this is we understand that not all developers use the same infrastructure, programming languages or development procedures. Some are building applications in the cloud, some on-premises – and many are doing both. So a critical part of our innovation strategy is to facilitate as many options as possible to make the experience of building applications which are fundamentally powered by time series data faster and more efficient for all developers. We’re committed to constantly improving the developer experience – it’s what we work toward every day.

At InfluxData we strive toward two things:

Meet developers where they are - in their language of choice, using their preferred tools, running on their preferred cloud platform.
Optimize for Time to Awesome - the sooner developers can get up and running with InfluxDB, the sooner they can move onto other aspects of building their applications.

With that in mind, we’re excited about the newest features released today at InfluxDays.

Meet developers where they are

Our first group of updates is focused on creating more ways for builders to easily write Flux queries – taking our commitment to support developers wherever they are another step further. These capabilities let builders pick the development style that works best for them, wherever they choose to build apps. New updates include:

Build, test and operate in the browser with InfluxDB Notebooks Builders can test out ideas, annotate or explain what they're doing and why, and even deploy those tasks – all from within the InfluxDB platform without ever having to leave the browser. Developers can now more easily create alerts without having to write code since they can use the new Notebooks Alerting template to send notifications to Slack, PagerDuty and other applications or systems.

Auto-generate code in 10+ languages with Client Libraries If you've used the browser-based tooling to explore your data, create a query, and analyze the results, perhaps you are ready to embed this within your application? Now, you can auto-generate application code that can be rapidly incorporated into your application by simply choosing the target language, allowing teams to quickly develop, validate and test code.

Write Flux code in Visual Studio with the Flux VS Code Extension For those who may be more comfortable doing all of their development within an IDE, we've created a Flux extension for Visual Studio Code (VS Code). The Flux VS Code Extension lets developers write Flux code with all the convenience and efficiency of Visual Studio, including syntax checking, autocompletion, and a schema explorer, which speeds up writing code. Now, the extension also integrates directly with InfluxDB so developers can run Flux tasks natively, but also browse existing tasks from within VS Code. It also allows developers to execute and view their query results, enabling a better experience whether they are composing a simple query or something more sophisticated, which might require a number of iterations to obtain precisely the results they desire.

New InfluxDB Cloud enhancements improve the developer experience

As important as streamlining the development process is, there are new capabilities being delivered within InfluxDB Cloud which are just as critical. In working closely with our community members and customers, these new features address a number of requests for the platform to optimize their Time to Awesome:

Protect against unwanted changes with the Explicit Schema option The schema-less nature of InfluxDB contributes to how quickly developers can get up and running with it. However, we also recognize that there are times when it makes sense for developers to have more control over the schema. InfluxDB Cloud now allows developers to explicitly define a schema at the bucket level. This can safeguard developers against unwanted changes, ensuring they can continue to run applications with peace of mind.

Invoke Flux scripts from your application with API-invocable scripts. InfluxDB Cloud now supports API-invocable scripts, which allow developers to define parameterized Flux scripts that they can invoke in their applications. Apps powered by API-invocable scripts are more intuitive by delivering predictive outcomes through triggered automated actions. And these API-invocable scripts can be defined using Flux via the VS Code extension or directly via the InfluxDB API.

Integrate Flux with 3rd party platforms We want users to be able to leverage Flux so that it meets the needs of their environment or system – no matter where it is. That's why we've added notification support for several new platforms, such as Alerta, WebEx Teams, and ServiceNow to an already impressive list of integrations.

Customize Flux for time zone & location. It's now possible to write Flux queries which adhere to local time zones, and Flux can even adjust to daylight saving time – allowing developers to fine-tune their analytics based on their precise locations around the world.

More to come at InfluxDays

By understanding the challenges developers face with time series data, the InfluxData team can provide these kinds of features that mitigate development barriers and expedite that coveted Time to Awesome™. As InfluxDays kicks off, we’ll be talking more about how these new features and capabilities extend the flexibility of InfluxDB and Flux, and make the development process a more efficient and productive one.

Make sure you’ve registered for the event so you can follow the livestream and watch all our executive, customer and community speakers. And be sure to tune into our session with InfluxData CTO and Founder Paul Dix at 9:30am PT today where he will be discussing these new features and how they are helping users unlock even more developer happiness.

See you there!

Release Announcement: Chronograf 1.9.1

Tim Hall (InfluxData) — Fri, 15 Oct 2021 10:27:16 -0700

A new maintenance release for Chronograf is now available.

Chronograf 1.9.1 — Release Notes

This latest release of Chronograf includes the following new improvements and fixes:

Visualization

When building a query, the browser history is now not extended without a change in InfluxQL/Flux query. Previously, this was causing some issues when combined with a very short duration query refresh interval.
The new v.windowPeriod introduced in Chronograf 1.9.0 was "stuck" at 3ms. The calculation used to determine the appropriate value has been fixed.
When zooming into a cell powered by a Flux query, a cell's Flux query is now rerun with zoomed time interval parameters, the same way as the InfluxQL query does.
Switching the table orientation from horizontal to vertical did not respect the configured time format. This has been addressed.
When using Flux to power dashboard cells, missing values were being interpreted, in line chart, as zeros instead of nulls. This has been addressed so that the behavior is consistent with the way that the InfluxQL-based queries function.

Multi-organization navigation

If you leverage the multi-organization capabilities of Chronograf and attempt to access different organizations across multiple tabs within the same browser, the result was some very strange and inconsistent behavior. Now, switching between organizations and browser tabs forces the underlying session information to be updated correctly eliminating the inconsistencies. Only one organization at a time can be accessed at a time within a single browser and its associated tabs.

Browser specific issues

Safari failed to display cells of type Single Stat. This has been addressed.
Addressed an issue where, using Firefox in private mode failed to display query results in the dashboard.

Security

Upgraded bluemonday component to resolve CVE-2021-29272.
Upgraded jwt package to resolve CVE-2020-26160.

Kapacitor integration

If you use a name task variable, the TICKscript name that appears in the Alert portion of Chronograf now reflects that variable. Previously, any name variables were ignored and this led to confusion.
TICKscripts that are created from templates are now visible in a read-only mode from within Chronograf. This requires you to use Kapacitor 1.6.2 which now provides information about the template used to create the underlying TICKscript. In addition, TICKscripts that are created from templates will also NOT appear in the Alert Rule section of the UI.
Pagination of more than 500 Flux tasks was broken. This has now been addressed.

Packaging

Chronograf ARM RPM packages were renamed with yum-compatible names.

Other

Chronograf 1.9.1 was built using golang 1.17.1.

If you find issues or have questions, please join our InfluxDB Community Slack, post them in our Chronograf Github Repo or our Community Site and we will take a look.

Release Announcement: InfluxDB OSS & Enterprise 1.8.10

Tim Hall (InfluxData) — Wed, 13 Oct 2021 12:00:10 -0700

Maintenance releases for InfluxDB Enterprise and OSS are now available. Keep in mind that these are not the most current versions of InfluxDB. These maintenance releases are provided with the associated fixes to support community members and customers who do not wish to upgrade to a more current version at this time. Keep in mind that the current version of InfluxDB OSS is 2.0.9 and Enterprise is 1.9.5. Independent of the versions, there is API compatibility of v1 and v2 for the read and write APIs across all editions, OSS, Enterprise, and Cloud.

InfluxDB OSS 1.8.10 — release notes
InfluxDB Enterprise 1.8.10 — release notes

For community members, InfluxDB 1.8.10 the download links can be found here under the “Are you interested in InfluxDB 1.x Open Source?” section of the page.

For our InfluxDB Enterprise customers, if you need access to this specific release, please contact support for assistance with the download links.

If you find issues or have questions, please join our InfluxDB Community Slack, post them in our InfluxDB Github Repo or our Community Site and we will take a look.

Release Announcement: InfluxDB Enterprise 1.9.5

Tim Hall (InfluxData) — Mon, 11 Oct 2021 16:40:10 -0700

A new maintenance release for InfluxDB Enterprise is now available.

InfluxDB Enterprise 1.9.5 — release notes

Key highlights for this InfluxDB Enterprise release include:

Memory Utilization Improvement

Improvements to the compaction cycle using the TSI index has resulted in a significant reduction in memory usage. In some cases, a 50% reduction in memory usage was observed.
The underlying protobuf library has also advanced to the latest version which results in some additional resource efficiency.

Flux Advancement

This latest update moves Flux from version 0.120.1 to 0.131.0.
- Breaking change: removed the sleep() function
- Added WebEx Teams notification support.
- Added new Hex package to ease working with hexadecimal string values.
- Optimized the pivot() transformation.
- Added InfluxDB sample data package.
- Now table.fill() is called when aggregateWindow(createEmpty: true) is used.
Fixes have been added to address panics caused by queries using limit() and other cases where no data is present.
In cases where the replication factor for the database was less than the number of data nodes and datasets with > 1000 points to merge were being returned, the Flux engine encountered issues where some points were not read correctly. This has been addressed.
Please join the discussion about Flux via InfluxCommunity or Slack.

Backup/Restore Improvements

The following improvements have been made to the restore process. Review the documentation for more details on how to take advantage of these improvements:

You can now restore data with a new retention policy into an existing database.
- You can override the duration of a retention policy contained within the backup while restoring. So, if you backed-up a database with a 30-day retention period, you can restore this and extend the retention period to any duration you wish, including infinite.
- You can now specify a destination shard when restoring a specific shard.
- The process of a single-shard restore has been improved to reduce the amount of validation of shards during shard restore, if you specify a new shard. Specifically, the shard just has to have the same index in the shard group (for hashing), and the same start and end time (for queries). Previously, InfluxDB Enterprise also asserted a matching source and destination database, retention policy, and shard group id. This existing behavior is preserved when -newshard is not provided as part of the restore process. Even if -shard is supplied, the metadata is updated if there is a change to the retention policy or database name.

Security

If you've configured InfluxDB Enterprise to use LDAP for authentication, LDAP queries that use nested connections to the LDAP server fail to properly use STARTTLS, if configured. The result was that an unencrypted LDAP connection was used for part of the operation. This has been addressed so that STARTTLS is now used for all connections.
influxd-ctl entropy commands could use the incorrect TLS settings to communicate with data nodes if meta nodes and data nodes don't have matching TLS configurations. This has been addressed such that the appropriate TLS settings are now used when working with influxd-ctl entropy.

Eventual Consistency Fixes

In some cases the Anti-Entropy service was not reading the remote digest completely. This causes a broken pipe error on the remote node when it tries to write to the closed connection. This issue has been addressed.
- There are rare situations where shards with overlapping time ranges can exist within the cluster. If overlapping shards do exist, then writing multiple points to those shards resulted in dropped writes with a dropped write error reported to the writer. If only a single point is written, it will succeed. This edge case has been addressed.
- A race condition was found within the hinted handoff service which was triggered by frequent hinted handoff queue growth and clearing. In these situations, writes were lost for the remote data nodes. In these situations, data entropy was introduced or the data could be lost entirely. This has been addressed.

Logging Improvements

Enabling the log format = "json" did not result in all of the log output being in JSON format. This has been addressed.
In some circumstances, InfluxDB Enterprise can lose logs for shard writes that time out. Additionally, in situations where InfluxDB Enterprise fails to fully read a TLV for queries and writes in the RPC cluster API, it doesn't log which type of RPC call was attempted. Both of these issues have been addressed.

Again, 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 within 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.

InfluxData Blog - Tim Hall

Latest release of InfluxDB Enterprise delivers improvements to Flux, database backup options and audit logging

Ops & Security improvements in the new release of Chronograf

Security and extensibility enhancements are now available in Kapacitor 1.6.3

Apache log4j Vulnerabilities CVE-2021-44228 and CVE-2021-45046

Release Announcement: InfluxDB OSS 2.1.0

New Packaging

influx CLI moved to separate repository

influxdb release artifacts affected

Find supported influx CLI commands

Feature Advancement

Notebooks, annotations, and visualization updates

VS Code Flux Extension

InfluxQL

API

CLI

influxd configuration

influxd inspect

influxd downgrade

Tokens

Flux

Telegraf Configuration Support

Bug Fixes

By Developers, for Developers: New Offerings Announced at InfluxDays North America

Meet developers where they are

New InfluxDB Cloud enhancements improve the developer experience

More to come at InfluxDays

Release Announcement: Chronograf 1.9.1

Release Announcement: InfluxDB OSS & Enterprise 1.8.10

Release Announcement: InfluxDB Enterprise 1.9.5

`influx` CLI moved to separate repository

`influxdb` release artifacts affected

Find supported `influx` CLI commands