[DOCS] Move monitoring folder to docs (elastic#9677)

docs/index.asciidoc

@@ -132,8 +132,8 @@ ifdef::include-xpack[]
 :edit_url: https://github.com/elastic/logstash/edit/{branch}/x-pack/docs/en/management/configuring-centralized-pipelines.asciidoc
 include::{xls-repo-dir}/management/configuring-centralized-pipelines.asciidoc[]
 
-:edit_url: https://github.com/elastic/logstash/edit/{branch}/x-pack/docs/en/monitoring/configuring-logstash.asciidoc
-include::{xls-repo-dir}/monitoring/configuring-logstash.asciidoc[]
+:edit_url: https://github.com/elastic/logstash/edit/{branch}/docs/static/monitoring/configuring-logstash.asciidoc
+include::static/monitoring/configuring-logstash.asciidoc[]
 
 :edit_url: https://github.com/elastic/logstash/edit/{branch}/docs/static/security/logstash.asciidoc
 include::static/security/logstash.asciidoc[]

docs/static/monitoring.asciidoc

@@ -18,5 +18,5 @@ requiring any extra configuration.
 
 ifdef::include-xpack[]
 :edit_url!:
-include::{xls-repo-dir}/monitoring/index.asciidoc[]
+include::monitoring/index.asciidoc[]
 endif::include-xpack[]

x-pack/docs/en/monitoring/configuring-logstash.asciidoc → docs/static/monitoring/configuring-logstash.asciidoc

@@ -93,7 +93,7 @@ your Logstash nodes should be visible in the Logstash section. When security is
 enabled, to view the monitoring dashboards you must log in to {kib} as a user
 who has the `kibana_user` and `monitoring_user` roles.
 +
-image:monitoring/images/monitoring-ui.png["Monitoring",link="monitoring/images/monitoring-ui.png"]
+image:static/monitoring/images/monitoring-ui.png["Monitoring",link="monitoring/images/monitoring-ui.png"]
 
 [float]
 [[monitoring-upgraded-logstash]]

x-pack/docs/en/monitoring/monitoring-ui.asciidoc → docs/static/monitoring/monitoring-ui.asciidoc

@@ -8,11 +8,11 @@ to gain deep visibility into metrics about your Logstash deployment. In the
 overview dashboard, you can see all events received and sent by Logstash, plus
 info about memory usage and uptime:
 
-image::monitoring/images/overviewstats.png[Logstash monitoring overview dashboard in Kibana]
+image::static/monitoring/images/overviewstats.png[Logstash monitoring overview dashboard in Kibana]
 
 Then you can drill down to see stats about a specific node:
 
-image::monitoring/images/nodestats.png[Logstash monitoring node stats dashboard in Kibana]
+image::static/monitoring/images/nodestats.png[Logstash monitoring node stats dashboard in Kibana]
 
 NOTE: A Logstash node is considered unique based on its persistent UUID, which
 is written to the <<logstash-settings-file,`path.data`>> directory when the node

x-pack/docs/en/monitoring/pipeline-viewer.asciidoc → docs/static/monitoring/pipeline-viewer.asciidoc

@@ -59,7 +59,7 @@ metrics to the monitoring cluster.
 You should see a Logstash section.
 +
 [role="screenshot"]
-image::monitoring/images/monitoring-ui.png[Monitoring UI]
+image::static/monitoring/images/monitoring-ui.png[Monitoring UI]
 
 . Click the *Pipelines* link under Logstash to see all the pipelines that are
 being monitored.
@@ -69,7 +69,7 @@ pipeline, you'll see charts showing the pipeline's throughput and the number
 of nodes on which the pipeline is running during the selected time range.
 +
 [role="screenshot"]
-image::monitoring/images/pipeline-viewer-overview.png[Pipeline Overview]
+image::static/monitoring/images/pipeline-viewer-overview.png[Pipeline Overview]
 +
 // To update the screenshot above, see pipelines/tweets_about_rain.conf
 +
@@ -89,7 +89,7 @@ The diagram shows all the stages feeding data through the pipeline. It also show
 conditional logic.
 +
 [role="screenshot"]
-image::monitoring/images/pipeline-diagram.png[Pipeline Diagram]
+image::static/monitoring/images/pipeline-diagram.png[Pipeline Diagram]
 +
 // To update the screenshot above, see pipelines/tweets_about_rain.conf
 +
@@ -98,7 +98,7 @@ The information displayed on each vertex varies depending on the plugin type.
 Here's an example of an *input* vertex:
 +
 [role="screenshot"]
-image::monitoring/images/pipeline-input-detail.png[Input vertex]
+image::static/monitoring/images/pipeline-input-detail.png[Input vertex]
 +
 The *I* badge indicates that this is an input stage. The vertex shows:
 +
@@ -110,7 +110,7 @@ The *I* badge indicates that this is an input stage. The vertex shows:
 Here's an example of a *filter* vertex.
 
 [role="screenshot"]
-image::monitoring/images/pipeline-filter-detail.png[Filter vertex]
+image::static/monitoring/images/pipeline-filter-detail.png[Filter vertex]
 
 The filter icon indicates that this is a filter stage. The vertex shows:
 
@@ -128,7 +128,7 @@ An *output* vertex shows the same information as a vertex node, but it has an
 *O* badge to indicate that it is an output stage:
 
 [role="screenshot"]
-image::monitoring/images/pipeline-output-detail.png[Output vertex]
+image::static/monitoring/images/pipeline-output-detail.png[Output vertex]
 --
 
 . Hover over a vertex in the diagram, and you'll see only the related nodes that
@@ -139,4 +139,4 @@ are ancestors or descendants of the current vertex.
 . Click on a vertex to see details about it.
 +
 [role="screenshot"]
-image::monitoring/images/pipeline-viewer-detail-drawer.png[Vertex detail]
+image::static/monitoring/images/pipeline-viewer-detail-drawer.png[Vertex detail]