diff --git a/docs/static/breaking-changes.asciidoc b/docs/static/breaking-changes.asciidoc index 64b15808d..603ee94ea 100644 --- a/docs/static/breaking-changes.asciidoc +++ b/docs/static/breaking-changes.asciidoc @@ -5,7 +5,7 @@ Although 2.2 is fully compatible with configurations from older versions, there are some architectural changes to the pipeline that users need to take into consideration before deploying in production. These changes are not strictly "breaking" in the semantic versioning sense, but they make Logstash behave differently -in runtime, and can also affect performance. We have compiled such a list in the <<_upgrading_logstash_to_2.2>> section. +in runtime, and can also affect performance. We have compiled such a list in the <> section. Please review it before deploying 2.2 version. **Changes in 2.0** diff --git a/docs/static/upgrading.asciidoc b/docs/static/upgrading.asciidoc index 144954932..a4465decc 100644 --- a/docs/static/upgrading.asciidoc +++ b/docs/static/upgrading.asciidoc @@ -78,6 +78,7 @@ of workers by passing a command line flag such as: [source,shell] bin/logstash `-w 1` +[[upgrading-logstash-2.2]] === Upgrading Logstash to 2.2 Logstash 2.2 re-architected the pipeline stages to provide more performance and help future enhancements in resiliency.