Draft:BDS/Current/BDSPEGuide/Logging - Revision history

WikiSysop: Redirected page to Draft:BDS/Current/BDSPEGuide/Observability#Logging

2022-03-30T13:18:01Z

Redirected page to Draft:BDS/Current/BDSPEGuide/Observability#Logging

Tony.gilchrist@genesys.com at 17:30, June 25, 2021

2021-06-25T17:30:00Z

Tony.gilchrist@genesys.com at 17:29, June 25, 2021

2021-06-25T17:29:40Z

Tony.gilchrist@genesys.com at 17:25, June 25, 2021

2021-06-25T17:25:19Z

Tony.gilchrist@genesys.com at 14:58, June 18, 2021

2021-06-18T14:58:00Z

Tony.gilchrist@genesys.com at 14:57, June 18, 2021

2021-06-18T14:57:12Z

Tony.gilchrist@genesys.com at 14:55, June 18, 2021

2021-06-18T14:55:46Z

Tony.gilchrist@genesys.com at 12:33, June 17, 2021

2021-06-17T12:33:37Z

Tony.gilchrist@genesys.com at 16:25, June 10, 2021

2021-06-10T16:25:20Z

Tony.gilchrist@genesys.com at 19:32, June 2, 2021

2021-06-02T19:32:12Z

← Older revision		Revision as of 13:18, March 30, 2022
Line 1:		Line 1:
−	~~{{Article~~	+	#REDIRECT [[Draft:BDS/Current/BDSPEGuide/Observability#Logging]]
−	~~\|Standalone=No~~
−	~~\|DisplayName=Logging~~
−	~~\|Context=Learn how to store logs for Billing Data Service (BDS).~~
−	~~\|ComingSoon=No~~
−	~~\|Section={{Section~~
−	~~\|alignment=Vertical~~
−	~~\|structuredtext=BDS writes all logs to the standard output.~~
−
−	~~===Viewing logs===~~
−
−	#~~Execute the following command to get the pod name~~:
−	~~#:<source lang="bash">kubectl -n bds get po<~~/~~source>~~
−	~~#:<source lang="bash">NAME READY STATUS RESTARTS AGE~~
−
−	~~bds-t2023-2023-1624633200-w8nh5 0~~/~~1 Completed 0 34m~~
−	</~~source>~~
−	#~~:Where the NAME string is composed of the following elements: bds-t<tenant id>-<tenant id>-<job start linux time>-<random value>~~
−	~~#Execute the following command to check the logs:~~
−	~~#:<source lang="bash">kubectl logs bds-pod-<name></source>~~
−	~~#:Where <name> is the pod name.~~
−	~~#:For example:~~
−	~~#:<source lang="bash">kubectl logs bds-pod-wn8bx</source>~~
−
−	~~===Setting the log level===~~
−	~~Optionally, you can set the log level using the BDS_LOG_LEVEL environment variable. Acceptable values are:~~
−	~~<source lang="bash">CRITICAL, 50, ERROR, 40, WARNING, 30, INFO, 20, DEBUG, 10,NOTSET, 0.</source>~~
−	~~If you do not set a value, BDS reads the default value from '''gvars.py'''. If '''gvars.py''' contains no value, BDS uses the default value (DEBUG).~~
−	~~\|Status=No~~
−	}}
−	~~\|PEPageType=7a5823f3-05b5-412b-b580-e73e34079c41~~
−	}}

@@ Line 9: / Line 9: @@
 ===Viewing logs===
 #Execute the following command to get the pod name:
 #:<source lang="bash">kubectl -n bds get po</source>
@@ Line 16: / Line 17: @@
 </source>
 #:Where the NAME string is composed of the following elements: bds-t<tenant id>-<tenant id>-<job start linux time>-<random value>
-#Execute the following kubectl command to check the logs:
+#Execute the following command to check the logs:
 #:<source lang="bash">kubectl logs bds-pod-<name></source>
 #:Where &lt;name&gt; is the pod name.

@@ Line 9: / Line 9: @@
 ===Viewing logs===
-Execute the following command to get the pod name:
+#Execute the following command to get the pod name:
+#:<source lang="bash">kubectl -n bds get po</source>
-devops@developer:~$ kubectl -n bds get po
+#:<source lang="bash">NAME                             READY   STATUS      RESTARTS   AGE
 bds-t2023-2023-1624633200-w8nh5  0/1     Completed  0          34m
+</source>
-bds-t<tenant id>-<tenant id>-<job start linux time>-<random value>
+#:Where the NAME string is composed of the following elements: bds-t<tenant id>-<tenant id>-<job start linux time>-<random value>
+#Execute the following kubectl command to check the logs:
-Execute the following kubectl command to check the logs:
+#:<source lang="bash">kubectl logs bds-pod-<name></source>
-<source lang="bash">kubectl logs bds-pod-wn8bx</source>
+#:Where &lt;name&gt; is the pod name.
 ===Setting the log level===

@@ Line 8: / Line 8: @@
 |structuredtext=BDS writes all logs to the standard output.
-=== Viewing logs ===
+===Viewing logs===
 Execute the following kubectl command to check the logs:
 <source lang="bash">kubectl logs bds-pod-wn8bx</source>

@@ Line 6: / Line 6: @@
 |Section={{Section
 |alignment=Vertical
-|structuredtext=BDS writes all logs to the standard output. Execute the following kubectl command to check the logs:
+|structuredtext=BDS writes all logs to the standard output.
 <source lang="bash">kubectl logs bds-pod-wn8bx</source>

@@ Line 7: / Line 7: @@
 |alignment=Vertical
 |structuredtext=BDS writes all logs to the standard output. Execute the following kubectl command to check the logs:
-{{{!}} class="wikitable" resolved
+<source lang="bash">kubectl logs bds-pod-wn8bx</source>
-====Setting the log level====
+===Setting the log level===
 Optionally, you can set the log level using the BDS_LOG_LEVEL environment variable. Acceptable values are:
- CRITICAL, 50, ERROR, 40, WARNING, 30, INFO, 20, DEBUG, 10,NOTSET, 0.
+<source lang="bash">CRITICAL, 50, ERROR, 40, WARNING, 30, INFO, 20, DEBUG, 10,NOTSET, 0.</source>
 If you do not set a value, BDS reads the default value from '''gvars.py'''. If '''gvars.py''' contains no value, BDS uses the default value (DEBUG).
 |Status=No

@@ Line 10: / Line 10: @@
 {{!}} class="confluenceTd"{{!}}<code class="java plain">kubectl logs bds-pod-wn8bx</code>
 {{!}}}
-Log level could be set by BDS_LOG_LEVEL environment variable. Acceptable values are:
   CRITICAL, 50, ERROR, 40, WARNING, 30, INFO, 20, DEBUG, 10,NOTSET, 0.
-If none were given, default value will be read from gvars.py. If none provided by gvars, default value is DEBUG.
+If you do not set a value, BDS reads the default value from '''gvars.py'''. If '''gvars.py''' contains no value, BDS uses the default value (DEBUG).
 |Status=No
 }}
 |PEPageType=7a5823f3-05b5-412b-b580-e73e34079c41
 }}

@@ Line 2: / Line 2: @@
 |Standalone=No
 |DisplayName=Logging
-|Context=Learn how to store logs for Billing Data Server (BDS).
+|Context=Learn how to store logs for Billing Data Service (BDS).
 |ComingSoon=No
 |Section={{Section
 |alignment=Vertical
 |structuredtext=BDS writes all logs to the standard output.  Use kubectl to check them:
-{{{!}} class="wikitable" resolved=""
+{{{!}} class="wikitable" resolved
-{{!}} class="confluenceTd" {{!}}<code class="java plain">kubectl logs bds-pod-wn8bx</code>
+{{!}} class="confluenceTd"{{!}}<code class="java plain">kubectl logs bds-pod-wn8bx</code>
 {{!}}}
 Log level could be set by BDS_LOG_LEVEL environment variable. Acceptable values are: