Release Announcement: Chronograf 1.9.1

Navigate to:

A new maintenance release for Chronograf is now available.

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


  • 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.


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.


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


  • 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.