Versioned plugin docs

docs/versioned-plugins/filters/grok-v3.4.1.asciidoc

@@ -160,7 +160,7 @@ filter. This newly defined patterns in `pattern_definitions` will not be availab
 [id="{version}-plugins-{type}s-{plugin}-options"]
 ==== Grok Filter Configuration Options
 
-This plugin supports the following configuration options plus the <<{version}-plugins-{type}s-{plugin}-common-options>> described later.
+This plugin supports the following configuration options plus the <<plugins-{type}s-common-options>> described later.
 
 [cols="<,<,<",options="header",]
 |=======================================================================
@@ -178,7 +178,7 @@ This plugin supports the following configuration options plus the <<{version}-pl
 | <<{version}-plugins-{type}s-{plugin}-timeout_millis>> |{logstash-ref}/configuration-file-structure.html#number[number]|No
 |=======================================================================
 
-Also see <<{version}-plugins-{type}s-{plugin}-common-options>> for a list of options supported by all
+Also see <<plugins-{type}s-common-options>> for a list of options supported by all
 filter plugins.
 
 &nbsp;
@@ -328,5 +328,5 @@ Actual timeout is approximate based on a 250ms quantization.
 Set to 0 to disable timeouts
 
 
-[id="{version}-plugins-{type}s-{plugin}-common-options"]
+
 include::{include_path}/{type}.asciidoc[]

docs/versioned-plugins/filters/ruby-v3.1.0.asciidoc

@@ -188,14 +188,5 @@ The path of the ruby script file that implements the `filter` method.
 A key/value hash with parameters that are passed to the register method
 of your ruby script file defined in `path`.
 
-[id="{version}-plugins-{type}s-{plugin}-tag_on_exception"]
-===== `tag_on_exception`
-
-  * Value type is {logstash-ref}/configuration-file-structure.html#string[string]
-  * Default value is `_rubyexception`
-
-Tag to add to events in case the ruby code (either inline or file based)
-causes an exception.
-
 [id="{version}-plugins-{type}s-{plugin}-common-options"]
 include::{include_path}/{type}.asciidoc[]

docs/versioned-plugins/filters/ruby-v3.1.1.asciidoc

@@ -188,14 +188,5 @@ The path of the ruby script file that implements the `filter` method.
 A key/value hash with parameters that are passed to the register method
 of your ruby script file defined in `path`.
 
-[id="{version}-plugins-{type}s-{plugin}-tag_on_exception"]
-===== `tag_on_exception`
-
-  * Value type is {logstash-ref}/configuration-file-structure.html#string[string]
-  * Default value is `_rubyexception`
-
-Tag to add to events in case the ruby code (either inline or file based)
-causes an exception.
-
 [id="{version}-plugins-{type}s-{plugin}-common-options"]
 include::{include_path}/{type}.asciidoc[]

docs/versioned-plugins/filters/ruby-v3.1.2.asciidoc

@@ -188,14 +188,5 @@ The path of the ruby script file that implements the `filter` method.
 A key/value hash with parameters that are passed to the register method
 of your ruby script file defined in `path`.
 
-[id="{version}-plugins-{type}s-{plugin}-tag_on_exception"]
-===== `tag_on_exception`
-
-  * Value type is {logstash-ref}/configuration-file-structure.html#string[string]
-  * Default value is `_rubyexception`
-
-Tag to add to events in case the ruby code (either inline or file based)
-causes an exception.
-
 [id="{version}-plugins-{type}s-{plugin}-common-options"]
 include::{include_path}/{type}.asciidoc[]

docs/versioned-plugins/inputs/beats-v4.0.1.asciidoc

@@ -46,20 +46,20 @@ output {
 
 NOTE: The Beats shipper automatically sets the `type` field on the event.
 You cannot override this setting in the Logstash config. If you specify
-a setting for the <<{version}-plugins-inputs-beats-type,`type`>> config option in
+a setting for the <<{version}-plugins-{type}s-{plugin}-type,`type`>> config option in
 Logstash, it is ignored.
 
 IMPORTANT: If you are shipping events that span multiple lines, you need to
 use the https://www.elastic.co/guide/en/beats/filebeat/current/multiline-examples.html[configuration options available in Filebeat] to handle multiline events
 before sending the event data to Logstash. You cannot use the
-{logstash-ref}/plugins-codecs-multiline.html[Multiline codec plugin] codec to handle multiline events. Doing so will
+<<plugins-codecs-multiline>> codec to handle multiline events. Doing so will
 result in the failure to start Logstash.
 
 
 [id="{version}-plugins-{type}s-{plugin}-options"]
 ==== Beats Input Configuration Options
 
-This plugin supports the following configuration options plus the <<{version}-plugins-{type}s-{plugin}-common-options>> described later.
+This plugin supports the following configuration options plus the <<plugins-{type}s-common-options>> described later.
 
 [cols="<,<,<",options="header",]
 |=======================================================================
@@ -80,7 +80,7 @@ This plugin supports the following configuration options plus the <<{version}-pl
 | <<{version}-plugins-{type}s-{plugin}-tls_min_version>> |{logstash-ref}/configuration-file-structure.html#number[number]|No
 |=======================================================================
 
-Also see <<{version}-plugins-{type}s-{plugin}-common-options>> for a list of options supported by all
+Also see <<plugins-{type}s-common-options>> for a list of options supported by all
 input plugins.
 
 &nbsp;
@@ -236,5 +236,5 @@ The minimum TLS version allowed for the encrypted connections. The value must be
 1.0 for TLS 1.0, 1.1 for TLS 1.1, 1.2 for TLS 1.2
 
 
-[id="{version}-plugins-{type}s-{plugin}-common-options"]
+
 include::{include_path}/{type}.asciidoc[]

docs/versioned-plugins/inputs/beats-v4.0.2.asciidoc

@@ -46,20 +46,20 @@ output {
 
 NOTE: The Beats shipper automatically sets the `type` field on the event.
 You cannot override this setting in the Logstash config. If you specify
-a setting for the <<{version}-plugins-inputs-beats-type,`type`>> config option in
+a setting for the <<{version}-plugins-{type}s-{plugin}-type,`type`>> config option in
 Logstash, it is ignored.
 
 IMPORTANT: If you are shipping events that span multiple lines, you need to
 use the https://www.elastic.co/guide/en/beats/filebeat/current/multiline-examples.html[configuration options available in Filebeat] to handle multiline events
 before sending the event data to Logstash. You cannot use the
-{logstash-ref}/plugins-codecs-multiline.html[Multiline codec plugin] codec to handle multiline events. Doing so will
+<<plugins-codecs-multiline>> codec to handle multiline events. Doing so will
 result in the failure to start Logstash.
 
 
 [id="{version}-plugins-{type}s-{plugin}-options"]
 ==== Beats Input Configuration Options
 
-This plugin supports the following configuration options plus the <<{version}-plugins-{type}s-{plugin}-common-options>> described later.
+This plugin supports the following configuration options plus the <<plugins-{type}s-common-options>> described later.
 
 [cols="<,<,<",options="header",]
 |=======================================================================
@@ -80,7 +80,7 @@ This plugin supports the following configuration options plus the <<{version}-pl
 | <<{version}-plugins-{type}s-{plugin}-tls_min_version>> |{logstash-ref}/configuration-file-structure.html#number[number]|No
 |=======================================================================
 
-Also see <<{version}-plugins-{type}s-{plugin}-common-options>> for a list of options supported by all
+Also see <<plugins-{type}s-common-options>> for a list of options supported by all
 input plugins.
 
 &nbsp;
@@ -236,5 +236,5 @@ The minimum TLS version allowed for the encrypted connections. The value must be
 1.0 for TLS 1.0, 1.1 for TLS 1.1, 1.2 for TLS 1.2
 
 
-[id="{version}-plugins-{type}s-{plugin}-common-options"]
-include::{include_path}/{type}.asciidoc[]
+
+include::{include_path}/{type}.asciidoc[]

docs/versioned-plugins/inputs/beats-v4.0.3.asciidoc

@@ -46,20 +46,20 @@ output {
 
 NOTE: The Beats shipper automatically sets the `type` field on the event.
 You cannot override this setting in the Logstash config. If you specify
-a setting for the <<{version}-plugins-inputs-beats-type,`type`>> config option in
+a setting for the <<{version}-plugins-{type}s-{plugin}-type,`type`>> config option in
 Logstash, it is ignored.
 
 IMPORTANT: If you are shipping events that span multiple lines, you need to
 use the https://www.elastic.co/guide/en/beats/filebeat/current/multiline-examples.html[configuration options available in Filebeat] to handle multiline events
 before sending the event data to Logstash. You cannot use the
-{logstash-ref}/plugins-codecs-multiline.html[Multiline codec plugin] codec to handle multiline events. Doing so will
+<<plugins-codecs-multiline>> codec to handle multiline events. Doing so will
 result in the failure to start Logstash.
 
 
 [id="{version}-plugins-{type}s-{plugin}-options"]
 ==== Beats Input Configuration Options
 
-This plugin supports the following configuration options plus the <<{version}-plugins-{type}s-{plugin}-common-options>> described later.
+This plugin supports the following configuration options plus the <<plugins-{type}s-common-options>> described later.
 
 [cols="<,<,<",options="header",]
 |=======================================================================
@@ -80,7 +80,7 @@ This plugin supports the following configuration options plus the <<{version}-pl
 | <<{version}-plugins-{type}s-{plugin}-tls_min_version>> |{logstash-ref}/configuration-file-structure.html#number[number]|No
 |=======================================================================
 
-Also see <<{version}-plugins-{type}s-{plugin}-common-options>> for a list of options supported by all
+Also see <<plugins-{type}s-common-options>> for a list of options supported by all
 input plugins.
 
 &nbsp;
@@ -236,5 +236,5 @@ The minimum TLS version allowed for the encrypted connections. The value must be
 1.0 for TLS 1.0, 1.1 for TLS 1.1, 1.2 for TLS 1.2
 
 
-[id="{version}-plugins-{type}s-{plugin}-common-options"]
+
 include::{include_path}/{type}.asciidoc[]

docs/versioned-plugins/inputs/beats-v4.0.4.asciidoc

@@ -46,13 +46,13 @@ output {
 
 NOTE: The Beats shipper automatically sets the `type` field on the event.
 You cannot override this setting in the Logstash config. If you specify
-a setting for the <<{version}-plugins-inputs-beats-type,`type`>> config option in
+a setting for the <<{version}-plugins-{type}s-{plugin}-type,`type`>> config option in
 Logstash, it is ignored.
 
 IMPORTANT: If you are shipping events that span multiple lines, you need to
 use the https://www.elastic.co/guide/en/beats/filebeat/current/multiline-examples.html[configuration options available in Filebeat] to handle multiline events
 before sending the event data to Logstash. You cannot use the
-{logstash-ref}/plugins-codecs-multiline.html[Multiline codec plugin] codec to handle multiline events. Doing so will
+<<plugins-codecs-multiline>> codec to handle multiline events. Doing so will
 result in the failure to start Logstash.
 
 

docs/versioned-plugins/inputs/beats-v4.0.5.asciidoc

@@ -46,13 +46,13 @@ output {
 
 NOTE: The Beats shipper automatically sets the `type` field on the event.
 You cannot override this setting in the Logstash config. If you specify
-a setting for the <<{version}-plugins-inputs-beats-type,`type`>> config option in
+a setting for the <<{version}-plugins-{type}s-{plugin}-type,`type`>> config option in
 Logstash, it is ignored.
 
 IMPORTANT: If you are shipping events that span multiple lines, you need to
 use the https://www.elastic.co/guide/en/beats/filebeat/current/multiline-examples.html[configuration options available in Filebeat] to handle multiline events
 before sending the event data to Logstash. You cannot use the
-{logstash-ref}/plugins-codecs-multiline.html[Multiline codec plugin] codec to handle multiline events. Doing so will
+<<plugins-codecs-multiline>> codec to handle multiline events. Doing so will
 result in the failure to start Logstash.
 
 

docs/versioned-plugins/inputs/beats-v5.0.0.asciidoc

@@ -46,13 +46,13 @@ output {
 
 NOTE: The Beats shipper automatically sets the `type` field on the event.
 You cannot override this setting in the Logstash config. If you specify
-a setting for the <<{version}-plugins-inputs-beats-type,`type`>> config option in
+a setting for the <<{version}-plugins-{type}s-{plugin}-type,`type`>> config option in
 Logstash, it is ignored.
 
 IMPORTANT: If you are shipping events that span multiple lines, you need to
 use the https://www.elastic.co/guide/en/beats/filebeat/current/multiline-examples.html[configuration options available in Filebeat] to handle multiline events
 before sending the event data to Logstash. You cannot use the
-{logstash-ref}/plugins-codecs-multiline.html[Multiline codec plugin] codec to handle multiline events. Doing so will
+<<plugins-codecs-multiline>> codec to handle multiline events. Doing so will
 result in the failure to start Logstash.
 
 

docs/versioned-plugins/inputs/beats-v5.0.1.asciidoc

@@ -46,13 +46,13 @@ output {
 
 NOTE: The Beats shipper automatically sets the `type` field on the event.
 You cannot override this setting in the Logstash config. If you specify
-a setting for the <<{version}-plugins-inputs-beats-type,`type`>> config option in
+a setting for the <<{version}-plugins-{type}s-{plugin}-type,`type`>> config option in
 Logstash, it is ignored.
 
 IMPORTANT: If you are shipping events that span multiple lines, you need to
 use the https://www.elastic.co/guide/en/beats/filebeat/current/multiline-examples.html[configuration options available in Filebeat] to handle multiline events
 before sending the event data to Logstash. You cannot use the
-{logstash-ref}/plugins-codecs-multiline.html[Multiline codec plugin] codec to handle multiline events. Doing so will
+<<plugins-codecs-multiline>> codec to handle multiline events. Doing so will
 result in the failure to start Logstash.
 
 

docs/versioned-plugins/inputs/beats-v5.0.2.asciidoc

@@ -46,13 +46,13 @@ output {
 
 NOTE: The Beats shipper automatically sets the `type` field on the event.
 You cannot override this setting in the Logstash config. If you specify
-a setting for the <<{version}-plugins-inputs-beats-type,`type`>> config option in
+a setting for the <<{version}-plugins-{type}s-{plugin}-type,`type`>> config option in
 Logstash, it is ignored.
 
 IMPORTANT: If you are shipping events that span multiple lines, you need to
 use the https://www.elastic.co/guide/en/beats/filebeat/current/multiline-examples.html[configuration options available in Filebeat] to handle multiline events
 before sending the event data to Logstash. You cannot use the
-{logstash-ref}/plugins-codecs-multiline.html[Multiline codec plugin] codec to handle multiline events. Doing so will
+<<plugins-codecs-multiline>> codec to handle multiline events. Doing so will
 result in the failure to start Logstash.
 
 

docs/versioned-plugins/inputs/beats-v5.0.3.asciidoc

@@ -46,13 +46,13 @@ output {
 
 NOTE: The Beats shipper automatically sets the `type` field on the event.
 You cannot override this setting in the Logstash config. If you specify
-a setting for the <<{version}-plugins-inputs-beats-type,`type`>> config option in
+a setting for the <<{version}-plugins-{type}s-{plugin}-type,`type`>> config option in
 Logstash, it is ignored.
 
 IMPORTANT: If you are shipping events that span multiple lines, you need to
 use the https://www.elastic.co/guide/en/beats/filebeat/current/multiline-examples.html[configuration options available in Filebeat] to handle multiline events
 before sending the event data to Logstash. You cannot use the
-{logstash-ref}/plugins-codecs-multiline.html[Multiline codec plugin] codec to handle multiline events. Doing so will
+<<plugins-codecs-multiline>> codec to handle multiline events. Doing so will
 result in the failure to start Logstash.
 
 

docs/versioned-plugins/inputs/beats-v5.0.4.asciidoc

@@ -46,13 +46,13 @@ output {
 
 NOTE: The Beats shipper automatically sets the `type` field on the event.
 You cannot override this setting in the Logstash config. If you specify
-a setting for the <<{version}-plugins-inputs-beats-type,`type`>> config option in
+a setting for the <<{version}-plugins-{type}s-{plugin}-type,`type`>> config option in
 Logstash, it is ignored.
 
 IMPORTANT: If you are shipping events that span multiple lines, you need to
 use the https://www.elastic.co/guide/en/beats/filebeat/current/multiline-examples.html[configuration options available in Filebeat] to handle multiline events
 before sending the event data to Logstash. You cannot use the
-{logstash-ref}/plugins-codecs-multiline.html[Multiline codec plugin] codec to handle multiline events. Doing so will
+<<plugins-codecs-multiline>> codec to handle multiline events. Doing so will
 result in the failure to start Logstash.
 
 

docs/versioned-plugins/inputs/beats-v5.0.5.asciidoc

@@ -46,13 +46,13 @@ output {
 
 NOTE: The Beats shipper automatically sets the `type` field on the event.
 You cannot override this setting in the Logstash config. If you specify
-a setting for the <<{version}-plugins-inputs-beats-type,`type`>> config option in
+a setting for the <<{version}-plugins-{type}s-{plugin}-type,`type`>> config option in
 Logstash, it is ignored.
 
 IMPORTANT: If you are shipping events that span multiple lines, you need to
 use the https://www.elastic.co/guide/en/beats/filebeat/current/multiline-examples.html[configuration options available in Filebeat] to handle multiline events
 before sending the event data to Logstash. You cannot use the
-{logstash-ref}/plugins-codecs-multiline.html[Multiline codec plugin] codec to handle multiline events. Doing so will
+<<plugins-codecs-multiline>> codec to handle multiline events. Doing so will
 result in the failure to start Logstash.
 
 

docs/versioned-plugins/inputs/beats-v5.0.6.asciidoc

@@ -46,13 +46,13 @@ output {
 
 NOTE: The Beats shipper automatically sets the `type` field on the event.
 You cannot override this setting in the Logstash config. If you specify
-a setting for the <<{version}-plugins-inputs-beats-type,`type`>> config option in
+a setting for the <<{version}-plugins-{type}s-{plugin}-type,`type`>> config option in
 Logstash, it is ignored.
 
 IMPORTANT: If you are shipping events that span multiple lines, you need to
 use the https://www.elastic.co/guide/en/beats/filebeat/current/multiline-examples.html[configuration options available in Filebeat] to handle multiline events
 before sending the event data to Logstash. You cannot use the
-{logstash-ref}/plugins-codecs-multiline.html[Multiline codec plugin] codec to handle multiline events. Doing so will
+<<plugins-codecs-multiline>> codec to handle multiline events. Doing so will
 result in the failure to start Logstash.