From 3701b6192e095042532ec68b51abc3d4f041135e Mon Sep 17 00:00:00 2001
From: Mustafa Demirhan <4033879+mdemirhan@users.noreply.github.com>
Date: Wed, 30 May 2018 14:20:10 -0700
Subject: [PATCH] Added information on how to open logs for a config, revision
 and build to telemetry documentation. (#943)

---
 telemetry.md | 28 +++++++++++++++++++++++++++-
 1 file changed, 27 insertions(+), 1 deletion(-)

diff --git a/telemetry.md b/telemetry.md
index 0fedc7ba5..1cec50c75 100644
--- a/telemetry.md
+++ b/telemetry.md
@@ -35,9 +35,35 @@ kubectl proxy
 ```
 Then open Kibana UI at this [link](http://localhost:8001/api/v1/namespaces/monitoring/services/kibana-logging/proxy/app/kibana)
 (*it might take a couple of minutes for the proxy to work*).
-When Kibana is opened the first time, it will ask you to create an index. Accept the default options as is. As logs get ingested,
+When Kibana is opened the first time, it will ask you to create an index. Accept the default options as is. As more logs get ingested,
 new fields will be discovered and to have them indexed, go to Management -> Index Patterns -> Refresh button (on top right) -> Refresh fields.
 
+### Accessing configuration and revision logs
+To access to logs for a configuration, use the following search term in Kibana UI:
+```
+kubernetes.labels.elafros_dev\/configuration: "configuration-example"
+```
+Replace `configuration-example` with your configuration's name.
+
+To access logs for a revision, use the following search term in Kibana UI:
+```
+kubernetes.labels.elafros_dev\/revision: "configuration-example-00001"
+```
+Replace `configuration-example-00001` with your revision's name.
+
+### Accessing build logs
+To access to logs for a build, use the following search term in Kibana UI:
+```
+kubernetes.labels.build\-name: "test-build"
+```
+Replace `test-build` with your build's name. A build's name is specified in its YAML file as follows:
+```yaml
+apiVersion: build.dev/v1alpha1
+kind: Build
+metadata:
+  name: test-build
+```
+
 ## Accessing metrics
 
 Run: