Github user sjcorbett commented on a diff in the pull request:

    https://github.com/apache/incubator-brooklyn/pull/1070#discussion_r45967503
  
    --- Diff: docs/guide/yaml/advanced-example.md ---
    @@ -0,0 +1,177 @@
    +---
    +title: YAML BLueprint Advanced Example
    +layout: website-normal
    +---
    +
    +By this point you should be familiar with the fundamental concepts behind 
both Apache Brooklyn and YAML blueprints. This section of the documentation is 
intended to show a complete, advanced example of a YAML blueprint.
    +
    +The intention is that this example is used to learn the more in-depth 
concepts, but also to serve as a reference point when writing your own 
blueprints. This page will first exaplin what the example is and how to run it, 
then it will spotlight interesting features.
    +
    +
    +### The Example
    +
    +The example itself is a deployment of an ELK stack. ELK stands for 
Elasticsearch, Logstash and Kibana- and this blueprint deploys, installs, runs 
and manages all three. Briefly, the component parts are:
    +
    +* Elasticsearch: A clustered search engine
    +* Logstash: Collects, parses and stores logs. For our application it will 
store logs in Elasticsearch
    +* Kibana: A front end to Elasticsearch
    +
    +For more about the ELK stack, please see the documentation 
[here](https://www.elastic.co/webinars/introduction-elk-stack).
    +
    +In our example, we will be creating the ELK stack, and a Tomcat8 server 
which sends its logs using Logstash to Elasticsearch.
    +
    +#### The Blueprints
    +-----------
    +
    +There are four blueprints that make up this application. Each of them are 
used to add one or more catalog items to Brooklyn. You can find them below:
    +
    +* [Elasticsearch](example_yaml/brooklyn-elasticsearch-catalog.bom)
    +* [Logstash](example_yaml/brooklyn-logstash-catalog.bom)
    +* [Kibana](example_yaml/brooklyn-kibana-catalog.bom)
    +* [ELK](example_yaml/brooklyn-elk-catalog.bom)
    +
    +#### Running the example
    +First, add all four blueprints to the Brooklyn Catalog. This can be done 
by clicking the 'Catalog' tab, clinking the '+' symbol and pasting the YAML. 
Once this is done , click the 'Application' then the '+' button to bring up the 
add application wizard. A new Catalog item will be available called 'ELK 
Stack'. Using the add application wizard, you should be able to deploy an ELK 
stack to a location of your choosing.
    --- End diff --
    
    `the 'Application'` what?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to