[DOCS] Migrating images to separate x-pack repos.

Original commit: elastic/x-pack-elasticsearch@80317c063b

docs/en/ml/getting-started.asciidoc

@@ -135,7 +135,7 @@ and `monitor_ml` roles (TBD).
 
 . Click **Machine Learning** in the side navigation.
 
-//image::ml.jpg["Job Management"]
+//image::images/ml.jpg["Job Management"]
 
 You can choose to create single-metric, multi-metric, or advanced jobs in Kibana.
 
@@ -267,4 +267,4 @@ locally, go to `http://localhost:5601/`.
 
 . Click **ML** in the side navigation ...
 ////
-//image::graph-open.jpg["Accessing Graph"]
+//image::images/graph-open.jpg["Accessing Graph"]

docs/en/ml/introduction.asciidoc

@@ -13,7 +13,7 @@ statistically significant influencers in the data.
 Automated periodicity detection and quick adaptation to changing data ensure
 that you don’t need to specify algorithms, models, or other data
 science-related configurations in order to get the benefits of {ml}.
-//image::graph-network.jpg["Graph network"]
+//image::images/graph-network.jpg["Graph network"]
 
 [float]
 === Integration with the Elastic Stack

docs/en/rest-api/graph.asciidoc

@@ -1,8 +1,6 @@
 [[graph-api]]
 == Graph APIs
 
-:imagesdir:         images/graph
-
 * <<graph-api-explore>>
 
 include::graph/explore.asciidoc[]

docs/en/rest-api/graph/explore.asciidoc

@@ -7,7 +7,7 @@ Graph UI to visually click around connected data and then view the "Last request
 panel (accessible from the button with the cog icon). This panel shows the JSON request/response
 pair of the last user operation.
 
-image::spy.jpg["Viewing the last request in the Kibana Graph UI"]
+image::images/spy.jpg["Viewing the last request in the Kibana Graph UI"]
 
 - <<basic-search, Basic exploration>>
 - <<optional-controls, Optional controls>>
@@ -111,7 +111,7 @@ The `doc_count` value indicates how many documents contain this pairing of terms
 In the Kibana Graph UI response data is visualized in a diagram like this:
 
 
-image::midiclicks.jpg["An example visualization of product/search click data using the Kibana Graph UI",width="50%", align="center"]
+image::images/midiclicks.jpg["An example visualization of product/search click data using the Kibana Graph UI",width="50%", align="center"]
 
 
 [float]

docs/en/security/index.asciidoc

@@ -1,8 +1,6 @@
 [[xpack-security]]
 = Securing Elasticsearch and Kibana
 
-:imagesdir:         images/security
-
 [partintro]
 --
 {security} enables you to easily secure a cluster. With Security,

docs/en/security/tribe-clients-integrations/kibana.asciidoc

@@ -172,7 +172,7 @@ Kibana locally, go to `https://localhost:5601` and enter the credentials for a
 user you've assigned a Kibana user role. For example, you could log in as the
 `jacknich` user created above.
 +
-image::kibana-login.jpg["Kibana Login",link="images/kibana-login.jpg"]
+image::images/kibana-login.jpg["Kibana Login",link="images/kibana-login.jpg"]
 +
 NOTE: This must be a user who has been assigned the `kibana_user` role.
 Kibana server credentials should only be used internally by the

docs/en/settings/monitoring-settings.asciidoc

@@ -1,8 +1,6 @@
 [[monitoring-settings]]
 == Monitoring Settings
 
-:imagesdir:         images/monitoring
-
 You configure <<monitoring-collection-settings, `xpack.monitoring.collection`>>
 settings in `elasticsearch.yml` to control how data is collected from your
 Elasticsearch nodes. You can adjust how monitoring data is displayed in the
@@ -156,7 +154,7 @@ display the CPU Utilization based on the reported Cgroup statistics. This will a
 Cgroup CPU Utilization to the Node Overview page instead of the overall operating system's CPU
 Utilization. Defaults to `false`.
 +
-image::monitoring-es-cgroup-true.png["Elasticsearch Inside a Container",link="images/monitoring-es-cgroup-true.png"]
+image::images/monitoring-es-cgroup-true.png["Elasticsearch Inside a Container",link="images/monitoring-es-cgroup-true.png"]
 
 [float]
 [[local-exporter-settings]]

docs/en/watcher/actions.asciidoc

@@ -184,7 +184,7 @@ of the action ids you want to acknowledge. To acknowledge all actions, omit the
 The following diagram illustrates the throttling decisions made for each action
 of a watch during its execution:
 
-image::action-throttling.jpg[align="center"]
+image::images/action-throttling.jpg[align="center"]
 
 include::actions/email.asciidoc[]
 

docs/en/watcher/actions/hipchat.asciidoc

@@ -205,13 +205,13 @@ account. To generate an authentication token:
 . Click the *Tokens* link.
 . Enter a name for the token in the *Label* field.
 +
-image::hipchat-generate-room-token.jpg[]
+image::images/hipchat-generate-room-token.jpg[]
 . Select the *Send Notification* scope.
 . Click *Create*.
 . Copy the generated token so you can paste it into your HipChat account
   configuration in `elasticsearch.yml`.
 +
-image::hipchat-copy-room-token.jpg[]
+image::images/hipchat-copy-room-token.jpg[]
 
 To configure a HipChat account that uses the `integration` profile:
 
@@ -268,13 +268,13 @@ Before you can configure a `user` account, you need to:
 .. Confirm the user password.
 .. Enter a name for the token in the *Label* field.
 +
-image::hipchat-generate-user-token.jpg[]
+image::images/hipchat-generate-user-token.jpg[]
 . Select the *Send Notification* and *Send Message* scopes.
 . Click *Create*.
 . Copy the generated token so you can paste it into your HipChat account
   configuration in `elasticsearch.yml`.
 +
-image::hipchat-copy-room-token.jpg[]
+image::images/hipchat-copy-room-token.jpg[]
 
 To configure a HipChat account that uses the `user` profile:
 
@@ -335,13 +335,13 @@ Before you can configure a `v1` account, you need to generate a `v1` API token:
 . Confirm your admin password.
 . Select the *Notification* type.
 +
-image::hipchat-generate-v1-token.jpg[]
+image::images/hipchat-generate-v1-token.jpg[]
 . Enter a name for the token in the *Label* field.
 . Click *Create*.
 . Copy the generated token so you can paste it into your HipChat account
   configuration in `elasticsearch.yml`.
 +
-image::hipchat-copy-v1-token.jpg[]
+image::images/hipchat-copy-v1-token.jpg[]
 
 To configure a HipChat account that uses the `v1` profile:
 

docs/en/watcher/actions/pagerduty.asciidoc

@@ -139,11 +139,11 @@ key:
 . Go to **Configuration > Services** and select the PagerDuty service. The 
 service must use the API integration.
 +
-image::pagerduty-services.jpg[]
+image::images/pagerduty-services.jpg[]
 
 . Click the **Integrations** tab and copy the API integration key.
 +
-image::pagerduty-integrations.jpg[]
+image::images/pagerduty-integrations.jpg[]
 
 To configure a PagerDuty account in `elasticsearch.yml`, at a minimum you
 must specify an account name and integration key:

docs/en/watcher/actions/slack.asciidoc

@@ -185,12 +185,12 @@ URL, set up an an _Incoming Webhook Integration_ through the Slack console:
 . Go to https://my.slack.com/services/new/incoming-webhook.
 . Select a default channel for the integration.
 +
-image::slack-add-webhook-integration.jpg[]
+image::images/slack-add-webhook-integration.jpg[]
 . Click *Add Incoming Webhook Integration*.
 . Copy the generated webhook URL so you can paste it into your Slack account
   configuration in `elasticsearch.yml`.
 +
-image::slack-copy-webhook-url.jpg[]
+image::images/slack-copy-webhook-url.jpg[]
 
 To configure a Slack account, at a minimum you need to specify the account 
 name and webhook URL:

docs/en/watcher/how-watcher-works.asciidoc

@@ -171,7 +171,7 @@ action that was executed.
 
 The following diagram shows the watch execution process:
 
-image::watch-execution.jpg[align="center"]
+image::images/watch-execution.jpg[align="center"]
 
 [float]
 [[watch-acknowledgment-throttling]]

docs/en/watcher/index.asciidoc

@@ -1,8 +1,6 @@
 [[xpack-alerting]]
 = Alerting on Cluster and Index Events
 
-:imagesdir:         images/watcher
-
 [partintro]
 --
 You can watch for changes or anomalies in your data and perform the necessary