77To get up and running with infrastructure monitoring, you need:
88
99* An Elasticsearch cluster and Kibana (version 6.5 or later) with a basic
10- license. To learn how to get up and running quickly, see
11- {stack-gs}/get-started-elastic-stack.html[Getting started with the
12- {stack}].
10+ license. To learn how to get started quickly, see
11+ {stack-gs}/get-started-elastic-stack.html[Getting started with the {stack}].
1312+
1413[TIP]
1514==============
@@ -20,7 +19,14 @@ https://www.elastic.co/cloud/elasticsearch-service/signup[Try out the {es}
2019Service for free].
2120==============
2221
23- * {beats} shippers installed on each system you want to monitor
22+ * {beats} shippers (version 6.5 or later) installed on each system you want to
23+ monitor
24+
25+ You might also need to modify UI settings in {kib} to change default behaviors,
26+ such as the index pattern used to query the data, and the timestamp field used
27+ for sorting. For more information, see
28+ {kibana-ref}/infrastructure-ui-settings-kb.html[{infra-ui} UI Settings] and
29+ {kibana-ref}/logs-ui-settings-kb.html[{logs-ui} UI Settings].
2430
2531[float]
2632[[install-beats-for-infra-UI]]
@@ -86,7 +92,7 @@ module]
8692* {filebeat-ref}/add-kubernetes-metadata.html[{filebeat} `add_kubernetes_metadata` processor]
8793
8894[float]
89- ==== More about monitoring containers
95+ ==== More about container monitoring
9096
9197If you're monitoring containers, you can use autodiscover to automatically apply
9298configuration changes in response to changes in your containers. To learn how,
0 commit comments