t Merge branch 'f-servicenow' into test

Author: niuweili

flashduty/en/0. Overview/1. Introduction.md

@@ -20,7 +20,7 @@ Flashduty is not Nightingale. As an open-source monitoring tool primarily contri
 ### On-call
 An intelligent on-call and alert collaboration platform supporting flexible on-call scheduling, automatic dispatching and escalation, and multi-channel notifications to ensure critical alerts are not missed. Integrated with automated workflows to improve team response efficiency.
 
-You can learn more at [On-call](https://docs.flashcat.cloud/en/flashduty/on-call/introduction?nav=flashduty).
+You can learn more at [On-call](https://docs.flashcat.cloud/en/flashduty/getting-started).
 
 ### Monitors (Beta)
 Multi-source monitoring and alerting engine supporting alert detection on data from various sources such as Prometheus, Elasticsearch, Clickhouse, and more.

flashduty/en/1. On-call/1. Getting Started/1.4 Product Comparison.md

@@ -141,9 +141,9 @@ After the application is released, you can access it via mobile/PC client. First
     - Return to the escalation rule configuration page, refresh and reselect the group chat list
     - If still unable to get the group chat list, try uninstalling the Cool App from the group and repeat the above steps. If it still doesn't work, please contact customer or dedicated technical support
 
-<img src="https://download.flashcat.cloud/flashduty/doc/en/ding/ding-18.png" alt="drawing" width="500"/>
+<img src="https://download.flashcat.cloud/flashduty/doc/en/dingtalk-install-1.png" alt="drawing" width="500"/>
 
-<img src="https://download.flashcat.cloud/flashduty/doc/en/ding/ding-19.png" alt="drawing" width="500"/>
+<img src="https://download.flashcat.cloud/flashduty/doc/en/dingtalk-install-2.png" alt="drawing" width="500"/>
 
 4. **Dingtalk Custom Application API Call Limits:** [Dingtalk Documentation](https://open.dingtalk.com/document/orgapp/descriptions-about-adjusting-limit-and-frequency-of-api-calls?spm=ding_open_doc.document.0.0.6f6b21d9WtkxJI)
 

flashduty/en/1. On-call/4. Configure On-call/4.13 Notification Bots.md

@@ -0,0 +1,278 @@
+---
+title: "ServiceNow Sync"
+description: "Sync incidents with ServiceNow Incidents through ServiceNow sync webhook."
+date: "2025-05-19T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/service-now-sync"
+---
+
+Through ServiceNow sync webhook, Flashduty incidents are associated and synchronized with ServiceNow Incidents to achieve integration between Flashduty and ServiceNow.
+
+## In ServiceNow
+
+### Create User
+
+1. Log in to the ServiceNow instance console, select `ALL`, enter `USERS` and select `Organization`-`Users`.
+2. Click `New` to create a new user.
+3. In the edit page, enter `flashduty` in the `User ID` field.
+4. Keep `Password needs reset`, `Web service access only`, and `Internal Integration User` unchecked.
+5. Submit and save.
+
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/snow/snow-1.png" />
+
+### Configure User
+The user used to access ServiceNow needs to have administrator roles.
+1. On the user list page, find the newly created `flashduty` user and go to the configuration page.
+2. In the edit page, click `Set Password` to set a password.
+3. Click `Roles` to add **admin and itil** roles.
+4. Click `Update` to update the configuration.
+
+<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/snow/snow-2.png" />
+
+
+
+## In Flashduty
+
+### Configure Integration
+
+Enter the username/password and instance name configured above into the integration information on the left and click Next to configure.
+
+- **Integration Name:** Define a name for the current integration.
+- **Management Team:** When a management team is selected, only team members and tenant administrators can edit this integration.
+- **Channel:** Select the channel where this integration takes effect.
+- **Sync Direction:** 
+    - To_ServiceNow: Sync Flashduty incidents to ServiceNow.
+    - From_ServiceNow: Sync ServiceNow Incidents to Flashduty.
+    - Two-way: Bidirectional sync between Flashduty and ServiceNow.
+- **Trigger Mode**:
+    - Auto Trigger: Requires configuration of corresponding conditions, Flashduty will automatically sync incidents that meet the conditions to ServiceNow.
+    - Manual Trigger: Requires manual triggering of ServiceNow sync in the More Actions section of the incident details page (the integration configuration name is the trigger name).
+- **Severity Mapping:** ServiceNow's Priority is determined by the combined values of Impact and Urgency, so you can refer to ServiceNow's `Priority Lookup Rules` for configuration. Additionally, note that only when ServiceNow Incident's Urgency changes will it trigger updates to Flashduty incident severity.
+- **Custom Field Mapping:** You can choose to sync certain labels or all labels of incidents as well as custom field content to ServiceNow fields (only text-type fields are supported).
+
+## In ServiceNow
+
+When sync direction is set to From_ServiceNow or Two-way, additional configuration is required in ServiceNow to sync ServiceNow Incidents to Flashduty. When syncing to Flashduty, there are two methods available, choose based on your actual needs.
+
+### Manual Sync
+
+This method relies on ServiceNow's UI Action and Script Include configuration. The effect achieved by following the steps below: When creating or updating an Incident, you can see a button to send sync requests in the function area. Triggering this button will sync the current Incident content to Flashduty. Note that if the request fails when triggered, please retry (retry interval should be greater than 10 seconds).
+
+#### Configure UI Action
+
+1. Log in to the ServiceNow instance console, select `ALL`, enter `UI Actions` and select `System Definition`-`UI Actions`.
+2. Click `New` to create a new Action.
+3. Enter **Send To Flashduty** in `Name`, select **Incident** in `Table`.
+4. Keep `Form button`, `Active`, `Show insert`, `Show update`, `Client`, `List v2/3 Compatible` checked.
+5. Enter **onClick();** in `Onclick`.
+6. Enter the following in `Script`:
+
+    ```
+    function onClick() {
+        g_form.save(); 
+
+        var ga = new GlideAjax('IncidentWebhookHelperAjax');
+        ga.addParam('sysparm_name', 'sendWebhook');
+        ga.addParam('sysparm_sys_id', g_form.getUniqueValue());
+        
+        ga.getXMLAnswer(function(response) {
+            alert('Webhook Triggered: ' + response);
+        });
+    }
+
+    ```
+
+7. Submit and save.
+
+#### Configure Script Include
+
+1. Log in to the ServiceNow instance console, select `ALL`, enter `Script Includes` and select `System Definition`-`Script Includes`.
+2. Click `New` to create a new Script Include.
+3. Enter **IncidentWebhookHelper** in `Name`, select **All application scopes** in `Accessible from`.
+4. Keep `Client callable` and `Active` checked.
+5. Enter the following content in `Script`, where you need to add the integration push URL in **request.setEndpoint**:
+
+<div class="hide">
+
+Note: The body configures default receiving fields. If you have custom fields that need to be synced to Flashduty, you need to manually add content to the body. For example, if you want to add a field named: test_001 (this field name can be obtained when adding custom fields in the integration configuration, do not use the field name displayed in the ServiceNow Incident form), then you need to add to the body: test_001: current.getDisplayValue("test_001").
+
+</div>
+    ```
+    var IncidentWebhookHelper = Class.create();
+    IncidentWebhookHelper.prototype = {
+    initialize: function() {},
+
+    sendIncidentWebhook: function(current) {
+        function getLastComment(sysId) {
+            var journalGR = new GlideRecord('sys_journal_field');
+            journalGR.addQuery('element_id', sysId);
+            journalGR.addQuery('element', 'comments');
+            journalGR.orderByDesc('sys_created_on');
+            journalGR.setLimit(1);
+            journalGR.query();
+            if (journalGR.next()) {
+                return journalGR.getValue('value');
+            }
+            return '';
+        }
+
+        var body = {
+            action_type: current.isNewRecord() ? 'insert' : 'update',
+            number: current.getValue("number"),
+            sys_id: current.getUniqueValue(),
+            short_description: current.getValue("short_description"),
+            description: current.getValue("description"),
+            state: current.getDisplayValue("state"),
+            impact: current.getDisplayValue("impact"),
+            urgency: current.getDisplayValue("urgency"),
+            comments: getLastComment(current.getUniqueValue())
+        };
+
+        try {
+            var request = new sn_ws.RESTMessageV2();
+            request.setHttpMethod("POST");
+            request.setEndpoint("PUSH URL");
+            request.setRequestHeader("Content-Type", "application/json");
+            request.setRequestBody(JSON.stringify(body));
+            request.executeAsync();
+            } catch (ex) {
+            gs.error("Webhook Call failed: " + ex.message);
+        }
+    },
+
+    type: 'IncidentWebhookHelper'
+    };
+
+    ```
+
+6. Submit and save.
+7. Return to the Script Includes list and continue creating.
+8. Click `New` to create a new Script Include.
+9. Enter **IncidentWebhookHelperAjax** in `Name`, select **All application scopes** in `Accessible from`.
+10. Keep `Client callable` and `Active` checked.
+11. Enter the following content in `Script`:
+
+    ```
+    var IncidentWebhookHelperAjax = Class.create();
+    IncidentWebhookHelperAjax.prototype = Object.extendsObject(global.AbstractAjaxProcessor, {
+    sendWebhook: function() {
+        var sysId = this.getParameter('sysparm_sys_id');
+        var gr = new GlideRecord('incident');
+        if (gr.get(sysId)) {
+            var helper = new IncidentWebhookHelper(); 
+            helper.sendIncidentWebhook(gr);
+                return 'Success';
+        }
+        return 'Request failed';
+    }
+    });
+    ```
+  
+12. Submit and save.
+
+### Auto Sync
+This method relies on ServiceNow's Business Rules configuration. Using this method, you can automatically sync Incidents to Flashduty when there are new or update events.
+
+#### Configure Business Rules
+
+1. Log in to the ServiceNow instance console, select `ALL`, enter `Business Rules` and select `System Definition`-`Business Rules`.
+2. Click `New` to create a new Business Rule.
+3. Enter **Send To Flashduty** in `Name`, select **Incident** in `Table`.
+4. Keep `Advanced` and `Active` checked.
+5. In the `When to run` section, select **async** in `When`, keep `Insert` and `Upsert` checked, configure others as needed.
+6. In the `Advanced` section, enter the following content in `Script`, where you need to add the integration push URL in **endpoint**:
+
+<div class="hide">
+
+Note: The body configures default receiving fields. If you have custom fields that need to be synced to Flashduty, you need to manually add content to the body. For example, if you want to add a field named: test_001 (this field name can be obtained when adding custom fields in the integration configuration, do not use the field name displayed in the ServiceNow Incident form), then you need to add to the body: test_001: current.getDisplayValue("test_001").
+
+</div>
+
+   ```
+    (function executeRule(current, previous) {
+        function getLastComment(recordSysId) {
+            var journalGR = new GlideRecord('sys_journal_field');
+            journalGR.addQuery('element_id', recordSysId);
+            journalGR.addQuery('element', 'comments');
+            journalGR.orderByDesc('sys_created_on');
+            journalGR.setLimit(1); 
+            journalGR.query();
+            if (journalGR.next()) {
+                var comment = journalGR.getValue('value');
+                return comment;
+            }
+    
+            return '';
+        }
+
+        var operation = current.operation() || 'unknown';
+        var isPreviousNull = previous === null;
+        var createdOn = current.getValue('sys_created_on');
+        var updatedOn = current.getValue('sys_updated_on');
+        var isNewRecord = createdOn === updatedOn; 
+
+        var action = 'update'; 
+        if (isPreviousNull && isNewRecord) {
+            action = 'insert'; 
+        }
+
+        var body = {
+            action_type: action,
+            number: current.getValue("number"),
+            sys_id: current.getUniqueValue(),
+            short_description: current.getValue("short_description"),
+            description: current.getValue("description"),
+            state: current.getDisplayValue("state"),
+            impact: current.getDisplayValue("impact"),
+            urgency: current.getDisplayValue("urgency"),
+            comments: getLastComment(current.getUniqueValue())
+        };
+
+        try {
+            var endpoint = ''; 
+            var request = new sn_ws.RESTMessageV2();
+            request.setHttpMethod("POST");
+            request.setEndpoint(endpoint);
+            request.setRequestHeader("Content-Type", "application/json");
+            request.setRequestBody(JSON.stringify(body));
+            request.executeAsync(); 
+        } catch (ex) {
+            gs.error("Error sending webhook: " + ex.message);
+        }
+
+})(current, previous);
+
+    ```
+7. Submit and save.
+
+## Sync Information
+
+### Form Fields
+| ServiceNow |  Flashduty | Notes |
+| ---------- | -------- | ---- |
+| Short_description    | Title |  |
+| Description    | Description  |  |
+| Additional comments     | Comments     |  |
+| State      | Progress     |  |
+| Urgency      | Severity     |  |
+| Others      | Custom Fields     |  |
+
+### Status Mapping
+
+| ServiceNow |  Flashduty | Notes |
+| ---------- | -------- | ---- |
+| New   | Trigger |  |
+| In Progress    | Processing  |  |
+| On Hold     | Snoozed     | Default snooze 2 hours  |
+| Resolved     | CLosed     |  |
+| Closed     | CLosed      |  |
+| Canceled    | CLosed      |  |
+
+
+### Priority Mapping
+Only when ServiceNow's Urgency value changes will it affect Flashduty's Severity
+
+| ServiceNow |  Flashduty | Notes |
+| ---------- | -------- | ---- |
+| Low   | Info |  |
+| Medium    | Warning  |  |
+| High     | Critical     |  |

flashduty/en/1. On-call/8. Integrations/8.3 IM integration/8.3.2 Dingtalk Integration Guide.md

@@ -31,7 +31,7 @@ The overview module focuses on the core metrics of your application across multi
 The performance analysis module focuses on full-chain monitoring of application loading and interaction experience, including:
 
 - **Page Performance**: Monitor trends and sample distribution of core page loading metrics such as FCP, LCP, CLS, and FCP.
-- **Long Tasks**: Events that block the browser's main thread for more than 50 milliseconds.
+- **Long Tasks**: A [long animation frame](https://developer.chrome.com/docs/web-platform/long-animation-frames#long-frames-api)  is when a rendering update is delayed beyond 50 milliseconds.
 - **XHR and Fetch Requests**: Analyze the loading performance of XHR and Fetch interfaces to locate slow interfaces.
 - **Static Resources**: Analyze the loading time of static resources to identify performance bottlenecks during application loading.
 

flashduty/en/1. On-call/8. Integrations/8.5 Webhooks/8.5.5 ServiceNow sync.md

@@ -25,6 +25,10 @@ In addition to core metrics, it also supports other auxiliary metrics:
 
 These metrics are automatically collected when users visit pages and reported to the Flashduty platform through the SDK. You can view detailed performance data in the analysis dashboard.
 
+:::tip
+Interaction to Next Paint and Largest Contentful Paint are not collected for pages opened in the background (for example, in a new tab or a window without focus).
+:::
+
 ## Metric Calculation Methods
 
 ### 1. Largest Contentful Paint (LCP)
@@ -53,6 +57,18 @@ These metrics are automatically collected when users visit pages and reported to
 - **Use case**: Optimize response speed for interaction-intensive pages (such as forms, navigation menus).
 
 
+## Monitoring Single Page Applications (SPA)
+
+For Single Page Applications (SPA), the RUM browser SDK distinguishes between two navigation types through the `loading_type` attribute: `initial_load` and `route_change`.
+
+1. History Single Page Applications
+If an interaction on a webpage causes the URL to change but the page does not refresh completely, the RUM SDK will start a new `view` using `loading_type:route_change`. RUM uses the [History API](https://developer.mozilla.org/en-US/docs/Web/API/History) to track URL changes.
+
+2. Hash Single Page Applications
+The RUM SDK automatically monitors frameworks that rely on hash (`#`) navigation. The SDK listens for `HashChangeEvent` and issues a new `view`. Events from HTML anchors that do not affect the current view context are ignored.
+
+For SPA applications, if you need to monitor performance after route changes, it is recommended to use the [Custom Performance Monitoring](#Custom%20Performance%20Monitoring) feature to measure performance metrics of specific components or interactions.
+
 ## Custom Performance Monitoring
 
 ### 1. Component-level Performance Measurement
@@ -122,13 +138,7 @@ document.addEventListener("scroll", function handler() {
 - Use descriptive naming (such as `login_form_render`).
 - Maintain naming consistency.
 
-### 2. SPA Scenario Handling
-
-- When route changes, timing is based on the start time of the current RUM view.
-- Some timers need to be reset.
-- Pay attention to metric continuity during page transitions.
-
-### 3. Performance Impact Control
+### 2. Performance Impact Control
 
 - Control the number of custom metrics.
 - Avoid frequent timing.
@@ -154,6 +164,15 @@ document.addEventListener("scroll", function handler() {
 - Ensure timers are started and stopped correctly.
 - Check timestamp accuracy in asynchronous scenarios.
 
+### 4. Empty Web Vitals Metrics Collection
+
+- **Background pages**: Pages opened in new tabs or unfocused windows, causing INP and LCP to be uncollectable
+- **SPA route changes**: During `loading_type:route_change`, Core Web Vitals metrics (LCP, CLS, INP, FCP) will not be re-collected
+- **Integration method**: Page loads completely before SDK is fully initialized
+- **Page lifecycle**: Page is closed or navigated away before metrics collection is complete
+- **Browser compatibility**: Older browser versions do not support certain Web Vitals APIs
+- **Empty page content**: Page has no measurable content elements (such as blank pages)
+
 ## Next Steps
 
 - [Performance Analysis](https://docs.flashcat.cloud/en/flashduty/rum/performance-analysis?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5)

flashduty/en/2. RUM/2. Applications/4. Analysis Dashboard.md

@@ -49,11 +49,11 @@ Flashduty CLI provides the `sourcemaps` command for uploading `sourcemap` files
    Ensure Node.js is installed, then install `flashcat-cli` via npm:
 
    ```bash
-   npm install -g @flashcat/flashcat-cli
+   npm install -g @flashcloud/flashcat-cli
    ```
 
 2. **Configure API Key and Service Information**
-   ![2025-05-15-17-34-06](https://docs-cdn.flashcat.cloud/imges/png/026bb83be5f7ba043118e877f6bc2a82.png)
+   ![2025-06-24-17-20-59](https://docs-cdn.flashcat.cloud/imges/png/03c8b8922e101dc0b14cfdf60d3e08cf.png)
    In the **Application Management - Source Management** menu, click the "Upload Source" panel, fill in the following information, and generate an upload script:
 
    - **API Key**: Used to authenticate your identity (e.g., `test2`).
@@ -178,4 +178,4 @@ Flashduty RUM (Real User Monitoring) integrates `sourcemap` functionality, suppo
 ## Next Steps
 
 - [Error Grouping](https://docs.flashcat.cloud/en/flashduty/rum/error-grouping?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5)
-- [Issue Status](https://docs.flashcat.cloud/en/flashduty/rum/issue-states?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5) 
+- [Issue Status](https://docs.flashcat.cloud/en/flashduty/rum/issue-states?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5)

flashduty/en/2. RUM/3. Performance Monitoring/2. Metrics.md

@@ -20,7 +20,7 @@ Flashduty 不是夜莺（Nightingale）。夜莺作为 Flashcat 主要贡献的
 ### On-call
 智能值班与告警协作平台，支持灵活的值班调度、自动分派与升级、全渠道通知，保障关键告警不被遗漏。集成自动化工作流，提升团队响应效率。
 
-您可前往[On-call](https://docs.flashcat.cloud/zh/flashduty/on-call/introduction)了解更多。
+您可前往[On-call](https://docs.flashcat.cloud/zh/flashduty/getting-started)了解更多。
 
 ### Monitors (Beta)
 多源监控与告警引擎，支持对Prometheus、Elasticsearch、Clickhouse等各种来源数据进行告警判断。