Docs: Consolidated Watcher 2.0 release notes. Fixed pkg install cmds and subscription links for Watcher & Shield.
Original commit: elastic/x-pack-elasticsearch@1387a61a8f
This commit is contained in:
debadair
parent
604975d2c1
commit
e81e640190
|
|
@ -32,8 +32,8 @@ To install the Shield and License plugins on a DEB/RPM package installation, you
|
|||
[source,shell]
|
||||
----------------------------------------------------------
|
||||
cd /usr/share/elasticsearch
|
||||
sudo bin/plugin -i license
|
||||
sudo bin/plugin -i shield
|
||||
sudo bin/plugin install license
|
||||
sudo bin/plugin install shield
|
||||
----------------------------------------------------------
|
||||
|
||||
[float]
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
[[license-management]]
|
||||
== Managing Your License
|
||||
|
||||
When you initially install Shield, a 30 day trial license is installed that allows access to all features. At the end of the trial period, you can https://www.elastic.co/subscriptions/shield[purchase a subscription] to keep using the full functionality of Shield along with Marvel and Watcher.
|
||||
When you initially install Shield, a 30 day trial license is installed that allows access to all features. At the end of the trial period, you can https://www.elastic.co/subscriptions/[purchase a subscription] to keep using the full functionality of Shield along with Marvel and Watcher.
|
||||
|
||||
IMPORTANT: When your license expires, Shield operates in a degraded mode where access to the Elasticsearch cluster health, cluster stats, and index stats APIs is blocked. Shield keeps on protecting your cluster, but you won't be able to monitor its operation until you update your license. For more information, see <<license-expiration, License Expiration>>.
|
||||
|
||||
|
|
|
|||
|
|
@ -73,8 +73,8 @@ To install the Watcher and License plugins on a DEB/RPM package installation, yo
|
|||
[source,shell]
|
||||
----------------------------------------------------------
|
||||
cd /usr/share/elasticsearch
|
||||
sudo bin/plugin -i license
|
||||
sudo bin/plugin -i watcher
|
||||
sudo bin/plugin install license
|
||||
sudo bin/plugin install watcher
|
||||
----------------------------------------------------------
|
||||
|
||||
[float]
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
== Managing Your License
|
||||
|
||||
When you initially install Watcher, a 30 day trial license is installed that allows access to all
|
||||
features. At the end of the trial period, you can https://www.elastic.co/subscriptions/watcher[purchase a subscription] to keep using the full functionality of Watcher along with Shield and Marvel.
|
||||
features. At the end of the trial period, you can https://www.elastic.co/subscriptions/[purchase a subscription] to keep using the full functionality of Watcher along with Shield and Marvel.
|
||||
|
||||
IMPORTANT: When your license expires, your watches will still be triggered but no actions will
|
||||
be performed. You will not be able to get existing watches or add new ones, but you can still
|
||||
|
|
|
|||
|
|
@ -45,13 +45,7 @@ bin/plugin remove watcher
|
|||
[[float]
|
||||
==== 2.0.0
|
||||
|
||||
.Bug fixes
|
||||
* Fixed an issue where the scheduler may get stuck during Watcher startup. This caused no watches to ever fire.
|
||||
|
||||
[float]
|
||||
==== 2.0.0-rc1
|
||||
|
||||
.Breaking
|
||||
.Breaking Changes
|
||||
* The dynamic index names support has been removed and Elasticsearch's date math index names support should be used instead.
|
||||
The only difference between Watcher's dynamic index names support and Elasticsearch's date math index names support is
|
||||
how timezones are expressed. In Watcher this is done via node settings, in Elasticsearch the timezone is part of the
|
||||
|
|
@ -60,16 +54,6 @@ bin/plugin remove watcher
|
|||
`watcher.dynamic_indices.time_zone` setting was set to `+01:00` and a watch has the following index name `<logstash-{now/d}>`
|
||||
then after the upgrade you need to update this watch to use the following index name `<logstash-{now/d{YYYY.MM.dd|+01:00}}>`.
|
||||
|
||||
.Enhancements
|
||||
* If `action.auto_create_index` setting has been configured then Watcher will check if the setting is too restrictive.
|
||||
If the `action.auto_create_index` is too restrictive then Watcher will fail during startup with a descriptive error message.
|
||||
|
||||
.Bug Fixes
|
||||
* Fixed url encoding issue in http input and webhook output. The url params were url encoded twice.
|
||||
|
||||
[float]
|
||||
==== 2.0.0-beta2
|
||||
|
||||
.New Features
|
||||
* Added new <<actions-hipchat, HipChat Action>>
|
||||
* Added new <<actions-slack, Slack Action>>
|
||||
|
|
@ -78,17 +62,6 @@ bin/plugin remove watcher
|
|||
* Added new <<condition-array-compare, array-compare>>, that can compare an array of values in the
|
||||
<<watch-execution-context, Watch Execution Context Model>> to a given value.
|
||||
|
||||
.Bug Fixes
|
||||
* If Watcher was installed with Shield then the Watcher index templates couldn't be stored and could lead
|
||||
to Watcher behaving incorrectly. This was caused by Watcher not detecting correctly if Shield was installed.
|
||||
* Update `croneval` command line utility to properly handle whitespaces in the elasticsearch home path.
|
||||
|
||||
[float]
|
||||
==== 2.0.0-beta1
|
||||
|
||||
This release is primarily for compatibility with Elasticsearch 2.0.0-beta1 and the Watcher versioning has
|
||||
been aligned with the Elasticsearch versioning.
|
||||
|
||||
.Enhancements
|
||||
* Watcher continuously checks if the index templates for `.watches`, `.triggered_watches`
|
||||
and `.watch_history-*` exist. Whereas before the existence of these index templates was
|
||||
|
|
@ -99,6 +72,15 @@ been aligned with the Elasticsearch versioning.
|
|||
* During Watcher start up only wait for the shards of the `.watches` and `.triggered_watches`
|
||||
indices to be available. Before Watcher also waited for the shards of the `.watch_history-*`
|
||||
indices, which wasn't needed. This improved time it takes for Watcher to startup.
|
||||
* If `action.auto_create_index` setting has been configured then Watcher will check if the setting is too restrictive.
|
||||
If the `action.auto_create_index` is too restrictive then Watcher will fail during startup with a descriptive error message.
|
||||
|
||||
.Bug Fixes
|
||||
* If Watcher was installed with Shield then the Watcher index templates couldn't be stored and could lead
|
||||
to Watcher behaving incorrectly. This was caused by Watcher not detecting correctly if Shield was installed.
|
||||
* Update `croneval` command line utility to properly handle whitespaces in the elasticsearch home path.
|
||||
* Fixed an issue where the scheduler may get stuck during Watcher startup. This caused no watches to ever fire.
|
||||
* Fixed url encoding issue in http input and webhook output. The url params were url encoded twice.
|
||||
|
||||
[float]
|
||||
==== 1.0.0
|
||||
|
|
|
|||
Loading…
Reference in New Issue