Merge pull request #14445 from mburke5678/BZ-1699182

improvement in efk-logging-eventrouter.html

Author: mburke5678

logging/config/efk-logging-elasticsearch.adoc

@@ -55,5 +55,3 @@ modules/efk-logging-elasticsearch-persistent-storage-local.adoc[leveloffset=+2]
 
 // == Additional Resources
 
-//For information on installing Elasticsearch, see xref:../logging/efk-logging-deploy.adoc[Deploying cluster logging].
-

logging/efk-logging-eventrouter.adoc

@@ -5,8 +5,9 @@ include::modules/common-attributes.adoc[]
 
 toc::[]
 
-The Event Router is a pod that forwards {product-title} events to Cluster Logging.
+The Event Router communicates with the {product-title} and prints {product-title} events to log of the pod where the event occurs. 
 
+If Cluster Logging is deployed, you can view the {product-title} events in Kibana. 
 
 // The following include statements pull in the module files that comprise
 // the assembly. Include any combination of concept, procedure, or reference
@@ -15,3 +16,4 @@ The Event Router is a pod that forwards {product-title} events to Cluster Loggin
 
 include::modules/efk-logging-eventrouter-deploy.adoc[leveloffset=+1]
 
+

modules/efk-logging-eventrouter-deploy.adoc

@@ -9,11 +9,9 @@ Use the following steps to deploy Event Router into your cluster.
 
 The following Template object creates the Service Account, ClusterRole, and ClusterRoleBinding required for the Event Router.
 
-.Prerequisite
+.Prerequisites
 
-* Cluster logging and Elasticsearch must be installed.
-
-* You need proper permissions to make updates within the `openshift-*` namespace.
+You need proper permissions to create service accounts and update cluster role bindings.  For example, you can run the following template with a user that has the *cluster-admin* role.
 
 .Procedure
 
@@ -127,6 +125,9 @@ parameters:
 <6> Specify the memory limit for the Event Router pods. Defaults to '128Mi'.
 <7> Specify the minimum amount of CPU to allocate to the Event Router. Defaults to '100m'.
 <8> Specify the namespace where eventrouter is deployed. Defaults to `openshift-logging`. The value must be the same as specified for the ServiceAccount and ClusterRoleBinding.
+The project indicates where in Kibana you can locate events:
+* If the event router pod is deployed in a default project, such as `+kube-*+`  and `+openshift-*+`, you can find the events under the *.operation* index.
+* If the event router pod is deployed in other projects, you can find the event under the index using the project namespace. 
 
 . Use the following command to process and apply the template:
 +