[DOC-12684]: Update Explore the Server Configuration page (#3720)

Author: RayOffiah

modules/getting-started/assets/images/eventLogging.png

@@ -1,7 +1,7 @@
 = Explore the Server Configuration
 :page-pagination:
 :imagesdir: ../assets/images
-:description: Once you have Couchbase Server running, you can log into the Couchbase Server Web Console, and start to examine the different features that it provides.
+:description: Once you have Couchbase Server running, you can log into the Couchbase Server Web Console and start to examine the different features that it provides.
 
 [abstract]
 {description}
@@ -23,29 +23,31 @@ The Docker image that you installed comes pre-configured with a default username
 
 Type these credentials into the appropriate fields and click btn:[Sign In].
 
+[#examine-the-cluster-dashboard]
 == Examine the Cluster Dashboard
 
 Every time you log into the Web Console, you are brought to the [.ui]*Cluster Dashboard*:
 
 [#cluster_overview]
 image::ClusterOverview.png["The Cluster Dashboard",720]
 
-The [.ui]*Cluster Dashboard* provides a graphical summary of the current state of your Couchbase cluster.
+The [.ui]*Cluster Dashboard* provides a graphical summary of the Couchbase cluster's current state.
 The term _cluster_ might seem unexpected at this point, since you are only running a single instance of Couchbase Server; but nevertheless, it counts as a cluster of one.
 
-All of the values that are displayed on this screen were automatically configured by the sandbox container image during installation.
-In production, you will specify these values individually according to your needs.
+All the values that are displayed on this screen were automatically configured by the sandbox container image during installation.
+In production, you will specify these values individually, according to your needs.
 
 Notice the information panel at the very bottom.
 This shows that you have a single active bucket on the system — _bucket_ meaning a logical group of data-items.
-Taking a closer look at this bucket will give you some idea of how Couchbase stores data, and prepare you to make your first data-queries.
+Taking a closer look at this bucket will give you some idea
+of how Couchbase stores data and prepares you to make your first data-queries.
 
 == Examine Your Bucket and Its Documents
 
 Click menu:Buckets[] in the left-hand navigation bar to bring up the [.ui]*Buckets* screen.
 
 The [.ui]*Buckets* screen shows that you have a single active bucket on the system (_bucket_ meaning a logical group of data-items).
-Taking a closer look at this bucket will give you some idea of how Couchbase stores data, and prepare you to make your first data-queries:
+Taking a closer look at this bucket will give you some idea of how Couchbase stores data and prepare you to make your first data-queries:
 
 [#travel_sample_bucket_screen_initial]
 image::travelSampleBucketScreenInitial.png["The Buckets screen",720]
@@ -59,15 +61,16 @@ Click [.ui]*Scopes and Collections* to inspect the scopes and collections contai
 image::travelSampleScopesScreen.png["The travel-sample Scopes screen",720]
 
 The [.ui]*Scopes and Collections* screen shows, in a succession of page-views, the scopes that are contained within the bucket.
-To see the collections that are contained within a given scope, left-click on the row for the scope -- for example, for the `inventory` scope:
+To see the collections that are contained within a given scope,
+left-click on the row for the scope, e.g., for the `inventory` scope:
 
 [#travel_sample_collections_screen]
 image::travelSampleCollectionsScreen.png["The travel-sample Scopes screen, showing the inventory collections",720]
 
 In Couchbase Server 7.0 and later, all documents must be contained in a scope and collection.
 If you import a dataset that was created in earlier versions of Couchbase Server, the documents are automatically saved within a `_default` scope and a `_default` collection.
 For your initial work with the system, this will be fine.
-But as you continue, and you create more documents, your will benefit from using scopes and collections to organize those documents in the best way: this will make data-access intuitive and clear.
+But as you continue, and you create more documents, you will benefit from using scopes and collections to organize those documents in the best way: this will make data-access intuitive and clear.
 
 See the xref:getting-started:/look-at-the-results.adoc#other-destinations[Other Destinations] section, below, for a link to information on creating and managing your own scopes and collections.
 
@@ -84,7 +87,7 @@ The following document retrieval controls are provided:
 The documents within the selected collection are those that will be retrieved.
 (For information on scopes and collections, see xref:learn:data/scopes-and-collections.adoc[Scopes and Collections]).
 * *Limit*: The maximum number of rows (documents) to retrieve and display at once.
-* *Offset*: The number of documents in the entire set of the current collection that should be skipped, before display begins.
+* *Offset*: The number of documents in the entire set of the current collection that should be skipped before displaying begins.
 Notice that when you click [.ui]*Next Batch >*, the [.ui]*Offset* increases by the same value that is specified in [.ui]*Limit*.
 * *Document ID*: Accepts the ID of a specific document.
 Leave this field blank to retrieve documents based on *Limit* and *Offset*.
@@ -103,14 +106,14 @@ image::editDocumentDialog.png["The Edit Document dialog",480]
 +
 The document consists of a series of _key-value_ pairs (or, as they are sometimes expressed, _name-value_ pairs).
 You can make modifications to key-values directly in this editor.
-As will be demonstrated later, Couchbase Server allows you to search for keys, and return the corresponding values, by means of a _query_.
+As will be demonstrated later, Couchbase Server allows you to search for keys and return the corresponding values by using a _query_.
 For example, here, if you searched on the name `country`, you would return the value `United States`; if on the name `icao`, the value `MLA`.
 +
 If you make changes in the [.ui]*Edit Document* dialog, click [.ui]*Save* to save your changes.
 If you want to create a new document based on an existing document, you can click the *Make a copy of this document* button (described next).
 If you want to create an entirely new document, you can click the btn:[ADD DOCUMENT] button in the upper-right.
 +
-Note that Couchbase Web Console supports the editing of documents that are up to 10 MB in size (although documents on Couchbase Server can be up to 20 MB in size).
+Note that Couchbase Web Console supports the editing of documents that are up to 10 MB in size, (although documents on Couchbase Server can be up to 20 MB in size).
 
 * *Make a copy of this document*: Click this button to bring up the [.ui]*Save As* dialog, which allows you to create a new document based on the existing one:
 +
@@ -127,6 +130,48 @@ Click it to save your changes to the document.
 
 To view successive sets of documents, use the [.ui]*Next Batch >* and [.ui]*< Prev Batch* buttons.
 
+[#examining-the-cluster-logs]
+== Examining the Cluster's Logs
+
+The Couchbase Server maintains a constant, configurable log of alerts and operations,
+a subset of which can be examined from the web console.
+
+Start by selecting menu:Logs[] from the left-hand navigation menu.
+
+image::eventLogging.png[]
+
+You will be presented with a screen containing a series of events logged by the cluster.
+
+You can filter the log entries by entering a string in the [.ui]*filter logs ...* field.
+
+You can also opt to have logging data written to a file or a bucket on a Couchbase node
+by selecting the menu:Collect Information[] option from the top menu:
+
+image::collectLogInformationOptions.png[]
+
+The [.ui]*Collection Information* screen will be displayed, giving you a number of options for collecting logs.
+As well as specifying the nodes logged, you can also specify a location for writing the logging data.
+
+Once the options have been set, click on btn:[Start Collecting] to start recording logs to your specified location.
+
+TIP: If you are having a problem with your cluster setup, it may  be useful to provide Couchbase Support with a log of the server activity.
+
+[#examining-the-cluster-metrics]
+== Examining the Cluster's Metrics
+
+As well as examining the state of the cluster from the web console, (see the section on xref:examine-the-cluster-dashboard[Examining the cluster dashboard]),
+you can monitor more specific elements of the cluster operation, such as the indexes in real-time:
+
+
+. Select [.ui]*All Services* from the menu:Choose Dashboard[] dropdown menu.
+. The page will expand to include all the services available on the node. 
+Click on [.ui]*Index* and you will be presented with a series of graphs depicting real-time metrics for the indexes running on the node.
++
+image::showDashboardIndex.png["Index from UI dashboard", 720]
++
+TIP: The graphs will allow you to see if loads across multiple nodes differ significantly.
+
+
 [#other-destinations]
 == Other Destinations