From cae0716eb834c4c932d55fef0820a26d27776838 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Istv=C3=A1n=20Zolt=C3=A1n=20Szab=C3=B3?= Date: Mon, 1 Jul 2019 10:01:59 +0200 Subject: [PATCH] [DOCS] Removes the term: tutorial from the Getting started with the Elastic Stack page (#392) This PR removes the term "tutorial" from the getting started page for better differentiation between the two content types. Resolves conflict. Related issue: #391 --- .../getting-started/get-started-stack.asciidoc | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/en/getting-started/get-started-stack.asciidoc b/docs/en/getting-started/get-started-stack.asciidoc index 6294fbd17..45385a1a3 100644 --- a/docs/en/getting-started/get-started-stack.asciidoc +++ b/docs/en/getting-started/get-started-stack.asciidoc @@ -1,9 +1,9 @@ [[get-started-elastic-stack]] == Getting started with the {stack} -Looking for an {stack} ("ELK" tutorial) that shows how to set up the {stack}? In -this tutorial, you learn how to get up and running quickly. First you install -the core open source products: +Looking for an {stack} ("ELK") guide that shows how to set up the {stack} and +get up and running quickly? You're on the right place! First you install the +core products: * <> * <> @@ -310,7 +310,7 @@ The {beats} are open source data shippers that you install as agents on your servers to send operational data to {es}. {beats} can send data directly to {es} or via {ls}, where you can further process and enhance the data. -Each Beat is a separately installable product. In this tutorial, you learn how +Each Beat is a separately installable product. In this guide, you learn how to install and run {metricbeat} with the `system` module enabled to collect system metrics. @@ -645,7 +645,7 @@ To learn more about installing, configuring, and running {ls}, read the ==== Configure {ls} to listen for {beats} input {ls} provides {logstash-ref}/input-plugins.html[input plugins] for reading from -a variety of inputs. In this tutorial, you create a {ls} pipeline configuration +a variety of inputs. In this guide, you create a {ls} pipeline configuration that listens for {beats} input and sends the received events to the {es} output. To configure {ls}: @@ -785,9 +785,9 @@ For example: Rather than sending the whole command-line argument to {es}, you might want to send just the command's path. One way to do that is by using a Grok filter. -Learning Grok is beyond the scope of this tutorial, but if you want to learn -more, see the {logstash-ref}/plugins-filters-grok.html[Grok filter plugin] -documentation. +Learning Grok is beyond the scope of this getting started guide, but if you want +to learn more, see the +{logstash-ref}/plugins-filters-grok.html[Grok filter plugin] documentation. To extract the path, add the following Grok filter between the input and output sections in the {ls} config file that you created earlier: