Add infrastructure and logs doc (#25407)

docs/index.asciidoc

@@ -44,6 +44,10 @@ include::canvas.asciidoc[]
 
 include::ml/index.asciidoc[]
 
+include::infrastructure/index.asciidoc[]
+
+include::logs/index.asciidoc[]
+
 include::apm/index.asciidoc[]
 
 include::graph/index.asciidoc[]

docs/infrastructure/index.asciidoc

@@ -0,0 +1,26 @@
+[role="xpack"]
+[[xpack-infra]]
+= Infrastructure
+
+[partintro]
+--
+beta[]
+ 
+Use the interactive Infrastructure UI to monitor your infrastructure and
+identify problems in real time. You can explore metrics and logs for common
+servers, containers, and services. 
+
+[role="screenshot"]
+image::infrastructure/images/infra-sysmon.jpg[Infrastructure Overview in Kibana]
+
+
+[float]
+== Add data sources
+Kibana provides step-by-step instructions to help you add your data sources.
+The {infra-guide}[Infrastructure Monitoring Guide] is good source for more detailed
+instructions and information.
+
+--
+
+include::monitor.asciidoc[]
+include::infra-ui.asciidoc[]

docs/infrastructure/infra-ui.asciidoc

@@ -0,0 +1,62 @@
+[role="xpack"]
+[[infra-ui]]
+== Using the Infrastructure UI
+
+Use the Infrastructure UI in {kib} to monitor your infrastructure and identify
+problems in real time. 
+
+You start with an overview of your infrastructure.
+Then you can use the interactive UI to drill down into areas of interest.
+
+[role="screenshot"]
+image::infrastructure/images/infra-sysmon.jpg[Infrastructure Overview in Kibana]
+
+TIP: Right-click an element to jump to related logs or metrics. 
+
+[float]
+[[infra-cat]]
+=== View your infrastructure by hosts or container
+
+Select the high-level view: *Hosts*, *Kubernetes*, or *Docker*.
+When you change views, you can see the same data through the perspective of a
+different category.
+
+[float]
+[[infra-search]]
+=== Use the power of Search
+
+The Search bar is always available. You can use it to perform adhoc or structured searches.
+The Search feature can surface the information you're looking for, even if the
+other options you have selected would normally filter it out.
+
+[float]
+[[infra-metric]]
+=== Start at a high-level by selecting the metric
+
+This filter helps you start focusing on potential problem areas that may need
+further investigation. You'll see metrics that are most relevant for hosts or
+the container you selected.
+
+[float]
+[[infra-group]]
+=== Group components 
+
+The *Group By* selector offers grouping options that are native and specific for
+your physical, virtual, and container-based infrastructure.
+Examples include Availability Zone, Machine Type, Project ID, and Cloud Provider
+for Hosts, and Namespace and Node for Kubernetes.
+
+[float]
+[[infra-date]]
+=== Specify the date range
+
+Use the time selector to focus on a specific timeframe.
+
+[float]
+[[infra-refresh]]
+=== Auto-refresh or pause
+
+Set auto-refresh to keep up-to-date information coming in, or stop
+refreshing to focus on historical data without new distractions.
+
+

docs/infrastructure/monitor.asciidoc

@@ -0,0 +1,35 @@
+[role="xpack"]
+[[monitor-infra]]
+== Monitor your infrastructure
+
+You start with a visual summary of your infrastructure. 
+Then you can drill down into areas of interest.
+
+[float] 
+=== Monitor hosts and containers 
+
+View your infrastructure by hosts or containers. The UI helps you group, filter,
+and target data to help you find what you seek.
+
+[float]
+=== View metrics
+
+View relevant metric information such as CPU usage, memory usage, load, and inbound or
+outbound traffic. 
+
+[float]
+=== View logs
+
+View real-time and historical logs in the same viewer, streaming or pausing as needed. 
+When you stream logs, the most recent event appears at the bottom of console.
+You can easily correlate metrics and logs. Right-click an element in the
+Infrastructure UI, and select *View logs*.
+
+
+
+
+
+
+
+
+

docs/logs/index.asciidoc

@@ -0,0 +1,26 @@
+[role="xpack"]
+[[xpack-logs]]
+= Logs
+
+[partintro]
+--
+
+beta[]
+Use the Logs UI to explore logs for common servers, containers, and services.  
+{kib} provides a compact, console-like display that you can customize.
+
+[role="screenshot"]
+image::logs/images/logs-console.png[Log Console in Kibana]
+
+
+[float]
+== Add data sources
+
+Kibana provides step-by-step instructions to help you add your data sources.
+The {infra-guide}[Infrastructure Monitoring Guide] is good source for more detailed information and
+instructions.
+
+
+--
+
+include::logs-ui.asciidoc[]

docs/logs/logs-ui.asciidoc

@@ -0,0 +1,37 @@
+[role="xpack"]
+[[logs-ui]]
+== Using the Logs UI
+
+Customize the Infrastructure UI to focus on the data you want to see and control how you see it.
+
+[role="screenshot"]
+image::logs/images/logs-console.png[Log Console in Kibana]
+
+[float]
+[[logs-search]]
+=== Use the power of Search
+The Search bar is always available. Use it to perform adhoc and structured searches.
+
+[float]
+[[logs-time]]
+=== Jump to a specific time period
+Use the time selector to focus on a specific timeframe.  
+
+[float]
+[[logs-customize]]
+=== Customize your view
+Use *Customize* to adjust your console view and to set the time scale of the log data.
+
+* *Text size.*  Select `Small`, `Medium`, or `Large`.
+* *Wrap long lines.* Enable or disable line wrap.
+* *Minimap Scale.* Set the scale to 'year', 'month', 'week', 'day', 'hour', or 'minute'. 
+
+[float]
+[[logs-stream]]
+=== Stream or pause logs
+You can stream data for live log tailing, or pause streaming to focus on historical log data. 
+When you are streaming logs, the most recent log appears at the bottom on the console. 
+Historical data offers infinite scrolling. 
+
+
+