You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: expand drop rules, links template syntax, audit log tiers, and invite limits
- f001: Add dedicated drop rules section with full CRUD steps, matching
logic, priority ordering, and comparison with silence rules
- f002: Document channel links template variable syntax (${variable}),
list all available variables, and explain iframe vs new-tab modes
- f003: Add per-tier max searchable time range table for audit logs
(Free 30d, Standard 180d, Professional 366d)
- f004: Add daily invite resend limit (5/day) to member management
- f005: Clarify audit log retention varies by subscription tier
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: en/on-call/channel/create-edit.mdx
+65-5Lines changed: 65 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -87,14 +87,36 @@ After creating a channel, go to the **Configuration** tab on the details page to
87
87
Create alert integrations in **Configuration** → **Integrate Data** → **Dedicated Integrations** to bring monitoring system alerts into this channel.
88
88
89
89
- Each integration type generates an independent Webhook address
90
-
- Configure rules in **Configuration** → **Integrate Data** → **Drop Rules** to filter test data or invalid alerts
90
+
91
+
See [Integrate Data](/en/on-call/channel/integrate-data) for details.
92
+
93
+
### Configure Drop Rules
94
+
95
+
Configure rules in **Configuration** → **Integrate Data** → **Drop Rules** to filter out events that have entered the channel but don't need processing (such as test data or invalid alerts). Dropped events will not generate new alerts or merge into existing alerts.
96
+
97
+
<Steps>
98
+
<Steptitle="Create a Drop Rule">
99
+
Go to **Configuration** → **Integrate Data** → **Drop Rules**, click **Add Drop Rule**.
100
+
</Step>
101
+
<Steptitle="Fill in Rule Information">
102
+
Enter a **Rule Name** (required) and **Description** (optional) for identification and management.
103
+
</Step>
104
+
<Steptitle="Set Filter Conditions">
105
+
Configure filter conditions — supports matching by **Integration Source** and **Severity**.
106
+
</Step>
107
+
<Steptitle="Save the Rule">
108
+
After saving, the rule is enabled by default. You can enable or disable any rule at any time from the drop rules list.
109
+
</Step>
110
+
</Steps>
111
+
112
+
<Note>
113
+
Multiple drop rules are executed sequentially in list order. If any rule matches, the event is dropped. You can drag to adjust the execution priority of rules.
114
+
</Note>
91
115
92
116
<Warning>
93
-
Dropped events will not appear anywhere. If you're not receiving alerts, check the drop rules first.
117
+
Dropped events will not appear anywhere. If you're not receiving alerts, check the drop rules first. Drop rules differ from [silence rules](/en/on-call/channel/noise-reduction) — silence rules only suppress notifications while the incident still exists; drop rules discard events entirely, producing no alert or incident records.
94
118
</Warning>
95
119
96
-
See [Integrate Data](/en/on-call/channel/integrate-data) for details.
97
-
98
120
### Configure Escalation Rules
99
121
100
122
Define incident notification paths in **Configuration** → **Notification & Assignment** → **Escalation Rules**: who to notify, how to notify, and how to escalate on timeout.
@@ -126,7 +148,45 @@ Typical use cases include:
126
148
- Linking to an internal knowledge base or Runbook
127
149
- Opening a related monitoring dashboard
128
150
129
-
Links support two open modes: **Open in New Tab** and **Open in Embedded iframe**.
151
+
#### Template Variable Syntax
152
+
153
+
Use `${variable_name}` in the link URL to reference incident or alert property values. The system automatically replaces variables with actual values when rendering links.
154
+
155
+
**Supported variables:**
156
+
157
+
| Variable | Description |
158
+
| :--- | :--- |
159
+
|`${title}`| Incident/alert title |
160
+
|`${incident_id}`| Incident ID |
161
+
|`${alert_id}`| Alert ID |
162
+
|`${num}`| Incident number |
163
+
|`${description}`| Incident/alert description |
164
+
|`${incident_severity}`| Incident severity |
165
+
|`${alert_severity}`| Alert severity |
166
+
|`${channel_id}`| Channel ID |
167
+
|`${progress}`| Incident processing progress |
168
+
|`${start_time}`| Trigger time |
169
+
|`${end_time}`| Close time |
170
+
|`${labels.KEY}`| Alert label value — replace `KEY` with the label name, e.g., `${labels.service}`|
171
+
|`${fields.KEY}`| Custom field value — replace `KEY` with the field identifier, e.g., `${fields.actions}`|
|**Open in New Tab**| Clicking the link opens the target URL in a new browser tab |
185
+
|**Open in Embedded iframe**| Clicking the link opens an iframe popup on the current page, embedding the target page directly |
186
+
187
+
<Note>
188
+
Each channel can be associated with up to 3 links. Create links through the **Integration Center**, then select the associated channels in the link configuration.
Copy file name to clipboardExpand all lines: en/platform/audit-log.mdx
+10-2Lines changed: 10 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,7 @@ Audit logs provide multiple filtering criteria to help you quickly locate target
32
32
33
33
| Filter | Description |
34
34
| --- | --- |
35
-
|**Time Range**| Select the query time interval; defaults to showing the last 7 days of logs |
35
+
|**Time Range**| Select the query time interval; defaults to showing the last 7 days of logs. The maximum searchable range depends on your subscription plan (see table below)|
36
36
|**User**| Filter by operator, supports searching by member name or email |
37
37
|**Event**| Filter by event type, supports multi-select and keyword search |
38
38
|**Event ID**| Enter an event ID to precisely match a specific operation record |
@@ -41,14 +41,22 @@ Audit logs provide multiple filtering criteria to help you quickly locate target
41
41
You can combine multiple filters. For example, you can specify both a time range and an operator to quickly find all operations by a specific member during a particular period.
42
42
</Tip>
43
43
44
+
**Maximum searchable range by plan:**
45
+
46
+
| Subscription Plan | Maximum Searchable Range |
47
+
| --- | --- |
48
+
| Free | 30 days |
49
+
| Standard | 180 days |
50
+
| Professional | 366 days |
51
+
44
52
## Pagination
45
53
46
54
---
47
55
48
56
Audit logs display 10 records per page. Use the pagination buttons at the bottom of the page to browse more records. The current page number and total pages are shown at the bottom.
49
57
50
58
<Note>
51
-
The audit log retention period depends on your subscription plan. Contact support to upgrade if you need a longer retention period.
59
+
Both the audit log retention period and searchable range depend on your subscription plan — higher tiers retain logs longer. Contact support to upgrade if you need a longer retention period.
0 commit comments