|
| 1 | +--- |
| 2 | +title: "Link Integration" |
| 3 | +description: "Through Link integration, you can quickly access external links by obtaining key parameters from incident attributes, labels, and other information" |
| 4 | +date: "2025-05-19T10:00:00+08:00" |
| 5 | +url: "https://docs.flashcat.cloud/en/flashduty/link-integration-guide" |
| 6 | +--- |
| 7 | + |
| 8 | +Through Link integration, you can quickly access external links by obtaining key parameters from incident attributes, labels, and other information |
| 9 | + |
| 10 | +## Configuration Guide |
| 11 | + |
| 12 | +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. |
| 13 | + |
| 14 | +### Opening Methods |
| 15 | + |
| 16 | +#### 1. Pop-up Window |
| 17 | +Opens a window in the current incident details page, maintaining the original interface state, suitable for quick viewing or returning after operations |
| 18 | + |
| 19 | +#### 2. New Tab |
| 20 | +Opens the link in a new browser tab, suitable for scenarios where you need to retain the current operation context while accessing external content |
| 21 | + |
| 22 | +### URL Configuration |
| 23 | + |
| 24 | +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 |
| 25 | + |
| 26 | +#### Retrieving from Incident Labels |
| 27 | +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: |
| 28 | + |
| 29 | +``` |
| 30 | +https://cmdb.com/vm?sn=${labels.sn} |
| 31 | +``` |
| 32 | + |
| 33 | +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: |
| 34 | + |
| 35 | +``` |
| 36 | +https://cmdb.com/vm?sn=VM123456 |
| 37 | +``` |
| 38 | + |
| 39 | + |
| 40 | +#### Retrieving from Custom Fields |
| 41 | +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: |
| 42 | + |
| 43 | +``` |
| 44 | +https://cmdb.com/vm?sn=${fields.sn} |
| 45 | +``` |
| 46 | + |
| 47 | +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: |
| 48 | + |
| 49 | +``` |
| 50 | +https://cmdb.com/vm?sn=VM123456 |
| 51 | +``` |
| 52 | + |
| 53 | +### Notes |
| 54 | + |
| 55 | +1. When referenced content does not exist, Link integration will still generate the corresponding link but will not be able to retrieve the value |
| 56 | +2. Each channel can bind up to three Link integrations |
| 57 | +3. Pay attention to reference syntax; improper variable reference formatting will result in failure to retrieve corresponding values |
0 commit comments