Announcing Kapacitor 0.2.0
Nathaniel Cook /
Dec 07, 2015
Kapacitor version 0.2.0 has been released today. What’s Kapacitor? If you missed out announcement last week, it’s the “K” in the TICK stack. Kapacitor is an alerting and data processing engine for time series data. It lets you define your own custom pipeline to aggregate, select, transform or otherwise process data and then store it back in InfluxDB or trigger an event.
- Stream data from InfluxDB or query from InfluxDB
- Trigger events/alerts based on complex or dynamic criteria
- Perform any transformation currently possible in InfluxQL, for example: SUM, MIN, MAX, etc.
- Store transformed data back into InfluxDB
- Process historical data, for example: backfill data using a processing pipeline
This release is a bug fix release since the initial release last week. We want to commit to making regular updates to Kapacitor, so we are going to follow a regular release cadance. If a feature is ready when the next release comes around it will be included, if not it will have to wait for a later release. Iteratively we will be able to fix bugs and push out quality features. Our initial plans are to cut a release every month. Time will tell if this is the right cadance for Kapacitor or if we should adjust.
We have received great feedback from the community in the past several days since the initial release. We are constructing a roadmap based on that feedback for the next several months of feature development for Kapacitor. The next big feature to hit Kapacitor will be custom user functions. This will enable you to plugin in your own custom algorithms for running anomaly detection or ETL jobs, etc. Since integrating your custom code to another software stack can be tedious and difficult process, we are making ease of use a priority for this feature. We want to get it right so that it meets your needs while not being a difficult and cumbersome task. One of our big questions for the community is what languages would you like supported for integrating your algorithms with Kapacitor? Let us know on the github issue here. Or if you have specific ideas on how you would like to see this feature work please chime in as well.
That’s it for now. Kapacitor’s next release will be in January.