[skywalking] branch wu-sheng-patch-1 created (now 904a864)

[wu...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

wusheng pushed a change to branch wu-sheng-patch-1
in repository https://gitbox.apache.org/repos/asf/skywalking.git.


      at 904a864  Update backend-alarm.md

This branch includes the following new commits:

     new 904a864  Update backend-alarm.md

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.

[skywalking] 01/01: Update backend-alarm.md

[wu...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

wusheng pushed a commit to branch wu-sheng-patch-1
in repository https://gitbox.apache.org/repos/asf/skywalking.git

commit 904a86419ce1556c3da38bff47c93c46082024e0
Author: 吴晟 Wu Sheng <wu...@foxmail.com>
AuthorDate: Mon Sep 27 08:18:04 2021 +0800

    Update backend-alarm.md
---
 docs/en/setup/backend/backend-alarm.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/en/setup/backend/backend-alarm.md b/docs/en/setup/backend/backend-alarm.md
index 7e6e34f..f6e7782 100644
--- a/docs/en/setup/backend/backend-alarm.md
+++ b/docs/en/setup/backend/backend-alarm.md
@@ -41,7 +41,7 @@ For multiple-value metrics, such as **percentile**, the threshold is an array. I
 Each value may serve as the threshold for each value of the metrics. Set the value to `-` if you do not wish to trigger the alarm by one or more of the values.  
 For example in **percentile**, `value1` is the threshold of P50, and `-, -, value3, value4, value5` means that there is no threshold for P50 and P75 in the percentile alarm rule.
 - **OP**. The operator. It supports `>`, `>=`, `<`, `<=`, `=`. We welcome contributions of all OPs.
-- **Period**. The frequency for checking the alarm rule. This is a time window that corresponds to the backend deployment env time.
+- **Period**. The size of metrics cache in minutes for checking the alarm conditions. This is a time window that corresponds to the backend deployment env time.
 - **Count**. Within a period window, if the number of times which **value** goes over the threshold (based on OP) reaches `count`, then an alarm will be sent.
 - **Only as condition**. Indicates if the rule can send notifications, or if it simply serves as an condition of the composite rule.
 - **Silence period**. After the alarm is triggered in Time-N, there will be silence during the **TN -> TN + period**.