packplusplus
diff --git a/‎docs/gettingstarted.asciidoc
Lines changed: 12 additions & 105 deletions b/‎docs/gettingstarted.asciidoc
Lines changed: 12 additions & 105 deletions
@@ -1,22 +1,23 @@
 [[beats-getting-started]]
 == Getting started
 
+A regular _Beats setup_ consists of:
 
-The _Beats platform_ together with Elasticsearch and Kibana form an _open source 
-application monitoring solution_.
-
- * _Beats shippers_ to collect the data. You should install these on
+ * Beats shippers to collect the data. You should install these on
    your servers so that they capture the data.
- * _Elasticsearch_ for storage and indexing.
- * _Kibana_ for the UI.
+ * Elasticsearch for storage and indexing. <<elasticsearch-installation>>
+ * Optionally Logstash. <<logstash-installation>>
+ * Kibana for the UI. <<kibana-installation>>
+ * Kibana dashboards to customize your widgets. <<load-kibana-dashboards>>
 
-For now, you can just install Elasticsearch and Kibana on a single VM or even
+NOTE:  For now, you can just install Elasticsearch and Kibana on a single VM or even
 on your laptop. The only condition is that this machine is accessible from the
 servers you want to monitor. As you add more shippers and your traffic grows, you
 will want replace the single Elasticsearch instance with a cluster. You will
 probably also want to automate the installation process.  But for now, let's
 just do the fun part.
 
+[[elasticsearch-installation]]
 === Elasticsearch installation
 
 http://www.elasticsearch.org/[Elasticsearch] is a distributed real-time
@@ -84,58 +85,9 @@ curl http://127.0.0.1:9200
 }
 ----------------------------------------------------------------------
 
-=== Beat configuration
-
-Set the IP address and port where the shipper can find the Elasticsearch
-installation:
-
-[source,yaml]
-----------------------------------------------------------------------
-output:
-
-  elasticsearch:
-    # Uncomment out this option if you want to output to Elasticsearch. The
-    # default is false.
-    enabled: true
-
-    # Set the host and port where to find Elasticsearch.
-    host: 192.168.1.42
-    port: 9200
-
-    # Comment this option if you don't want to store the topology in
-    # Elasticsearch. The default is false. 
-    # This option makes sense only for Packetbeat
-    save_topology: true
-----------------------------------------------------------------------
-
-Before starting the shipper, you should also load an
-http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/indices-templates.html[index
-template], which is different for every Beat.
-
-The recommended template file is installed by the Beats Platform packages. Load it with the
-following command:
-
-deb or rpm:
-
-[source,shell]
-----------------------------------------------------------------------
-curl -XPUT 'http://localhost:9200/_template/packetbeat' -d@/etc/packetbeat/packetbeat.template.json
-----------------------------------------------------------------------
-
-mac:
-
-[source,shell]
-----------------------------------------------------------------------
-cd beats-1.0.0-beta3-darwin
-curl -XPUT 'http://localhost:9200/_template/packetbeat' -d@packetbeat.template.json
-----------------------------------------------------------------------
-
-where `localhost:9200` is the IP and port where Elasticsearch is listening on
-Replace `packetbeat` with the beat name that you are running.
 
-
-[[logstash]]
-=== Using Logstash
+[[logstash-installation]]
+=== Insert data to Elasticsearch via Logstash
 
 The simplest architecture for the Beat platform setup consists of the Beats shippers, Elasticsearch and Kibana.
 This is nice and easy to get started with and enough for networks with small traffic. It also uses the
@@ -213,53 +165,7 @@ output {
 }
 ------------------------------------------------------------------------------
 
-
-=== Starting the Beat shipper
-
-
-There is an _init.d_ script for each Beat that can be used for starting and stopping the Beat. 
-In the following examples, packetbeat is used as an example, but it can be any Beat.
-
-deb:
-
-[source,shell]
-----------------------------------------------------------------------
-sudo /etc/init.d/packetbeat start
-----------------------------------------------------------------------
-
-rpm:
-
-[source,shell]
-----------------------------------------------------------------------
-sudo /etc/init.d/packetbeat start
-----------------------------------------------------------------------
-
-mac:
-
-[source,shell]
-----------------------------------------------------------------------
-sudo ./packetbeat -e -c packetbeat.yml -d "publish"
-----------------------------------------------------------------------
-
-Packetbeat is now ready to capture data from your network traffic. You can test
-that it works by creating a simple HTTP request. For example:
-
-[source,shell]
-----------------------------------------------------------------------
-curl http://www.elastic.co/ > /dev/null
-----------------------------------------------------------------------
-
-Now check that the data is present in Elasticsearch with the following command:
-
-[source,shell]
-----------------------------------------------------------------------
-curl -XGET 'http://localhost:9200/packetbeat-*/_search?pretty'
-----------------------------------------------------------------------
-
-Make sure to replace `localhost:9200` with the address of your Elasticsearch
-instance. It should return data about the HTTP transaction you just created.
-
-
+[[kibana-installation]]
 === Kibana installation
 
 https://www.elastic.co/products/kibana[Kibana] is a visualization application
@@ -304,6 +210,7 @@ interface.
 You can learn more about Kibana in the
 http://www.elastic.co/guide/en/kibana/current/index.html[Kibana User Guide].
 
+[[load-kibana-dashboards]]
 === Load Kibana dashboards
 
 Kibana has a large set of visualization types which you can combine to create