Originally published at: Release Announcement: Kapacitor 1.6.1 - InfluxData
A new feature-bearing release of Kapacitor is available now.
- Kapacitor 1.6.1 — release notes
This release for Kapacitor includes the following fixes and improvements:
-
Flux Tasks
- Kapacitor now includes an embedded Flux engine to allow for Flux scripts to be scheduled. A Flux script associated with a schedule represents a Flux Task.
- Flux Tasks can be defined and managed using the Kapacitor CLI. Kapacitor also exposes the v2 Task API making it forward compatible with InfluxDB v2 and InfluxDB Cloud.
- Information about task runs can also be stored into InfluxDB and visualized via Chronograf 1.9.
-
Security
- User authentication and authorization (previously only supported in Kapacitor Enterprise) has been backported to Kapacitor OSS 1.6. You can configure Kapacitor to leverage InfluxDB Enterprise as an authentication and authorization for interactions with the Kapacitor API.
- We’ve added a couple of configuration options to allow for stronger control over CIDR ranges for certain handlers, and nodes and for disabling alert handlers, which can be particularly useful for disabling the exec handler on a shared host.
-
Event Handlers
- Zenoss: New event handler!
- Kafka: Kafka alerts are now routed to partitions by message ID and support hashing strategy configuration.
- Slack: the Slack event handler now supports the new Slack App integration approach.
- BigPanda: we addressed an issue with payload serialization.
-
TICKscript
-
TrickleNode
: converts from batch edges to stream edges. Children of trickle are treated as if they are in a stream.
-
-
Platform support
- Kapacitor 1.6.x no longer supports 32-bit operating systems. If you are still using a 32-bit operating system, continue to leverage Kapacitor 1.5.x.
- Builds have been provided for ARM 64-bit.
The binaries for the latest open source release can be found on our downloads page.
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.