Github user ahgittin commented on a diff in the pull request:
https://github.com/apache/incubator-brooklyn/pull/440#discussion_r22718833
--- Diff: docs/guide/start/managing.md ---
@@ -0,0 +1,40 @@
+---
+title: Monitoring and Managing Applications
+title_in_menu: Monitoring and Managing Applications
+layout: guide-normal
+menu_parent: index.md
+---
+
+Click on the application name, or open the Applications tab.
+
+We can explore the management hierarchy of the application, which will
show us the entities it is composed of.
+
+ * My Web Cluster (A `BasicApplication`)
+ * My DB (A `MySqlNode`)
+ * My Web (A `ControlledDynamicWebAppCluster`)
+ * Cluster of JBoss7 Servers (A `DynamicWebAppCluster`)
+ * NginxController (An `NginxController`)
+
+
+
+Clicking on the 'My Web' entity will show the Summary tab. Here we can see
if the cluster is ready to serve and, when ready, grab the web address for the
front of the loadbalancer.
+
+
+
+
+The Activity tab allows us to drill down into what activities each entity
is currently doing or has recently done. It is possible to drill down to all
child tasks, and view the commands issued, and any errors or warnings that
occured.
+
+Drill into the 'My DB' start operation. Working down through 'Start
(processes)', then 'launch', we can discover the ssh command used including the
stdin, stdout and stderr.
+
+[](images/my-db-activities-large.png)
+
+
+## Stopping the Application
+
+To stop an application, select the application in the tree view (the
top/root entity), click on the Effectors tab, and invoke the 'Stop' effector.
This will cleanly shutdown all components in the application and return any
cloud machines that were being used.
+
+[](images/my-web-cluster-stop-confirm-large.png)
+
+### Next
+
+Brooklyn's real power is in using Policies to automatically *manage*
applications.
--- End diff --
make this link to the next page (policies)
---
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.
---
