Observability Overview updates (#3678)

Co-authored-by: Trey Spiller <1831878+treysp@users.noreply.github.com>
Co-authored-by: Sung Won Chung <sungwonchung3@gmail.com>

Author: 3 people

docs/cloud/features/observability/overview.md

@@ -4,20 +4,18 @@ Fixing problems with data pipelines is challenging because there are so many pot
 
 For transformation pipelines, those range from upstream source timeouts to SQL query errors to Python library conflicts (and more!).
 
-A useful observation tool should make it easy to answer the following questions:
+![Data Ops Observability](./overview/data-ops-light.png)
 
-- Did a problem occur?
-- When did it occur?
-- What type of problem is it?
-- Where is the problem coming from?
-- What is causing the problem?
+Tobiko Cloud makes it easy to detect and respond to changes in your pipelines:
 
-Tobiko Cloud supports answering these questions in four ways:
-
-1. Automatically notifying users if a problem occurs
-2. Capturing, storing, and displaying historical information that reveals when a problem occurred
-3. Enabling easy navigation from aggregated to granular information about pipeline components to identify the problem source
-4. Centralizing error information from multiple sources to debug the problem
+- Did a problem occur? 
+    - **Alerts notify you immediately.**
+- When did the problem occur? 
+    - **Historical pipeline information reveals the moment.**
+-  Where is the problem coming from? 
+    - **Easy navigation through pipeline components lets you pinpoint the source.**
+-  What is causing the problem? 
+    - **Centralized logs and errors have all the details.**
 
 ## How it works
 
@@ -33,15 +31,19 @@ This information allows you to:
 - Creation of custom visualizations and metrics
 - Troubleshoot problems and optimize inefficient operations
 
-Observability features are seamlessly integrated into Tobiko Cloud, making it simple to monitor and understand your project's behavior.
+Observability features are seamlessly integrated into Tobiko Cloud, making it simple to monitor and understand your project's behavior. For example, on the Tobiko Cloud Homepage, there is run history, plan executions, and freshness displayed for the production environment: 
+
+![Observability on the Homepage](./overview/observability_section_home.png)
 
 Instead of digging through complex logs or piecing together information from multiple sources, you can quickly access the relevant information from any part of your project.
 
+<!---
 Learn more about Tobiko Cloud Observability features on these pages:
 
-- [`prod` environment](prod_environment.md) health and recent activity
+- [`prod` environment](prod_environment.md) health and recent activity 
 - [Development environment](development_environment.md) differences from `prod` and recent activity
 - [Plan](plan.md) status and detailed model execution data
 - [Run](run.md) status and detailed model execution data
 - [Model](model.md) status and version history
-- [Dashboards](measures_dashboards.md) and custom visualizations of observability data
+- [Dashboards](measures_dashboards.md) and custom visualizations of observability data
+-->