From 8711e1fd1949f5528cc569fe84e39cf6a14dd76f Mon Sep 17 00:00:00 2001
From: Ela AWS <51791117+elamaran11@users.noreply.github.com>
Date: Fri, 10 Nov 2023 10:52:17 -0500
Subject: [PATCH] OSS Fargate doc issues (#131)

* Fix Doc Issues

* Fix Doc Issues

* Fix Doc Issues
---
 .../single-new-eks-fargate-opensource-observability.md     | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/docs/patterns/single-new-eks-observability-accelerators/single-new-eks-fargate-opensource-observability.md b/docs/patterns/single-new-eks-observability-accelerators/single-new-eks-fargate-opensource-observability.md
index 6aa88b11..08004375 100644
--- a/docs/patterns/single-new-eks-observability-accelerators/single-new-eks-fargate-opensource-observability.md
+++ b/docs/patterns/single-new-eks-observability-accelerators/single-new-eks-fargate-opensource-observability.md
@@ -1,4 +1,4 @@
-# Single New EKS Cluster Opensource Observability - Fargate
+# Single Cluster Opensource Observability - Fargate
 
 ## Architecture
 
@@ -192,6 +192,11 @@ You should now see a new dashboard named `Java/JMX`, under `Observability Accele
 
 ![java-dashboard](../images/java-jmx-dashboard-fargate-oss.png)
 
+## Viewing Logs
+
+By default, we deploy a FluentBit daemon set in the cluster to collect worker logs for all namespaces. Logs are collected and exported to Amazon CloudWatch Logs, which enables you to centralize the logs from all of your systems, applications,
+and AWS services that you use, in a single, highly scalable service.
+
 ## Teardown
 
 You can teardown the whole CDK stack with the following command: