refine diagrams (#600)

Author: chenziliang

docs/cluster.md

@@ -16,7 +16,7 @@ Underlying both the metadata and data layers is **Timeplus NativeLog**, the dist
 
 The following diagram shows a more advanced cluster design with metadata, data, and compute nodes running on separate tiers.
 
-![cluster-deployment](/img/cluster-deployment.png)
+![cluster-deployment](/img/cluster-deployment.svg)
 
 ## Distributed Ingest
 

docs/k8s-helm.md

@@ -5,9 +5,6 @@ import TabItem from '@theme/TabItem';
 
 You can deploy Timeplus Enterprise on a Kubernetes cluster with [Helm](https://helm.sh/). The source code of the chart can be find in our [github repo](https://github.com/timeplus-io/helm-charts/tree/main/charts/timeplus-enterprise).
 
-For visual learning, you can watch the following video:
-<iframe width="560" height="315" src="https://www.youtube.com/embed/kFyzYx1JI_8?si=WVszQMuFyW6Xcixm" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
-
 ## Prerequisites
 
 - Ensure you have Helm 3.12 + installed in your environment. For details about how to install Helm, see the [Helm documentation](https://helm.sh/docs/intro/install/)

docs/materialized-perf-tuning.md

@@ -2,7 +2,7 @@
 
 A **Materialized View** consists of four main components. Performance tuning can involve one or more of these components.  
 
-![MatView](/img/mat-view.png)
+![MatView](/img/mat-view-perf.svg)
 
 ## Tune Sources
 

docs/materialized-view-checkpoint.md

@@ -6,7 +6,7 @@ In general, the **checkpoint coordinator** periodically sends checkpoint markers
 
 The following diagram illustrates this process:
 
-![MaterializedViewCheckpoint](/img/materialized-view-checkpoint.png)
+![MaterializedViewCheckpoint](/img/mat-view-checkpoint.png)
 
 Each checkpoint round is assigned a new checkpoint **epoch**. Once a new checkpoint epoch is committed, older epochs can be garbage collected automatically.
 
@@ -44,7 +44,7 @@ In this mode (applies to both **local file system checkpoints** and **RocksDB-ba
 3. Peer replicas consume these checkpoint records from the log and reconstruct them into checkpoint files for the current epoch.
 4. After replication completes, all Materialized View replicas hold identical checkpoint states.
 
-![NativeLogCkptReplication](/img/materialized-view-nativelog-ckpt.png)
+![NativeLogCkptReplication](/img/mat-view-nativelog-ckpt.png)
 
 By default, **NativeLog-based checkpoint replication** is used in cluster environments.
 
@@ -78,7 +78,7 @@ There are two variants:
 1. The checkpoint coordinator serializes query states to the local file system in a new epoch.
 2. It asynchronously uploads the state files for that epoch to shared storage.
 
-![SharedStorageCkpt](/img/materialized-view-shared-storage-ckpt.png)
+![SharedStorageCkpt](/img/mat-view-shared-storage-ckpt.png)
 
 When using shared storage exclusively, Timeplus adopts a different high availability model for Materialized Views, governed by a centralized scheduler.
 
@@ -121,7 +121,7 @@ This hybrid approach combines NativeLog with shared storage.
 3. It commits the object URIs / paths metadata records to NativeLog.
 4. Peer replicas consume these path metadata records, fetch the checkpoint files from shared storage, and reconstruct the checkpoint locally.
 
-![NativeLogComboReplication](/img/materialized-view-hybrid-ckpt.png)
+![NativeLogComboReplication](/img/mat-view-hybrid-ckpt.png)
 
 **Example**:
 ```sql

docs/materialized-view-high-availability.md

@@ -10,7 +10,7 @@ The Raft-based HA model is the default option. When you create a Materialized Vi
 
 Internally, this model leverages a **NativeLog checkpoint shard**, which is replicated using Raft for fault tolerance.
 
-![RaftBasedHA](/img/materialized-view-raft-ha.png)
+![RaftBasedHA](/img/mat-view-raft-ha.png)
 
 ### Initial Leader Election
 
@@ -39,7 +39,7 @@ SETTINGS checkpoint_settings='replication_type=shared;shared_disk=...'
 
 We call this a **Scheduled Materialized View**, since it is governed by the scheduler.
 
-![SchedulerBasedHA](/img/materialized-view-scheduler-ha.png)
+![SchedulerBasedHA](/img/mat-view-scheduler-ha.png)
 
 ### Initial Placement
 

docs/materialized-view-lifecycle.md

@@ -20,7 +20,7 @@ Materialized Views can exist in the following states. Some are **transient** (sh
 
 The state transitions are illustrated in the diagram below:  
 
-![MaterializedViewStates](/img/materialized-view-states-transition.png)
+![MaterializedViewStates](/img/mat-view-states-transition.png)
 
 ## System Commands
 

docs/materialized-view-monitoring.md

@@ -3,6 +3,18 @@
 Timeplus provides detailed metrics and states to monitor Materialized Views.  
 The **Timeplus Console** offers visualizations for these metrics and states, but you can also query them directly.
 
+## Timeplus Console
+
+Here are screenshots from Timeplus Materialized View monitoring in the Timeplus Console.
+
+**High Level Information**
+
+![HighLevelMatViewList](/img/mat-view-monitor-1.png)
+
+**Detail Metrics**
+
+![DetailMatViewMon](/img/mat-view-monitor-2.png)
+
 ## Metrics
 
 The `system.stream_metric_log` stream records performance metrics such as **events per second (eps)** and **megabytes per second (mbps)** for Materialized Views, streams, external streams, and external tables.

docs/materialized-view.md

@@ -23,7 +23,7 @@ A **Materialized View** consists of 4 main components (illustrated in the diagra
    - Persists intermediate query state (e.g., for windowed aggregations or joins).
    - Ensures fault tolerance by allowing recovery and continuation from the last checkpoint after a failure.
 
-![MatView](/img/mat-view.png)
+![MatView](/img/mat-view.svg)
 
 When a Materialized View checkpoints its query state, it ensures durability and fault tolerance. If the process fails mid-execution, it can **restart from the last checkpoint** without reprocessing the entire stream from beginning.
 
@@ -39,7 +39,7 @@ By combining other Timeplus features / components such as:
 
 you can build **complex, end-to-end data processing pipelines** with Materialized Views.
 
-![Pipeline](/img/pipelines.png)
+![Pipeline](/img/mat-view-pipelines.png)
 
 ## Create Materialized View