flashduty-knowledge-base 1.2.7 → 1.2.8

package/dist/en.d.ts

@@ -1,3 +1,4 @@
+/** ⬆️⬆️⬆️⬆️ Other ⬆️⬆️⬆️⬆️ */
 declare const docs: {
     CustomAlert: string;
     Email: string;
@@ -59,5 +60,6 @@ declare const docs: {
     ElastAlert2: string;
     DingtalkAlert: string;
     FeishuAlert: string;
+    Link: string;
 };
 export default docs;

package/dist/esm/en.js

@@ -3267,7 +3267,7 @@ Choose this option when you need to route alerts to different channels based on
 
 </div>
 
-`,_=`---
+`,L=`---
 title: "Dynatrace Alert Events"
 description: "Sync Dynatrace alert events to Flashduty via webhook to achieve automated alert noise reduction."
 date: "2024-08-20T10:00:00+08:00"
@@ -3374,7 +3374,7 @@ Choose this option when you need to route alerts to different channels based on
 |CUSTOM_ALERT|Info|info|
 
 </div>
-`,L=`---
+`,_=`---
 title: "Huawei Cloud LTS Alert Events"
 description: "Sync Huawei Cloud Log Tank Service (LTS) alert events to Flashduty via webhook for automated alert noise reduction."
 date: "2024-08-20T10:00:00+08:00"
@@ -7642,4 +7642,61 @@ As shown in the image below:
 
 <img src="https://download.flashcat.cloud/flashduty/changelog/20230720/email_render.png" alt="drawing" style="display: block; margin: 0 auto;" width="500"/>
 
-</div>`,oe={CustomAlert:n,Email:t,N9e:a,Prometheus:i,Grafana:o,Zabbix:s,UptimeKuma:r,AliyunARMS:l,AliyunCmEvent:d,AliyunCm:c,AliyunSLS:e,AWSCW:e,AzureMonitor:h,BaiDuBCM:u,HuaWeiCES:g,InfluxDB:p,OpenFalcon:m,PagerDuty:f,TencentBK:y,TencentCLS:v,TencentCm:b,TencentEb:w,OceanBase:C,Graylog:k,Skywalking:I,Sentry:S,Jiankongbao:A,AWSEventBridge:x,Dynatrace:_,HuaweiyunLTS:L,GoogleCM:F,Zilliz:q,Splunk:R,AppDynamics:T,SolarWinds:D,VolcEngineMetric:U,VolcEngineEvent:E,VolcEngineTLS:N,OpManager:P,Meraki:M,StateCloud:W,Guance:G,CustomChange:z,Jira:V,Lark:K,Dingtalk:J,Wecom:Z,Slack:Q,MicrosoftTeams:X,AlertWebhook:ee,IncidentWebhook:ne,CustomAction:te,Templates:ie,HuaweiyunAPM:O,JiraSync:ae,ZStack:Y,Keep:H,ElastAlert2:$,DingtalkAlert:j,FeishuAlert:B};module.exports=oe;
+</div>`,oe=`---
+title: "Link Integration"
+description: "Through Link integration, you can quickly access external links by obtaining key parameters from incident attributes, labels, and other information"
+date: "2025-05-19T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/link-integration-guide"
+---
+
+Through Link integration, you can quickly access external links by obtaining key parameters from incident attributes, labels, and other information
+
+## Configuration Guide
+
+Link integration supports extracting key parameters from incident attributes, labels, and other information to enable quick navigation to external systems. Through automated parameter filling and redirection, it eliminates manual input, improving the efficiency of problem identification and resolution. This feature is applicable to incident troubleshooting, performance monitoring, and system debugging scenarios, helping optimize operations processes and enhance response speed and accuracy.
+
+### Opening Methods
+
+#### 1. Pop-up Window
+Opens a window in the current incident details page, maintaining the original interface state, suitable for quick viewing or returning after operations
+
+#### 2. New Tab
+Opens the link in a new browser tab, suitable for scenarios where you need to retain the current operation context while accessing external content
+
+### URL Configuration
+
+When referencing content from labels, start with labels.; when referencing custom fields, start with fields.; when referencing incident attributes, reference them directly, such as .title .severity
+
+#### Retrieving from Incident Labels
+Supports dynamic value retrieval through \${} syntax to construct request URLs. For example, parameter values can be automatically filled from incident labels, requiring no manual input:
+  
+\`\`\`
+https://cmdb.com/vm?sn=\${labels.sn}
+\`\`\`
+
+In the above example, \${labels.sn} indicates that the sn label value from the incident will be dynamically injected into the URL. If the incident data contains sn=VM123456, the final request URL will be:
+
+\`\`\`
+https://cmdb.com/vm?sn=VM123456
+\`\`\`
+
+
+#### Retrieving from Custom Fields
+Supports dynamic value retrieval through \${} syntax to construct request URLs. For example, parameter values can be automatically filled from custom fields, requiring no manual input:
+  
+\`\`\`
+https://cmdb.com/vm?sn=\${fields.sn}
+\`\`\`
+
+In the above example, \${fields.sn} indicates that the sn custom field value will be dynamically injected into the URL. If the custom field data contains sn=VM123456, the final request URL will be:
+
+\`\`\`
+https://cmdb.com/vm?sn=VM123456
+\`\`\`
+
+### Notes
+
+1. When referenced content does not exist, Link integration will still generate the corresponding link but will not be able to retrieve the value
+2. Each channel can bind up to three Link integrations
+3. Pay attention to reference syntax; improper variable reference formatting will result in failure to retrieve corresponding values
+`,se={CustomAlert:n,Email:t,N9e:a,Prometheus:i,Grafana:o,Zabbix:s,UptimeKuma:r,AliyunARMS:l,AliyunCmEvent:d,AliyunCm:c,AliyunSLS:e,AWSCW:e,AzureMonitor:h,BaiDuBCM:u,HuaWeiCES:g,InfluxDB:p,OpenFalcon:m,PagerDuty:f,TencentBK:y,TencentCLS:v,TencentCm:b,TencentEb:w,OceanBase:C,Graylog:k,Skywalking:I,Sentry:S,Jiankongbao:A,AWSEventBridge:x,Dynatrace:L,HuaweiyunLTS:_,GoogleCM:F,Zilliz:q,Splunk:R,AppDynamics:T,SolarWinds:D,VolcEngineMetric:U,VolcEngineEvent:E,VolcEngineTLS:N,OpManager:P,Meraki:M,StateCloud:W,Guance:G,CustomChange:z,Jira:V,Lark:K,Dingtalk:J,Wecom:Z,Slack:Q,MicrosoftTeams:X,AlertWebhook:ee,IncidentWebhook:ne,CustomAction:te,Templates:ie,HuaweiyunAPM:O,JiraSync:ae,ZStack:Y,Keep:H,ElastAlert2:$,DingtalkAlert:j,FeishuAlert:B,Link:oe};module.exports=se;

package/dist/esm/zh.js

@@ -3605,7 +3605,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/dynatrace-integration-guide"
 |CUSTOM_ALERT|Info|提醒|
 
 </div>
-`,I=`---
+`,L=`---
 title: "华为云日志服务 LTS 告警事件"
 description: "通过 webhook 的方式同步华为云日志服务 LTS 告警事件到 Flashduty，实现告警事件自动化降噪处理。"
 date: "2024-08-20T10:00:00+08:00"
@@ -3721,7 +3721,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/huaweilts-integration-guide"
 |Info|Info|提醒|
 
 </div>
-`,L=`---
+`,I=`---
 title: "GoogleCloudMonitoring 告警事件"
 description: "通过 webhook 的方式同步 GoogleCloudMonitoring 告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-07-05T10:00:00+08:00"
@@ -4344,7 +4344,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/volcengine-event-integration-guid
 |通知|Info|提醒|
 
 </div>
-`,W=`---
+`,$=`---
 title: "火山引擎日志服务 TLS 告警事件"
 description: "通过 webhook 的方式同步火山引擎日志服务 TLS 告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-07-05T10:00:00+08:00"
@@ -4481,7 +4481,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/volcengine-tls-integration-guide"
 |通知|Info|提醒|
 
 </div>
-`,$=`---
+`,W=`---
 title: "Opmanager 告警事件"
 description: "通过 webhook 的方式同步 Opmanager 告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-07-05T10:00:00+08:00"
@@ -4780,7 +4780,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/statecloud-integration-guide"
 
 
 </div>
-`,j=`---
+`,U=`---
 title: "观测云告警事件"
 description: "通过 webhook 的方式同步观测云告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-07-05T10:00:00+08:00"
@@ -4868,7 +4868,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/guance-integration-guide"
 | 数据断档     | Info     | 提醒 |
 
 </div>
-`,U=`---
+`,j=`---
 title: "zilliz 告警事件"
 description: "通过 webhook 的方式同步 zilliz 告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-07-05T10:00:00+08:00"
@@ -5342,7 +5342,7 @@ flashduty_env: "dev"
 # ------- FlashDuty ----------------
 \`\`\`
 
-5.重启 ElastAlert，等待告警触发。`,J=`---
+5.重启 ElastAlert，等待告警触发。`,V=`---
 title: "钉钉告警集成"
 description: "在 Flashduty 生成唯一的钉钉机器人地址，通过钉钉的方式将告警的发生与恢复同步到 Flashduty"
 date: "2025-05-19T10:00:00+08:00"
@@ -5425,7 +5425,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/dingtalk-alert-integration-guide"
 
 当前钉钉告警集成推送到 Flashduty 的严重程度均为Warning。
 
-`,G=`---
+`,J=`---
 title: "飞书告警集成"
 description: "在 Flashduty 生成唯一的飞书机器人地址，通过飞书的方式将告警的发生与恢复同步到 Flashduty"
 date: "2025-05-19T10:00:00+08:00"
@@ -5508,7 +5508,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/feishu-alert-integration-guide"
 
 当前飞书告警集成推送到 Flashduty 的严重程度均为 Warning。
 
-`,V=`---
+`,G=`---
 title: "自定义变更事件集成指引"
 description: "通过标准协议推送自有系统变更事件到 Flashduty，大部分故障由变更导致，变更和告警事件联动有助于快速定位故障原因。"
 date: "2025-05-19T10:00:00+08:00"
@@ -7938,4 +7938,61 @@ msg_type 必填，值为 post
 <img src="https://download.flashcat.cloud/flashduty/changelog/20230720/email_render.png" alt="drawing" style="display: block; margin: 0 auto;" width="500"/>
 
 </div>
-`,dn={CustomAlert:n,Email:t,N9e:e,Prometheus:a,Grafana:i,Zabbix:s,UptimeKuma:l,AliyunARMS:d,AliyunCmEvent:o,AliyunCm:r,AliyunSLS:c,AWSCW:u,AzureMonitor:h,BaiDuBCM:m,HuaWeiCES:p,InfluxDB:g,OpenFalcon:y,PagerDuty:f,TencentBK:b,TencentCLS:v,TencentCm:w,TencentEb:_,OceanBase:k,Graylog:F,Skywalking:x,Sentry:T,Jiankongbao:A,AWSEventBridge:S,Dynatrace:C,HuaweiyunLTS:I,GoogleCM:L,Splunk:D,AppDynamics:P,SolarWinds:M,VolcEngineMetric:N,VolcEngineEvent:E,VolcEngineTLS:W,OpManager:$,Meraki:R,Zilliz:U,StateCloud:z,Guance:j,CustomChange:V,Jira:K,Lark:Z,Dingtalk:X,Wecom:Y,Slack:Q,MicrosoftTeams:nn,AlertWebhook:tn,IncidentWebhook:en,CustomAction:an,Templates:ln,HuaweiyunAPM:H,JiraSync:sn,ZStack:O,Keep:q,ElastAlert2:B,DingtalkAlert:J,FeishuAlert:G};module.exports=dn;
+`,dn=`---
+title: "Link 集成"
+description: "通过 Link 集成，可直接从故障属性、标签等信息中获取访问外部链接所需的关键参数，实现快速访问"
+date: "2025-05-19T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/zh/flashduty/link-integration-guide"
+---
+
+通过 Link 集成，可直接从故障属性、标签等信息中获取访问外部链接所需的关键参数，实现快速访问
+
+## 配置说明
+
+Link 集成功能支持从故障属性、标签等信息中提取关键参数，实现与外部系统的快速跳转。通过自动化填充和跳转，避免了手动输入，提高了问题定位与处理的效率。该功能适用于故障排查、性能监控和系统调试等场景，有助于优化运维流程，提升响应速度与准确性
+
+### 打开方式
+
+#### 1. 弹窗
+在故障详情的当前页面中弹出窗口，保持原有界面状态，适合快速查看或操作后返回
+
+#### 2. 新标签页
+在浏览器新标签中打开链接，适用于需要保留当前操作上下文并同时访问外部内容的场景
+
+### URL 配置
+
+URL的参数引用内容为标签时以 labels. 开头；引用内容为自定义字段时，以 fields. 开头；引用内容为故障属性时，直接引用即可，如 .title、.severity 等
+
+#### 故障标签中获取
+支持通过 \${} 的方式从参数中动态取值，用于构造请求地址。例如参数值从故障标签（labels）中自动填充，无需手动输入：
+  
+\`\`\`
+https://cmdb.com/vm?sn=\${labels.sn}
+\`\`\`
+
+在上述示例中，\${labels.sn} 表示将故障中的 sn 标签值动态注入至 URL 中。如果故障数据中包含 sn=VM123456，则最终请求地址为：
+
+\`\`\`
+https://cmdb.com/vm?sn=VM123456
+\`\`\`
+
+
+#### 自定义字段中获取
+支持通过 \${} 的方式从参数中动态取值，用于构造请求地址。例如参数值从自定义字段（fields）中自动填充，无需手动输入：
+  
+\`\`\`
+https://cmdb.com/vm?sn=\${fields.sn}
+\`\`\`
+
+在上述示例中，\${fields.sn} 表示将故障中的 sn 自定义字段值动态注入至 URL 中。如果自定义字段数据中包含 sn=VM123456，则最终请求地址为：
+
+\`\`\`
+https://cmdb.com/vm?sn=VM123456
+\`\`\`
+
+### 注意事项
+
+1. 当引用的内容不存在时，Link 集成会正常生成对应的链接，但无法获取到值
+2. 同一个协作空间至多绑定三个 Link 集成
+3. 注意引用语法，如未按照要求进行书写引用变量，会导致无法正常获取对应值
+`,on={CustomAlert:n,Email:t,N9e:e,Prometheus:a,Grafana:i,Zabbix:s,UptimeKuma:l,AliyunARMS:d,AliyunCmEvent:o,AliyunCm:r,AliyunSLS:c,AWSCW:u,AzureMonitor:h,BaiDuBCM:m,HuaWeiCES:p,InfluxDB:g,OpenFalcon:y,PagerDuty:f,TencentBK:b,TencentCLS:v,TencentCm:w,TencentEb:_,OceanBase:k,Graylog:F,Skywalking:x,Sentry:T,Jiankongbao:A,AWSEventBridge:S,Dynatrace:C,HuaweiyunLTS:L,GoogleCM:I,Splunk:D,AppDynamics:P,SolarWinds:M,VolcEngineMetric:N,VolcEngineEvent:E,VolcEngineTLS:$,OpManager:W,Meraki:R,Zilliz:j,StateCloud:z,Guance:U,CustomChange:G,Jira:K,Lark:Z,Dingtalk:X,Wecom:Y,Slack:Q,MicrosoftTeams:nn,AlertWebhook:tn,IncidentWebhook:en,CustomAction:an,Templates:ln,HuaweiyunAPM:H,JiraSync:sn,ZStack:O,Keep:q,ElastAlert2:B,DingtalkAlert:V,FeishuAlert:J,Link:dn};module.exports=on;

package/dist/iife/en.js

@@ -7642,4 +7642,61 @@ By default, the system always creates new alerts for each message, but you can s
 
 Currently, all alerts pushed to Flashduty through Feishu Alert integration are set to Warning severity.
 
+`,Link:`---
+title: "Link Integration"
+description: "Through Link integration, you can quickly access external links by obtaining key parameters from incident attributes, labels, and other information"
+date: "2025-05-19T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/link-integration-guide"
+---
+
+Through Link integration, you can quickly access external links by obtaining key parameters from incident attributes, labels, and other information
+
+## Configuration Guide
+
+Link integration supports extracting key parameters from incident attributes, labels, and other information to enable quick navigation to external systems. Through automated parameter filling and redirection, it eliminates manual input, improving the efficiency of problem identification and resolution. This feature is applicable to incident troubleshooting, performance monitoring, and system debugging scenarios, helping optimize operations processes and enhance response speed and accuracy.
+
+### Opening Methods
+
+#### 1. Pop-up Window
+Opens a window in the current incident details page, maintaining the original interface state, suitable for quick viewing or returning after operations
+
+#### 2. New Tab
+Opens the link in a new browser tab, suitable for scenarios where you need to retain the current operation context while accessing external content
+
+### URL Configuration
+
+When referencing content from labels, start with labels.; when referencing custom fields, start with fields.; when referencing incident attributes, reference them directly, such as .title .severity
+
+#### Retrieving from Incident Labels
+Supports dynamic value retrieval through \${} syntax to construct request URLs. For example, parameter values can be automatically filled from incident labels, requiring no manual input:
+  
+\`\`\`
+https://cmdb.com/vm?sn=\${labels.sn}
+\`\`\`
+
+In the above example, \${labels.sn} indicates that the sn label value from the incident will be dynamically injected into the URL. If the incident data contains sn=VM123456, the final request URL will be:
+
+\`\`\`
+https://cmdb.com/vm?sn=VM123456
+\`\`\`
+
+
+#### Retrieving from Custom Fields
+Supports dynamic value retrieval through \${} syntax to construct request URLs. For example, parameter values can be automatically filled from custom fields, requiring no manual input:
+  
+\`\`\`
+https://cmdb.com/vm?sn=\${fields.sn}
+\`\`\`
+
+In the above example, \${fields.sn} indicates that the sn custom field value will be dynamically injected into the URL. If the custom field data contains sn=VM123456, the final request URL will be:
+
+\`\`\`
+https://cmdb.com/vm?sn=VM123456
+\`\`\`
+
+### Notes
+
+1. When referenced content does not exist, Link integration will still generate the corresponding link but will not be able to retrieve the value
+2. Each channel can bind up to three Link integrations
+3. Pay attention to reference syntax; improper variable reference formatting will result in failure to retrieve corresponding values
 `};n.FlashDocsEn=u})(window);

package/dist/iife/zh.js

@@ -7938,4 +7938,61 @@ url: "https://docs.flashcat.cloud/zh/flashduty/feishu-alert-integration-guide"
 
 当前飞书告警集成推送到 Flashduty 的严重程度均为 Warning。
 
+`,Link:`---
+title: "Link 集成"
+description: "通过 Link 集成，可直接从故障属性、标签等信息中获取访问外部链接所需的关键参数，实现快速访问"
+date: "2025-05-19T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/zh/flashduty/link-integration-guide"
+---
+
+通过 Link 集成，可直接从故障属性、标签等信息中获取访问外部链接所需的关键参数，实现快速访问
+
+## 配置说明
+
+Link 集成功能支持从故障属性、标签等信息中提取关键参数，实现与外部系统的快速跳转。通过自动化填充和跳转，避免了手动输入，提高了问题定位与处理的效率。该功能适用于故障排查、性能监控和系统调试等场景，有助于优化运维流程，提升响应速度与准确性
+
+### 打开方式
+
+#### 1. 弹窗
+在故障详情的当前页面中弹出窗口，保持原有界面状态，适合快速查看或操作后返回
+
+#### 2. 新标签页
+在浏览器新标签中打开链接，适用于需要保留当前操作上下文并同时访问外部内容的场景
+
+### URL 配置
+
+URL的参数引用内容为标签时以 labels. 开头；引用内容为自定义字段时，以 fields. 开头；引用内容为故障属性时，直接引用即可，如 .title、.severity 等
+
+#### 故障标签中获取
+支持通过 \${} 的方式从参数中动态取值，用于构造请求地址。例如参数值从故障标签（labels）中自动填充，无需手动输入：
+  
+\`\`\`
+https://cmdb.com/vm?sn=\${labels.sn}
+\`\`\`
+
+在上述示例中，\${labels.sn} 表示将故障中的 sn 标签值动态注入至 URL 中。如果故障数据中包含 sn=VM123456，则最终请求地址为：
+
+\`\`\`
+https://cmdb.com/vm?sn=VM123456
+\`\`\`
+
+
+#### 自定义字段中获取
+支持通过 \${} 的方式从参数中动态取值，用于构造请求地址。例如参数值从自定义字段（fields）中自动填充，无需手动输入：
+  
+\`\`\`
+https://cmdb.com/vm?sn=\${fields.sn}
+\`\`\`
+
+在上述示例中，\${fields.sn} 表示将故障中的 sn 自定义字段值动态注入至 URL 中。如果自定义字段数据中包含 sn=VM123456，则最终请求地址为：
+
+\`\`\`
+https://cmdb.com/vm?sn=VM123456
+\`\`\`
+
+### 注意事项
+
+1. 当引用的内容不存在时，Link 集成会正常生成对应的链接，但无法获取到值
+2. 同一个协作空间至多绑定三个 Link 集成
+3. 注意引用语法，如未按照要求进行书写引用变量，会导致无法正常获取对应值
 `};n.FlashDocsZh=t})(window);

package/dist/zh.d.ts

@@ -1,3 +1,4 @@
+/** ⬆️⬆️⬆️⬆️ Other ⬆️⬆️⬆️⬆️ */
 declare const docs: {
     CustomAlert: string;
     Email: string;
@@ -59,5 +60,6 @@ declare const docs: {
     ElastAlert2: string;
     DingtalkAlert: string;
     FeishuAlert: string;
+    Link: string;
 };
 export default docs;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "flashduty-knowledge-base",
-  "version": "1.2.7",
+  "version": "1.2.8",
   "description": "flashduty knowledge base",
   "type": "module",
   "engines": {