[DOCS] Updates Watcher examples for code testing (#31152)

x-pack/docs/build.gradle

@@ -14,38 +14,6 @@ buildRestTests.expectedUnconvertedCandidates = [
         'en/security/authorization/run-as-privilege.asciidoc',
         'en/security/tribe-clients-integrations/http.asciidoc',
         'en/security/authorization/custom-roles-provider.asciidoc',
-        'en/watcher/actions/email.asciidoc',
-        'en/watcher/actions/hipchat.asciidoc',
-        'en/watcher/actions/index.asciidoc',
-        'en/watcher/actions/logging.asciidoc',
-        'en/watcher/actions/pagerduty.asciidoc',
-        'en/watcher/actions/slack.asciidoc',
-        'en/watcher/actions/jira.asciidoc',
-        'en/watcher/actions/webhook.asciidoc',
-        'en/watcher/condition/always.asciidoc',
-        'en/watcher/condition/array-compare.asciidoc',
-        'en/watcher/condition/compare.asciidoc',
-        'en/watcher/condition/never.asciidoc',
-        'en/watcher/condition/script.asciidoc',
-        'en/watcher/customizing-watches.asciidoc',
-        'en/watcher/example-watches/example-watch-meetupdata.asciidoc',
-        'en/watcher/how-watcher-works.asciidoc',
-        'en/watcher/input/chain.asciidoc',
-        'en/watcher/input/http.asciidoc',
-        'en/watcher/input/search.asciidoc',
-        'en/watcher/input/simple.asciidoc',
-        'en/watcher/transform.asciidoc',
-        'en/watcher/transform/chain.asciidoc',
-        'en/watcher/transform/script.asciidoc',
-        'en/watcher/transform/search.asciidoc',
-        'en/watcher/trigger/schedule/cron.asciidoc',
-        'en/watcher/trigger/schedule/daily.asciidoc',
-        'en/watcher/trigger/schedule/hourly.asciidoc',
-        'en/watcher/trigger/schedule/interval.asciidoc',
-        'en/watcher/trigger/schedule/monthly.asciidoc',
-        'en/watcher/trigger/schedule/weekly.asciidoc',
-        'en/watcher/trigger/schedule/yearly.asciidoc',
-        'en/watcher/troubleshooting.asciidoc',
         'en/rest-api/ml/delete-snapshot.asciidoc',
         'en/rest-api/ml/get-bucket.asciidoc',
         'en/rest-api/ml/get-job-stats.asciidoc',

x-pack/docs/en/watcher/actions/email.asciidoc

@@ -35,6 +35,7 @@ the watch payload in the email body:
   }
 }
 --------------------------------------------------
+// NOTCONSOLE
 <1> The id of the action.
 <2> The action type is set to `email`.
 <3> One or more addresses to send the email to. Must be specified in the
@@ -92,6 +93,7 @@ killed by firewalls or load balancers inbetween.
   }
 }
 --------------------------------------------------
+// NOTCONSOLE
 <1> The ID of the attachment, which is used as the file name in the email
     attachment.
 <2> The type of the attachment and its specific configuration.
@@ -158,9 +160,8 @@ include::{kib-repo-dir}/reporting/watch-example.asciidoc[]
 
 include::{kib-repo-dir}/reporting/report-intervals.asciidoc[]
 
-//TODO: RE-ADD LINK:
-//For more information, see
-//{kibana-ref}/automating-report-generation.html[Automating Report Generation].
+For more information, see
+{kibana-ref}/automating-report-generation.html[Automating Report Generation].
 
 [[email-action-attributes]]
 ==== Email Action Attributes

x-pack/docs/en/watcher/actions/hipchat.asciidoc

@@ -37,6 +37,7 @@ attribute is the message itself:
   }
 }
 --------------------------------------------------
+// NOTCONSOLE
 <1> The name of a HipChat account configured in `elasticsearch.yml`.
 <2> The message you want to send to HipChat.
 
@@ -66,6 +67,7 @@ For example, the following action is configured to send messages to the
   }
 }
 --------------------------------------------------
+// NOTCONSOLE
 
 To send messages with a HipChat account that uses the <<hipchat-api-v1, v1>>
 profile, you need to specify what room or rooms you want to send the message to.
@@ -92,7 +94,7 @@ For example, the following action is configured to send messages to the
   }
 }
 --------------------------------------------------
-
+// NOTCONSOLE
 
 [[hipchat-action-attributes]]
 ==== HipChat Action Attributes

x-pack/docs/en/watcher/actions/index.asciidoc

@@ -22,6 +22,7 @@ The following snippet shows a simple `index` action definition:
   }
 }
 --------------------------------------------------
+// NOTCONSOLE
 <1> The id of the action
 <2> An optional <<condition, condition>> to restrict action execution
 <3> An optional <<transform, transform>> to transform the payload and prepare the data that should be indexed

x-pack/docs/en/watcher/actions/jira.asciidoc

@@ -40,6 +40,7 @@ The following snippet shows a simple jira action definition:
   }
 }
 --------------------------------------------------
+// NOTCONSOLE
 <1> The name of a Jira account configured in `elasticsearch.yml`.
 <2> The key of the Jira project in which the issue will be created.
 <3> The name of the issue type.

x-pack/docs/en/watcher/actions/logging.asciidoc

@@ -25,6 +25,7 @@ The following snippet shows a simple logging action definition:
   }
 }
 --------------------------------------------------
+// NOTCONSOLE
 <1> The id of the action.
 <2> An optional <<transform, transform>> to transform the payload before
     executing the `logging` action.

x-pack/docs/en/watcher/actions/pagerduty.asciidoc

@@ -25,6 +25,7 @@ The following snippet shows a simple PagerDuty action definition:
   }
 }
 --------------------------------------------------
+// NOTCONSOLE
 <1> Description of the message
 
 
@@ -59,6 +60,7 @@ payload as well as an array of contexts to the action.
   }
 }
 --------------------------------------------------
+// NOTCONSOLE
 
 
 [[pagerduty-action-attributes]]

x-pack/docs/en/watcher/actions/slack.asciidoc

@@ -29,6 +29,7 @@ The following snippet shows a simple slack action definition:
   }
 }
 --------------------------------------------------
+// NOTCONSOLE
 <1> The channels and users you want to send the message to.
 <2> The content of the message.
 
@@ -66,6 +67,7 @@ The following snippet shows a standard message attachment:
   }
 }
 --------------------------------------------------
+// NOTCONSOLE
 
 [[slack-dynamic-attachment]]
 
@@ -131,6 +133,7 @@ aggregation and the Slack action:
   }
 }
 --------------------------------------------------
+// NOTCONSOLE
 <1> The list generated by the action's transform.
 <2> The parameter placeholders refer to attributes in each item of the list
     generated by the transform.

x-pack/docs/en/watcher/actions/webhook.asciidoc

@@ -30,6 +30,7 @@ The following snippet shows a simple webhook action definition:
   }
 }
 --------------------------------------------------
+// NOTCONSOLE
 <1> The id of the action
 <2> An optional <<transform, transform>> to transform the payload before
     executing the `webhook` action
@@ -65,6 +66,7 @@ For example, the following `webhook` action creates a new issue in GitHub:
   }
 }
 --------------------------------------------------
+// NOTCONSOLE
 <1> The username and password for the user creating the issue
 
 NOTE: By default, both the username and the password are stored in the `.watches`
@@ -101,6 +103,7 @@ the values serve as the parameter values:
   }
 }
 --------------------------------------------------
+// NOTCONSOLE
 <1> The parameter values can contain templated strings.
 
 
@@ -128,6 +131,7 @@ the values serve as the header values:
   }
 }
 --------------------------------------------------
+// NOTCONSOLE
 <1> The header values can contain templated strings.
 
 

x-pack/docs/en/watcher/condition/always.asciidoc

@@ -22,3 +22,4 @@ object:
   "always" : {}
 }
 --------------------------------------------------
+// NOTCONSOLE

x-pack/docs/en/watcher/condition/array-compare.asciidoc

@@ -34,6 +34,7 @@ than or equal to 25:
   }
 }
 --------------------------------------------------
+// NOTCONSOLE
 <1> The path to the array in the execution
     context that you want to evaluate, specified in dot notation.
 <2> The path to the field in each array element that you want to evaluate.

x-pack/docs/en/watcher/condition/compare.asciidoc

@@ -49,6 +49,7 @@ search result>> is greater than or equal to 5:
   }
 }
 --------------------------------------------------
+// NOTCONSOLE
 <1> Use dot notation to reference a value in the execution context.
 <2> Specify a comparison operator and the value you want to compare against.
 
@@ -68,6 +69,7 @@ of the form `<{expression}>`. For example, the following expression returns
   }
 }
 --------------------------------------------------
+// NOTCONSOLE
 
 You can also compare two values in the execution context by specifying the 
 compared value as a path of the form of `{{path}}`. For example, the following 
@@ -85,6 +87,7 @@ to the `ctx.payload.aggregations.handled.buckets.true.doc_count`:
   }
 }
 --------------------------------------------------
+// NOTCONSOLE
 
 ==== Accessing Values in the Execution Context
 

x-pack/docs/en/watcher/condition/never.asciidoc

@@ -17,3 +17,4 @@ you specify the condition type and associate it with an empty object:
   "never" : {}
 }
 --------------------------------------------------
+// NOTCONSOLE

x-pack/docs/en/watcher/condition/script.asciidoc

@@ -19,6 +19,7 @@ The following snippet configures an inline `script` condition that always return
   "script" : "return true"
 }
 --------------------------------------------------
+// NOTCONSOLE
 
 This example defines a script as a simple string. This format is actually a
 shortcut for defining an <<condition-script-inline, inline>> script. The
@@ -43,6 +44,7 @@ parameter, `result`:
   }
 }
 --------------------------------------------------
+// NOTCONSOLE
 
 [[condition-script-inline]]
 ==== Inline Scripts
@@ -59,6 +61,7 @@ always returns `true`.
   }
 }
 --------------------------------------------------
+// NOTCONSOLE
 
 [[condition-script-stored]]
 ==== Stored Scripts
@@ -74,6 +77,7 @@ in Elasticsearch. The following snippet shows how to refer to a script by its `i
   }
 }
 --------------------------------------------------
+// NOTCONSOLE
 
 As with <<condition-script-inline, Inline>>
 scripts, you can also specify the script language and parameters:
@@ -88,6 +92,7 @@ scripts, you can also specify the script language and parameters:
   }
 }
 --------------------------------------------------
+// NOTCONSOLE
 
 [[accessing-watch-payload]]
 ==== Accessing the Watch Payload
@@ -121,6 +126,7 @@ threshold:
   }
 }
 --------------------------------------------------
+// NOTCONSOLE
 
 When you're using a scripted condition to evaluate an Elasticsearch response,
 keep in mind that the fields in the response are no longer in their native data
@@ -132,6 +138,7 @@ you need to parse the `@timestamp` string into a `DateTime`. For example:
 --------------------------------------------------
 org.elasticsearch.common.joda.time.DateTime.parse(@timestamp)
 --------------------------------------------------
+// NOTCONSOLE
 
 You can reference the following variables in the watch context:
 

x-pack/docs/en/watcher/customizing-watches.asciidoc

@@ -36,6 +36,7 @@ fields in the payload:
   }
 }
 -------------------------------------
+// NOTCONSOLE
 
 See <<input-simple>> for more details.
 
@@ -74,6 +75,7 @@ For example, the following `search` input loads the latest VIX quote:
   }
 }
 --------------------------------------------------
+// NOTCONSOLE
 <1> Will resolve to today's daily quotes index
 
 See <<input-search>> for more details.
@@ -105,7 +107,7 @@ Amsterdam using http://openweathermap.org/appid[OpenWeatherMap] online service:
   }
 }
 --------------------------------------------------
-
+// NOTCONSOLE
 See <<input-http>> for more details.
 
 [[chaining-inputs]]
@@ -146,7 +148,7 @@ returned any hits:
     "compare" : { "ctx.payload.hits.total" : { "gt" : 0 }}
   },
 --------------------------------------------------
-
+// NOTCONSOLE
 See <<condition-compare>> for more details.
 
 ==== Powerful Comparison Logic with the Script Condition
@@ -176,7 +178,7 @@ VIX quote loaded by the `http` input is either greater than 5% or lower than -5%
   }
 }
 --------------------------------------------------
-
+// NOTCONSOLE
 See <<condition-script>> for more details.
 
 [[using-transforms]]
@@ -231,6 +233,7 @@ attaches the payload data to the message:
   }
 }
 --------------------------------------------------
+// NOTCONSOLE
 <1> The id of the action
 <2> The action type, in this case it's an `email` action
 
@@ -261,6 +264,7 @@ creates a new issue in GitHub
   }
 }
 --------------------------------------------------
+// NOTCONSOLE
 <1> `<owner>` is the owner of the GitHub repo and `<repo>` is the name of the repo.
 <2> The username that creates the issue
 <3> The password of that user