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
Copy file name to clipboardExpand all lines: en/on-call/channel/create-edit.mdx
+67-5Lines changed: 67 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -87,13 +87,37 @@ 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
+
Click **Add Drop Rule**.
100
+
</Step>
101
+
<Steptitle="Fill in Rule Information">
102
+
Enter a **Rule Name** (required) and **Description** (optional).
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.
94
-
</Warning>
117
+
Dropped events will not appear anywhere. If you are not receiving alerts, check drop rules first.
95
118
96
-
See [Integrate Data](/en/on-call/channel/integrate-data) for details.
119
+
Drop rules differ from [silence rules](/en/on-call/channel/noise-reduction) and [inhibit rules](/en/on-call/channel/noise-reduction): silence and inhibit rules still match and process at the alert event level (alerts are created), but matched alerts will not group into or trigger any incident; drop rules discard events immediately upon ingestion, producing no alert or incident records at all.
120
+
</Warning>
97
121
98
122
### Configure Escalation Rules
99
123
@@ -126,7 +150,45 @@ Typical use cases include:
126
150
- Linking to an internal knowledge base or Runbook
127
151
- Opening a related monitoring dashboard
128
152
129
-
Links support two open modes: **Open in New Tab** and **Open in Embedded iframe**.
153
+
#### Template Variable Syntax
154
+
155
+
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.
156
+
157
+
**Supported variables:**
158
+
159
+
| Variable | Description |
160
+
| :--- | :--- |
161
+
|`${title}`| Incident/alert title |
162
+
|`${incident_id}`| Incident ID |
163
+
|`${alert_id}`| Alert ID |
164
+
|`${num}`| Incident number |
165
+
|`${description}`| Incident/alert description |
166
+
|`${incident_severity}`| Incident severity |
167
+
|`${alert_severity}`| Alert severity |
168
+
|`${channel_id}`| Channel ID |
169
+
|`${progress}`| Incident processing progress |
170
+
|`${start_time}`| Trigger time |
171
+
|`${end_time}`| Close time |
172
+
|`${labels.KEY}`| Alert label value — replace `KEY` with the label name, e.g., `${labels.service}`|
173
+
|`${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 |
187
+
|**Open in Embedded iframe**| Clicking the link opens an iframe popup on the current page, embedding the target page directly |
188
+
189
+
<Note>
190
+
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
+3-2Lines changed: 3 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, up to a maximum of 30 days|
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,15 @@ 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
+
44
45
## Pagination
45
46
46
47
---
47
48
48
49
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
50
50
51
<Note>
51
-
The audit log retention period depends on your subscription plan. Contact support to upgrade if you need a longer retention period.
52
+
Audit logs are retained for up to 30 days. Logs older than 30 days are automatically purged.
0 commit comments