This is archived documentation for InfluxData product versions that are no longer maintained. For newer documentation, see the latest InfluxData documentation.
There are two breaking changes from v0.10 that may require some work to upgrade from a v0.10 instance. These changes are:
- Support for multiple InfluxDB clusters
- Changes to InfluxQL functions
- Changes to Email, Slack, HipChat global behavior
Multiple InfluxDB Clusters
Now that Kapacitor supports connecting to multiple InfluxDB clusters,
the configuration has changed slightly. To upgrade your configuration
to work with v0.11, you will need to update the
of your configuration from:
[influxdb] enabled = true ...
[[influxdb]] enabled = true default = true name = "localhost" ...
With the new configuration, you can now alert on data from multiple
clusters. By giving each cluster a name in your configuration, you
can now specify which cluster to use when performing a batch query or
writing results to InfluxDB by using the
New InfluxQL Syntax
.mapReduce method has been deprecated, and replaced by a simpler
syntax. As an example, using the current syntax:
stream.from()... .window()... .mapReduce(influxql.count('value'))
Has been updated to:
stream.from()... .window()... .count('value')
This new syntax no longer exposes the map/reduce concept directly to the user, which makes the function calls simpler and improves overall readability.
Note: The old syntax will continue to work for all v0.11 versions of Kapacitor but will be removed starting with v0.12.
Email, Slack, HipChat Global/StateChangesOnly
In previous releases, setting
in the configuration would also set
stateChangesOnly globally. This
coupling caused significant confusion, as the behavior of alerts and
TICKscripts would change as a result of enabling/disabling a handler.
With v0.11, there is the
state-changes-only setting, which
explicitly enables/disables the
stateChangesOnly attribute for
globally configured alerts. For example:
[slack] enabled = true ... global = true state-changes-only = false
With this change you can now control whether you want to receive alerts for all events or just state changes, regardless of a globally configured alert handler.
Note: To preserve the legacy behavior, add a
state-changes-only = trueoption to any of the handlers that have been configured globally.