Incorporated Simon's suggestions and deleted unwanted sentences and images

Author: Pallavi-Janardhan

modules/eventing/assets/images/stats_00_counts.png

@@ -1,31 +1,22 @@
 = Statistics
-:description: Eventing Statistics, for each deployed Function, can be fetched from an Eventing node using the Web Console or using the REST API.
+:description: You can fetch Eventing Statistics for each deployed Function from an Eventing node using the Web Console or using the Capella UI.
 :page-edition: Enterprise Edition
 
 [abstract]
 {description}
 
-*Via the Web Console's Eventing page*
+== Via the Capella UI Eventing Tab
 
 As of 7.0.0, Eventing Statistics can be displayed in the Eventing main UI page for each deployed Function by clicking on the Function name to expand the Function controls. 
 These three key metrics or Deployment Statistics are updated every 10 seconds by default and displayed as numeric values:
 
 * *success*	- displays the number of processed Functions and also Eventing timer callbacks.
 * *failure*	- displays the number of failures while processing the Eventing Function code.
-* *timeout*	- displays the number of Functions which have encountered a timeout condition.	
+* *timeout*	- displays the number of Functions which have encountered a timeout condition.
+* *backlog* - displays the number of Functions in the backlog. 
 
-// image::stats_00_counts.png[,100%]
 
-In addition to the per Function numeric statistics above as of 7.0.0 there are the rate charts that can be accessed from any deployed function. 
-These charts are lagged by 30 seconds.
-
-* *success*	- displays the rate of processed Functions and also Eventing timer callbacks.
-* *failure*	- displays the rate of failures while processing the Function Eventing Function code.
-* *timeout*	- displays the rate of Functions which have encountered a timeout condition.
-
-// image::stats_01_counts_and_charts.png[,100%]
-
-In addition, per Function Statistics can be accessed via the Web Console or using the REST API.
+In addition to the numeric statistics, you can also click the Log button (icon:fine-Lines[]) to display the log for any deployed function. 
 
 *Via the Web Console's custom Dashboards*
 
@@ -44,42 +35,3 @@ There are six Eventing measures (three rates + three counts) these Dashboard sta
 * Failed Function Invocations
 * Eventing Timeouts
 
-////
-
-image::stats_02_add_charts.png[,100%]
-
-An example of all the possible dashboard charts is shown below:
-
-image::stats_02_system_charts.png[,100%]
-
-Note, you may click and expand any of the above graphs for any deployed Eventing Function or any Dashboard chart.
-
-////
-
-*Via the REST API*
-
-NOTE: The Functions REST API endpoints on this page are fully supported, as long as the content of the Eventing Function body is not created or modified externally (as the internal format of the body is not yet standardized).
-
-Eventing statistics can be fetched from each eventing node using REST API bound to localhost. 
-The resulting JSON based responses are local to the node, and suitable for further aggregation across nodes of the cluster.
-
-You must have appropriate RBAC privileges to view an Eventing Function's Application log in the UI or via the REST API. 
-The role of either "Full Admin" or "Eventing Full Admin" can access any Eventing Function endpoint. 
-For more information refer to xref:eventing-rbac.adoc[Eventing Role-Based Access Control].
-
-The following REST endpoint could be used to get the full set of Eventing statistics:
-[source,shell]
-----
-curl http://user:pass@localhost:8096/api/v1/stats?type=full
-----
-This will return the full statistics set inclusive of events processing, events remaining, execution, failure, latency, worker PIDs and sequence processed.
-
-NOTE: Omitting the parameter `type=full` will exclude `dcp_event_backlog_per_vb`, `doc_timer_debug_stats`, `latency_stats`, `plasma_stats` and `seqs_processed` from the response.
-
-The above statistics can also be individually obtained through the following REST endpoints:
-[source,shell]
-----
-curl http://user:pass@localhost:8096/getExecutionStats?name=function_name
-curl http://user:pass@localhost:8096/getLatencyStats?name=function_name
-curl http://user:pass@localhost:8096/getFailureStats?name=function_name
-----