Issue KN-767 fix: content service config map updated

kubernetes/content/content-service_logback.xml

@@ -23,37 +23,8 @@
 	<appender-ref ref="ASYNCSTDOUT" />
 	</root>
 	
-	
-	<appender name="kafka-appender" class="com.github.danielwegener.logback.kafka.KafkaAppender">
-	<encoder class="ch.qos.logback.classic.encoder.PatternLayoutEncoder">
-	<pattern>%msg</pattern>
-	</encoder>
-	
-	<topic>sunbirdstaging.telemetry.raw</topic>
-	<!-- ensure that every message sent by the executing host is partitioned to the same partition strategy -->
-	<keyingStrategy class="com.github.danielwegener.logback.kafka.keying.NoKeyKeyingStrategy" />
-	<!-- block the logging application thread if the kafka appender cannot keep up with sending the log messages -->
-	<deliveryStrategy class="com.github.danielwegener.logback.kafka.delivery.AsynchronousDeliveryStrategy" />
-	
-	<!-- each <producerConfig> translates to regular kafka-client config (format: key=value) -->
-	<!-- producer configs are documented here: https://kafka.apache.org/documentation.html#newproducerconfigs -->
-	<!-- bootstrap.servers is the only mandatory producerConfig -->
-	<producerConfig>bootstrap.servers=kafka.knowlg-db.svc.cluster.local:9092</producerConfig>
-	<!-- don't wait for a broker to ack the reception of a batch. -->
-	<producerConfig>acks=0</producerConfig>
-	<!-- wait up to 1000ms and collect log messages before sending them as a batch -->
-	<producerConfig>linger.ms=15000</producerConfig>
-	<!-- even if the producer buffer runs full, do not block the application but start to drop messages -->
-	<producerConfig>max.block.ms=0</producerConfig>
-	<!-- define a client-id that you use to identify yourself against the kafka broker -->
-	<producerConfig>client.id=${HOSTNAME}-${CONTEXT_NAME}-logback-relaxed</producerConfig>
-	
-	<!-- there is no fallback <appender-ref>. If this appender cannot deliver, it will drop its messages. -->
-	
-	</appender>
-	
 	<logger name="TelemetryEventLogger" level="INFO">
-	<appender-ref ref="kafka-appender" />
+	<appender-ref ref="STDOUT" />
 	</logger>
 	
 </configuration>