Release Notes

edit

Release Notes

edit

Version Compatibility

edit

Watcher 1.0.0 is compatible with:

Elasticsearch: 1.5.2+
License: 1.0
Shield: 1.2.2

Upgrading Watcher

edit

To upgrade Watcher, just uninstall the current Watcher plugin and install the new version of Watcher. Your watches and watch history will be preserved and you do this with a rolling upgrade of Elasticsearch. On each node, after you have stopped it run:

bin/plugin remove watcher
bin/plugin install elasticsearch/watcher/latest

latest will install the latest version of Watcher compatible with your version of Elasticsearch. A specific version, such as 1.0.1 can also be specified.

Then start the node. Larger sites should follow the steps in the rolling upgrade section in order to ensure recovery is as quick as possible.

Upgrading Watcher from beta or rc release

edit

Watcher 1.0.0 is not backward compatible with Watcher 1.0.0-rc1 and before. If you are on a beta or rc release then follow the following steps:

Back up all of the watches you’ve defined. You can search/scan the .watches index and save the returned watches aside.
Stop Elasticsearch on all nodes in your cluster.
Uninstall the Watcher plugin from each node:
```
bin/plugin -r watcher
```
Restart Elasticsearch on each node.
Delete the .watches index and all of the existing .watch_history-* indices
```
DELETE .watches
```
```
DELETE .watch_history*
```
Stop Elasticsearch on all nodes in your cluster.
From here on you can simply follow the Getting Started guide. If you are upgrading from Beta1, you can skip the license installation as both Beta1 and Beta2 are compatible with the same license version (1.0.0). Once Watcher is installed, you can use the PUT Watch API to restore your backed up watches.

Change List

edit

1.0.2

edit

Bug fixes

Fixed an issue where the scheduler may get stuck during Watcher startup. This caused no watches to ever fire.

1.0.1

edit

Enhancements

Added time zone support to dynamic index names. Before the timezone was fixed to UTC.

Bug Fixes

Fixed a rare bug when stopping Watcher manually, it would start again a small moment later.
Made Watcher compatible with Elasticsearch 1.6.2 and 1.7.1

1.0.0

edit

Enhancements

Added execution time aware dynamic index names support to index action, search input, and search transform.
You must now explicitly specify the unit when configuring any time value. (Numeric-only values are no longer supported.)
Cleaned up the Get Watch API response.
Cleaned up the Stats API response.

1.0.0-rc1

edit

New Features

Added inline watch support to the Execute API

Enhancements

Added execution context variables support.
Email html body sanitization is now configurable.
It is now possible to configure timeouts for http requests in HTTP input and webhook actions.

1.0.0-Beta2

edit

New Features

Acking and Throttling are now applied at the action level rather than the watch level.
Added support for multi-doc indexing to the index action.
Added a queued watches metric that’s accessible via the Stats API.
Added a currently-executing watches metric that’s accessible via the Stats API.

Enhancements

The compare condition result now includes the value of each field that was referenced in the comparison.
The Execute API now supports a default trigger event (breaking change)
The watch_record document structure in the .watch_history-* indices has changed significantly (breaking change)
A new internal index was introduced - .triggered_watches
Added support for headers in the Webhook Action result and the HTTP Input result.
Add plain text response body support for the HTTP Input.

Bug Fixes

Disallow negative time value settings for throttle_period
Added support for separate keystore and truststore in Webhook Action and HTTP Input.

« Troubleshooting