Skip to content

Commit

Permalink
[DOCS] Removes the term: tutorial from the Getting started with the E…
Browse files Browse the repository at this point in the history
…lastic 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
  • Loading branch information
szabosteve committed Jul 1, 2019
1 parent 9b6b736 commit 26718b9
Showing 1 changed file with 8 additions and 8 deletions.
16 changes: 8 additions & 8 deletions docs/en/getting-started/get-started-stack.asciidoc
Original file line number Diff line number Diff line change
@@ -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:

* <<install-elasticsearch,{es}>>
* <<install-kibana,{kib}>>
Expand Down Expand Up @@ -311,7 +311,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.

Expand Down Expand Up @@ -644,7 +644,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}:
Expand Down Expand Up @@ -784,9 +784,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:
Expand Down

0 comments on commit 26718b9

Please sign in to comment.