diff --git a/content/en/docs/cluster-administration/alerting/_index.md b/content/en/docs/cluster-administration/alerting/_index.md
new file mode 100644
index 000000000..fd315a5f3
--- /dev/null
+++ b/content/en/docs/cluster-administration/alerting/_index.md
@@ -0,0 +1,7 @@
+---
+linkTitle: "Alerting"
+weight: 4160
+
+_build:
+    render: false
+---
diff --git a/content/en/docs/cluster-administration/alerting/alerting-message.md b/content/en/docs/cluster-administration/alerting/alerting-message.md
new file mode 100644
index 000000000..e737387aa
--- /dev/null
+++ b/content/en/docs/cluster-administration/alerting/alerting-message.md
@@ -0,0 +1,52 @@
+---
+title: "Alerting Message - node level"
+keywords: 'KubeSphere, Kubernetes, Node, Alerting, Message, Notification'
+description: 'Alerting Message - node level'
+
+linkTitle: "Alerting Message - node level"
+weight: 4170
+---
+
+Alert Message records the detailed information of alert triggered by alert rule. In it, you can view alert details, monitoring targets, alert policies, recent notifications, comments and etc.
+
+## Prerequisites
+
+You have created a node-level alert policy and receive alert notifications of it. If no, please refer to [Alert Policy - node level](../alerting-policy/) to create one.
+
+## Hands-on Lab
+
+### Task 1: View Alert Message
+
+1. Log in the console with one account granted the role `platform-admin`. 
+2. Click **Platform** at the top left corner and select **Cluster Management**. 
+
+![alerting_message_node_level_guide](/images/docs/alerting/alerting_message_node_level_guide.png)
+
+3. Select one from the cluster list and enter it (If you do not enable multi-cluster, you will directly enter the only one). 
+4. Navigate to **Alerting Message** under **Monitoring & Alerting**, and you can see alert messages in the list. In the example of [Alert Policy - node level](../alerting-policy/), you set one node as the monitoring target, and its memory utilization rage is higher than the threshold of `50%`, so you can see an alert message of it.
+
+![alerting_message_node_level_list](/images/docs/alerting/alerting_message_node_level_list.png)
+
+5. Click the alert message to enter the detail page. In **Alerting Detail**, you can see the graph of memory utilization rate of the node over time, which has been continuously higher than the threshold of `50%` set in the alert rule, so the alert was triggered.
+
+![alerting_message_node_level_detail](/images/docs/alerting/alerting_message_node_level_detail.png)
+
+### Task 2: View Alert Policy
+
+Switch to **Alert Policy** to view the alert policy corresponding to this alert message, and you can see the triggering rule of it set in the example of [Alert Policy - node level](../alerting-policy/).
+
+![alerting_message_node_level_policy](/images/docs/alerting/alerting_message_node_level_policy.png)
+
+### Task 3: View Recent Notification
+
+Switch to **Recent Notification**, it can be seen that the notifiers have received 3 notifications, because notification rule has sending period of `Alert once every 5 miniutes` and retransmission of `Resend up to 3 times`.
+
+![alerting_message_node_level_notification](/images/docs/alerting/alerting_message_node_level_notification.png)
+
+Log in your email to see alert notification mails sent by the KubeSphere mail server. You have received a total of 3 emails. 
+
+### Task 4: Add Comment
+
+Click **Comment** to add comment to current alert message. For example, memory utilization rate of the node is higher than the threshold set by the alert rule, you can add a comment in the dialog: `The node needs to be tainted and new pod is not allowed to schedule`.
+
+![alerting_message_node_level_comment](/images/docs/alerting/alerting_message_node_level_comment.png)
diff --git a/content/en/docs/cluster-administration/alerting/alerting-policy.md b/content/en/docs/cluster-administration/alerting/alerting-policy.md
new file mode 100644
index 000000000..f0752afe3
--- /dev/null
+++ b/content/en/docs/cluster-administration/alerting/alerting-policy.md
@@ -0,0 +1,92 @@
+---
+title: "Alerting Policy - node level"
+keywords: 'KubeSphere, Kubernetes, Node, Alerting, Policy, Notification'
+description: 'Alerting Policy - node level'
+
+linkTitle: "Alerting Policy - node level"
+weight: 4160
+---
+
+## Objective
+
+KubeSphere provides alert policies for nodes and workloads. This guide demonstrates how you will create alert policy for nodes in the cluster and configure mail notifications. See [Alerting Policy - workload level](../../../project-user-guide/alerting/alerting-policy/) to learn how to configure alert policies for workloads.
+
+## Prerequisites
+
+- [KubeSphere Alerting and Notification](../../../pluggable-components/alerting-notification/) needs to be enabled.
+- [Mail Server](../../../cluster-administration/cluster-settings/mail-server/) needs to be configured.
+
+## Hands-on Lab
+
+### Task 1: Create a Alert Policy
+
+1. Log in the console with one account granted the role `platform-admin`. 
+2. Click **Platform** at the top left corner and select **Cluster Management**. 
+
+![alerting_policy_node_level_guide](/images/docs/alerting/alerting_policy_node_level_guide.png)
+
+3. Select one from the cluster list and enter it (If you do not enable multi-cluster, you will directly enter the only one). 
+4. Navigate to **Alerting Policies** under **Monitoring & Alerting**, and click **Create**.
+
+![alerting_policy_node_level_create](/images/docs/alerting/alerting_policy_node_level_create.png)
+
+### Task 2: Fill in basic information
+
+In the dialog that appears, fill in the basic information as follows. Click **Next** after finishing that.
+- **Name**: a concise and clear name to browse and search, such as `alert-demo`.
+- **Alias**: to help you distinguish alert policies better. Chinese is supported.
+- **Description**: a brief introduction to the alert policy.
+
+![alerting_policy_node_level_basic_info](/images/docs/alerting/alerting_policy_node_level_basic_info.png)
+
+### Task 3: Select Monitoring Targets
+
+Select several nodes in the node list as the monitoring targets. Here a node is selected for the convenience of demonstration. Then click **Next**.
+![alerting_policy_node_level_monitoring_target](/images/docs/alerting/alerting_policy_node_level_monitoring_target.png)
+
+{{< notice note >}}
+
+The node list supports sorting nodes by the following three ways: `Sort By CPU`, `Sort By Memory`,  `Sort By Pod Utilization`.
+
+{{</ notice >}}
+
+### Task 4: Add Alerting Rules
+
+Click **Add Rule** to begin to create an alerting rule. The rule defines parameters such as metric type, check period, consecutive times, metric threshold and alert level to provide rich configurations. The check period (the second field under **Rule**) means the time interval between 2 consecutive checks of the metric. For example, 2 minutes/period means the metric is checked every two minutes. The consecutive times (the third field under **Rule**) means the number of consecutive times that the metric meets the threshold when checked. An alert is only triggered when the actual time is equal to or is greater than the number of consecutive times set in the alert policy. 
+ 
+In this example, set those parameters to `memory utilization rate`, `1 minute/period`, `2 consecutive times`, `>` and `50%`, and `Major Alert` in turn. It means KubeSphere checks the memory utilization rate every minute, and a major alert is triggered if it is larger than 50% for 2 consecutive times.  
+
+Click **√** to save when finish that, and then click **Next**.
+
+![alerting_policy_node_level_alerting_rule](/images/docs/alerting/alerting_policy_node_level_alerting_rule.png)
+
+{{< notice note >}}
+
+- You can create node-level alert policies for the following metrics:
+    - cpu: `cpu utilization rate`, `cpu load average 1 minute`, `cpu load average 5 minutes`, `cpu load average 15 minutes`
+    - memory: `memory utilization rate`, `memory available`
+    - disk: `inode utilization rate`, `disk space available`, `local disk space utilization rate`, `disk write throughput`, `disk read throughput`, `disk read iops`, `disk write iops`
+    - network: `network data transmitting rate`, `network data receiving rate`
+    - pod: `pod abnormal ratio`, `pod utilization rate`
+
+{{</ notice >}}
+
+### Task 5: Set Notification Rule
+
+1. **Effective Notification Time Range** is used to set sending time of notification emails, such as `09:00 ~ 19:00`. Notification channel currently only supports email. You can add email addresses of members to be notified to **Notification List**.
+1. **Customize Repetition Rules** can set sending period and retransmission of notification emails. So if alerts have not been resolved, alerts will be sent repeatedly after a certain period of time. Different repetition rules can also be set for different levels of alerts. Since the alert level set in the previous step is `Major Alert`, So set **Major Alert** to `Alert once every 5 miniutes`(sending period) and `Resend up to 3 times`(retransmission). Refer to the followings to set notification rules:
+1. Click **Create**, and you can see that the alert policy is successfully created.
+
+![alerting_policy_node_level_notification_rule](/images/docs/alerting/alerting_policy_node_level_notification_rule.png)
+
+{{< notice note >}}
+
+*waiting time for alerting* **=** *check period* **x** *consecutive times*. For example, if check period is 1 minute/period, and the number of consecutive times is 2 times, you need to wait for 2 minutes.
+
+{{</ notice >}}
+
+### Task 6: View Alert Policy
+
+After `alert-demo` alert policy is successfully created, you can enter the detailed information page of it to view status of it, and alert rules, monitoring targets, notification rule, alert history, etc.
+
+You can go to **More** → **Change Status** on the left corner to enable or disable this alert policy.
\ No newline at end of file
diff --git a/content/en/docs/cluster-administration/cluster-settings/_index.md b/content/en/docs/cluster-administration/cluster-settings/_index.md
new file mode 100644
index 000000000..89e5f2112
--- /dev/null
+++ b/content/en/docs/cluster-administration/cluster-settings/_index.md
@@ -0,0 +1,7 @@
+---
+linkTitle: "Cluster Settings"
+weight: 4180
+
+_build:
+    render: false
+---
diff --git a/content/en/docs/cluster-administration/cluster-settings/mail-server.md b/content/en/docs/cluster-administration/cluster-settings/mail-server.md
new file mode 100644
index 000000000..db2a1d4b4
--- /dev/null
+++ b/content/en/docs/cluster-administration/cluster-settings/mail-server.md
@@ -0,0 +1,33 @@
+---
+title: "Mail Server"
+keywords: 'KubeSphere, Kubernetes, Notification, Mail Server'
+description: 'Mail Server'
+
+linkTitle: "Mail Server"
+weight: 4190
+---
+
+## Objective
+
+This guide demonstrates email notification settings (customized settings supported) for alert policies. You can specify user email addresses to receive alert messages.
+
+## Prerequisites
+
+- [KubeSphere Alerting and Notification](../../../pluggable-components/alerting-notification/) needs to be enabled
+
+## Hands-on Lab
+
+1. Log in the web console with one account granted the role  `platform-admin`.
+2. After you log in the console, click **Platform** at the top left corner and select **Cluster Management**.
+
+![mail_server_guide](/images/docs/alerting/mail_server_guide.png)
+
+3. If you enable multi-cluster, you have to select the cluster where you plan to configure the mail server from the cluster list, otherwise you will automatically enter the only cluster.
+4. Select **Mail Server** under **Cluster Settings**. In the page, provide your mail server configuration and SMTP authentication information as follows:
+    - **SMTP Server Address**: Fill in the SMTP server address that can provide mail service. The port is usually 25.
+    - **Use SSL Secure Connection**: SSL can be used to encrypt mails, thereby improving the security of information transmitted by mail. Usually you have to configure the certificate for the mail server.
+    - SMTP authentication information: Fill in **SMTP User**, **SMTP Password**, **Sender Email Address** and etc.
+
+![mail_server_config](/images/docs/alerting/mail_server_config.png)
+
+After completing the above settings, click **Save**. You can send a test email to verify the success of the server configuration.
\ No newline at end of file
diff --git a/content/en/docs/project-user-guide/alerting/_index.md b/content/en/docs/project-user-guide/alerting/_index.md
new file mode 100644
index 000000000..01205b6a6
--- /dev/null
+++ b/content/en/docs/project-user-guide/alerting/_index.md
@@ -0,0 +1,7 @@
+---
+linkTitle: "Alerting"
+weight: 2200
+
+_build:
+    render: false
+---
diff --git a/content/en/docs/project-user-guide/alerting/alerting-message.md b/content/en/docs/project-user-guide/alerting/alerting-message.md
new file mode 100644
index 000000000..faa12f936
--- /dev/null
+++ b/content/en/docs/project-user-guide/alerting/alerting-message.md
@@ -0,0 +1,46 @@
+---
+title: "Alerting Message - workload level"
+keywords: 'KubeSphere, Kubernetes, Workload, Alerting, Message, Notification'
+description: 'Alerting Message - workload level'
+
+linkTitle: "Alerting Message - workload level"
+weight: 2220
+---
+
+Alert Message records the detailed information of alert triggered by alert rule. In it, you can view alert details, monitoring targets, alert policies, recent notifications, comments and etc.
+
+## Prerequisites
+
+You have created a workload-level alert policy and receive alert notifications of it. If no, please refer to [Alert Policy - workload level](../alerting-policy/) to create one.
+
+## Hands-on Lab
+
+### Task 1: View Alert Message
+
+1. Log in the console and go to your project. Navigate to **Alerting Message** under **Monitoring & Alerting**, and you can see alert messages in the list. In the example of [Alert Policy - workload level](../alerting-policy/) you set two monitoring targets `reviews-v1` and `details-v1`, and both of their memory usages are higher than the threshold, so you can see two alert messages corresponding to them.
+
+![alerting_message_workload_level_list](/images/docs/alerting/alerting_message_workload_level_list.png)
+
+2. Select one of the alert messages to enter the detail page. In **Alerting Detail**, you can see the graph of the memory usage of the monitored workload over time, which has been continuously higher than the threshold of 20 MiB set in the alert rule, so the alert was triggered.
+
+![alerting_message_workload_level_detail](/images/docs/alerting/alerting_message_workload_level_detail.png)
+
+### Task 2: View Alert Policy
+
+Switch to **Alert Policy** to view the alert policy corresponding to this alert message, and you can see the triggering rule of it set in the example of [Alert Policy - workload level](../alerting-policy/).
+
+![alerting_message_workload_level_policy](/images/docs/alerting/alerting_message_workload_level_policy.png)
+
+### Task 3: View Recent Notification
+
+Switch to **Recent Notification**, it can be seen that the notifiers have received 3 notifications, because period of notification rule is set to `5 minutes/period` and consecutive count is `3 consecutive times`.
+
+![alerting_message_workload_level_notification](/images/docs/alerting/alerting_message_workload_level_notification.png)
+
+Log in your email to see alert notification mails sent by the KubeSphere mail server. You have received a total of 6 emails. This is because memory usages of two monitored workloads (deployments) have exceeded the threshold of `20 MiB` continuously, and notification rule has period of `5 minutes/period` and consecutive count of `3 consecutive times`.
+
+### Task 4: Add Comment
+
+Click **Comment** to add comment to current alert message. For example, if the memory usage of workload is higher than the threshold set by the alert rule, you can add a comment in the dialog: `Default maximum memory usage quota needs to be increased for this workload`.
+
+![alerting_message_workload_level_comment](/images/docs/alerting/alerting_message_workload_level_comment.png)
diff --git a/content/en/docs/project-user-guide/alerting/alerting-policy.md b/content/en/docs/project-user-guide/alerting/alerting-policy.md
new file mode 100644
index 000000000..53ffb1b8e
--- /dev/null
+++ b/content/en/docs/project-user-guide/alerting/alerting-policy.md
@@ -0,0 +1,77 @@
+---
+title: "Alerting Policy - workload level"
+keywords: 'KubeSphere, Kubernetes, Workload, Alerting, Policy, Notification'
+description: 'Alerting Policy - workload level'
+
+linkTitle: "Alerting Policy - workload level"
+weight: 2210
+---
+
+## Objective
+
+KubeSphere provides alert policies for nodes and workloads. This guide demonstrates how you as a project member will create alert policy for workloads in the project and configure mail notifications. See [Alerting Policy - node level](../../../cluster-administration/alerting/alerting-policy/) to learn how to configure alert policies for nodes.
+
+## Prerequisites
+
+- [KubeSphere Alerting and Notification](../../../pluggable-components/alerting-notification/) needs to be enabled by `platform-admin`.
+- [Mail Server](../../../cluster-administration/cluster-settings/mail-server/) needs to be configured by `platform-admin`.
+- You have been invited to one project with a `operator` role.
+- You have workloads in this project. If no, you can go to **Applications** under **Application Workloads**, click **Deploy Sample Application** to deploy an application quickly.
+
+## Hands-on Lab
+
+### Task 1: Create an Alert Policy
+
+Log in the console and go to your project. Navigate to **Alerting Policies** under **Monitoring & Alerting**, then click **Create**.
+
+![alerting_policy_workload_level_create](/images/docs/alerting/alerting_policy_workload_level_create.png)
+
+### Task 2: Fill in basic information
+
+In the dialog that appears, fill in the basic information as follows. Click **Next** after finishing that.
+- **Name**: a concise and clear name to browse and search, such as `alert-demo`.
+- **Alias**: to help you distinguish alert policies better. Chinese is supported.
+- **Description**: a brief introduction to the alert policy.
+
+![alerting_policy_workload_level_basic_info](/images/docs/alerting/alerting_policy_workload_level_basic_info.png)
+
+### Task 3: Select Monitoring Targets
+
+Supports three workloads as monitoring targets: deployment, statefulset and daemonset. 
+Here select **Deployments** and select `reviews-v1` and `details-v1` as monitoring targets. Then click **Next**.
+
+![alerting_policy_workload_level_monitoring_target](/images/docs/alerting/alerting_policy_workload_level_monitoring_target.png)
+
+### Task 4: Add Alerting Rules
+
+Click **Add Rule** to begin to create an alerting rule. The rule defines parameters such as metric type, check period, consecutive times, metric threshold and alert level to provide rich configurations. The check period (the second field under **Rule**) means the time interval between 2 consecutive checks of the metric. For example, 2 minutes/period means the metric is checked every two minutes. The consecutive times (the third field under **Rule**) means the number of consecutive times that the metric meets the threshold when checked. An alert is only triggered when the actual time is equal to or is greater than the number of consecutive times set in the alert policy.  
+
+In this example, set those parameters to `memory usage`, `1 minute/period`, `2 consecutive times`, `>` and `20` MiB for threshold and `Major Alert` for alert level. It means KubeSphere checks the memory usage every minute, and a major alert is triggered if it is larger than 20 MiB for 2 consecutive times.  
+
+Click **√** to save when finish that, and then click **Next**.
+
+![alerting_policy_workload_level_alerting_rule](/images/docs/alerting/alerting_policy_workload_level_alerting_rule.png)
+
+{{< notice note >}}
+
+- You can create workload-level alert policies for the following metrics:
+    - cpu: `cpu usage`
+    - memory: `memory usage (including cache)`, `memory usage`
+    - network: `network data transmitting rate`, `network data receiving rate`
+    - workload metric: `unavailable deployment replicas ratio`
+
+{{</ notice >}}
+
+### Task 5: Set Notification Rule
+
+1. **Effective Notification Time Range** is used to set sending time of notification emails, such as `09:00 ~ 19:00`. Notification channel currently only supports email. You can add email addresses of members to be notified to **Notification List**.
+1. **Customize Repetition Rules** can set sending period and retransmission of notification emails. So if alerts have not been resolved, alerts will be sent repeatedly after a certain period of time. Different repetition rules can also be set for different levels of alerts. Since the alert level set in the previous step is `Major Alert`, So set **Major Alert** to `Alert once every 5 miniutes`(sending period) and `Resend up to 3 times`(retransmission). Refer to the followings to set notification rules:
+1. Click **Create**, and you can see that the alert policy is successfully created.
+
+![alerting_policy_workload_level_notification_rule](/images/docs/alerting/alerting_policy_workload_level_notification_rule.png)
+
+### Task 6: View Alert Policy
+
+After `alert-demo` alert policy is successfully created, you can enter the detailed information page of it to view status of it, and alert rules, monitoring targets, notification rule, alert history, etc.
+
+You can go to **More** → **Change Status** on the left corner to enable or disable this alert policy.
\ No newline at end of file
diff --git a/content/en/docs/toolbox/events-query.md b/content/en/docs/toolbox/events-query.md
new file mode 100644
index 000000000..b6455ba9c
--- /dev/null
+++ b/content/en/docs/toolbox/events-query.md
@@ -0,0 +1,48 @@
+---
+title: "Event Query"
+keywords: 'KubeSphere, Kubernetes, Event'
+description: 'Event Query'
+
+linkTitle: "Event Query"
+weight: 4190
+---
+
+## Objective
+
+Kubernetes event provides insight into what is happening inside a cluster, based on which KubeSphere adds longer historical query and aggregation capabilities, and also supports event query for tenant isolation. This guide demonstrates how you will do multi-level, fine-grained event queries to track the state of your components.
+
+## Prerequisites
+
+- [KubeSphere Events](../../../pluggable-components/events/) needs to be enabled.
+
+## Hands-on Lab
+
+1. Log in the console with one account. Mouse over the **Toolbox** in the lower right corner and then select **Event Search**.
+
+![events_query_guide](/images/docs/events/events_query_guide.png)
+
+2. As shown in the pop-up window, you can see the amount trend of events that the logged in account has permission to view. 
+
+![events_query_home](/images/docs/events/events_query_home.png)
+
+{{< notice note >}}
+- The events console supports the following query conditions:
+    - Workspace
+    - Project
+    - Resource Type
+    - Resource Name
+    - Reason
+    - Message
+    - Category
+    - Time Range
+- It also supports customizing the range of time to query. KubeSphere stores the events for last seven days by default.
+
+{{</ notice >}}
+
+3. Here is an example to query the events in project `test` whose message contains `container` within last 1 hour as shown in the following screenshot. It returns 84 rows of results with the corresponding time, project, message.
+
+![events_query_list](/images/docs/events/events_query_list.png)
+
+4. Click any one of the results from the list, you can see raw information of it. It is convenient for developers to debug and analyze.
+
+![events_query_detail](/images/docs/events/events_query_detail.png)
\ No newline at end of file
diff --git a/static/images/docs/alerting/alerting_message_node_level_comment.png b/static/images/docs/alerting/alerting_message_node_level_comment.png
new file mode 100644
index 000000000..683f08682
Binary files /dev/null and b/static/images/docs/alerting/alerting_message_node_level_comment.png differ
diff --git a/static/images/docs/alerting/alerting_message_node_level_detail.png b/static/images/docs/alerting/alerting_message_node_level_detail.png
new file mode 100644
index 000000000..8841e8c28
Binary files /dev/null and b/static/images/docs/alerting/alerting_message_node_level_detail.png differ
diff --git a/static/images/docs/alerting/alerting_message_node_level_guide.png b/static/images/docs/alerting/alerting_message_node_level_guide.png
new file mode 100644
index 000000000..ee80648e1
Binary files /dev/null and b/static/images/docs/alerting/alerting_message_node_level_guide.png differ
diff --git a/static/images/docs/alerting/alerting_message_node_level_list.png b/static/images/docs/alerting/alerting_message_node_level_list.png
new file mode 100644
index 000000000..e7c780033
Binary files /dev/null and b/static/images/docs/alerting/alerting_message_node_level_list.png differ
diff --git a/static/images/docs/alerting/alerting_message_node_level_notification.png b/static/images/docs/alerting/alerting_message_node_level_notification.png
new file mode 100644
index 000000000..44010312e
Binary files /dev/null and b/static/images/docs/alerting/alerting_message_node_level_notification.png differ
diff --git a/static/images/docs/alerting/alerting_message_node_level_policy.png b/static/images/docs/alerting/alerting_message_node_level_policy.png
new file mode 100644
index 000000000..f5002418d
Binary files /dev/null and b/static/images/docs/alerting/alerting_message_node_level_policy.png differ
diff --git a/static/images/docs/alerting/alerting_message_workload_level_comment.png b/static/images/docs/alerting/alerting_message_workload_level_comment.png
new file mode 100644
index 000000000..90787da1d
Binary files /dev/null and b/static/images/docs/alerting/alerting_message_workload_level_comment.png differ
diff --git a/static/images/docs/alerting/alerting_message_workload_level_detail.png b/static/images/docs/alerting/alerting_message_workload_level_detail.png
new file mode 100644
index 000000000..79b4ebc46
Binary files /dev/null and b/static/images/docs/alerting/alerting_message_workload_level_detail.png differ
diff --git a/static/images/docs/alerting/alerting_message_workload_level_list.png b/static/images/docs/alerting/alerting_message_workload_level_list.png
new file mode 100644
index 000000000..16918e1a0
Binary files /dev/null and b/static/images/docs/alerting/alerting_message_workload_level_list.png differ
diff --git a/static/images/docs/alerting/alerting_message_workload_level_notification.png b/static/images/docs/alerting/alerting_message_workload_level_notification.png
new file mode 100644
index 000000000..aa8a67e04
Binary files /dev/null and b/static/images/docs/alerting/alerting_message_workload_level_notification.png differ
diff --git a/static/images/docs/alerting/alerting_message_workload_level_policy.png b/static/images/docs/alerting/alerting_message_workload_level_policy.png
new file mode 100644
index 000000000..ecbba244a
Binary files /dev/null and b/static/images/docs/alerting/alerting_message_workload_level_policy.png differ
diff --git a/static/images/docs/alerting/alerting_policy_node_level_alerting_rule.png b/static/images/docs/alerting/alerting_policy_node_level_alerting_rule.png
new file mode 100644
index 000000000..3a99908fa
Binary files /dev/null and b/static/images/docs/alerting/alerting_policy_node_level_alerting_rule.png differ
diff --git a/static/images/docs/alerting/alerting_policy_node_level_basic_info.png b/static/images/docs/alerting/alerting_policy_node_level_basic_info.png
new file mode 100644
index 000000000..00dbd7a9c
Binary files /dev/null and b/static/images/docs/alerting/alerting_policy_node_level_basic_info.png differ
diff --git a/static/images/docs/alerting/alerting_policy_node_level_create.png b/static/images/docs/alerting/alerting_policy_node_level_create.png
new file mode 100644
index 000000000..71ab8fb0a
Binary files /dev/null and b/static/images/docs/alerting/alerting_policy_node_level_create.png differ
diff --git a/static/images/docs/alerting/alerting_policy_node_level_guide.png b/static/images/docs/alerting/alerting_policy_node_level_guide.png
new file mode 100644
index 000000000..ee80648e1
Binary files /dev/null and b/static/images/docs/alerting/alerting_policy_node_level_guide.png differ
diff --git a/static/images/docs/alerting/alerting_policy_node_level_monitoring_target.png b/static/images/docs/alerting/alerting_policy_node_level_monitoring_target.png
new file mode 100644
index 000000000..615e3812a
Binary files /dev/null and b/static/images/docs/alerting/alerting_policy_node_level_monitoring_target.png differ
diff --git a/static/images/docs/alerting/alerting_policy_node_level_notification_rule.png b/static/images/docs/alerting/alerting_policy_node_level_notification_rule.png
new file mode 100644
index 000000000..5723856b4
Binary files /dev/null and b/static/images/docs/alerting/alerting_policy_node_level_notification_rule.png differ
diff --git a/static/images/docs/alerting/alerting_policy_workload_level_alerting_rule.png b/static/images/docs/alerting/alerting_policy_workload_level_alerting_rule.png
new file mode 100644
index 000000000..6849364ab
Binary files /dev/null and b/static/images/docs/alerting/alerting_policy_workload_level_alerting_rule.png differ
diff --git a/static/images/docs/alerting/alerting_policy_workload_level_basic_info.png b/static/images/docs/alerting/alerting_policy_workload_level_basic_info.png
new file mode 100644
index 000000000..c8a6ac2a1
Binary files /dev/null and b/static/images/docs/alerting/alerting_policy_workload_level_basic_info.png differ
diff --git a/static/images/docs/alerting/alerting_policy_workload_level_create.png b/static/images/docs/alerting/alerting_policy_workload_level_create.png
new file mode 100644
index 000000000..aa6744229
Binary files /dev/null and b/static/images/docs/alerting/alerting_policy_workload_level_create.png differ
diff --git a/static/images/docs/alerting/alerting_policy_workload_level_monitoring_target.png b/static/images/docs/alerting/alerting_policy_workload_level_monitoring_target.png
new file mode 100644
index 000000000..5c722b0ed
Binary files /dev/null and b/static/images/docs/alerting/alerting_policy_workload_level_monitoring_target.png differ
diff --git a/static/images/docs/alerting/alerting_policy_workload_level_notification_rule.png b/static/images/docs/alerting/alerting_policy_workload_level_notification_rule.png
new file mode 100644
index 000000000..75d823da0
Binary files /dev/null and b/static/images/docs/alerting/alerting_policy_workload_level_notification_rule.png differ
diff --git a/static/images/docs/alerting/mail_server_config.png b/static/images/docs/alerting/mail_server_config.png
new file mode 100644
index 000000000..87cdcf3c9
Binary files /dev/null and b/static/images/docs/alerting/mail_server_config.png differ
diff --git a/static/images/docs/alerting/mail_server_guide.png b/static/images/docs/alerting/mail_server_guide.png
new file mode 100644
index 000000000..ee80648e1
Binary files /dev/null and b/static/images/docs/alerting/mail_server_guide.png differ
diff --git a/static/images/docs/events/events_query_detail.png b/static/images/docs/events/events_query_detail.png
new file mode 100644
index 000000000..530c19caa
Binary files /dev/null and b/static/images/docs/events/events_query_detail.png differ
diff --git a/static/images/docs/events/events_query_guide.png b/static/images/docs/events/events_query_guide.png
new file mode 100644
index 000000000..fbd8de754
Binary files /dev/null and b/static/images/docs/events/events_query_guide.png differ
diff --git a/static/images/docs/events/events_query_home.png b/static/images/docs/events/events_query_home.png
new file mode 100644
index 000000000..26b6cbb0d
Binary files /dev/null and b/static/images/docs/events/events_query_home.png differ
diff --git a/static/images/docs/events/events_query_list.png b/static/images/docs/events/events_query_list.png
new file mode 100644
index 000000000..1b63b9d19
Binary files /dev/null and b/static/images/docs/events/events_query_list.png differ