docs: doc-review 2026-09-30 (diff) — dashboards page, RUM repository linking, on-prem license reminders

docs.json

@@ -3680,6 +3680,13 @@
                   "zh/monitors/explore/explore"
                 ]
               },
+              {
+                "group": "仪表盘",
+                "icon": "chart-line",
+                "pages": [
+                  "zh/monitors/dashboards/dashboards"
+                ]
+              },
               {
                 "group": "实体树",
                 "icon": "sitemap",
@@ -5316,6 +5323,13 @@
                   "en/monitors/explore/explore"
                 ]
               },
+              {
+                "group": "Dashboards",
+                "icon": "chart-line",
+                "pages": [
+                  "en/monitors/dashboards/dashboards"
+                ]
+              },
               {
                 "group": "Entity Tree",
                 "icon": "sitemap",

en/ai-sre/apps.mdx

@@ -27,6 +27,10 @@ AI SRE sessions run in a **Flashduty cloud sandbox** by default. The sandbox is
 **BYOC (self-hosted Runner) generally doesn't need it.** A Runner runs on your own machine, which usually **already has `gh` / `glab` / `git` credentials configured** (you work with repositories on it every day). In that case the agent just uses the host's own credentials — **no App authorization needed**. (If the host happens to have no credentials configured, authorizing the App lets BYOC sessions use it too.) For the differences between environments, see [Environments (BYOC)](/en/ai-sre/environments).
 </Note>
 
+<Tip>
+A RUM application can also record the repositories that build it (several may be linked; the first one is the primary), so that AI goes straight to the code when it analyses a RUM problem — see [Application Management · Code repositories](/en/rum/quickstart/app-management#code-repositories). Linking a repository there **grants no access by itself**: what a cloud AI session can read is still only what is authorized for the account here.
+</Tip>
+
 ## Where to Find It
 
 ---

en/ai-sre/sessions.mdx

@@ -138,9 +138,9 @@ When the console publishes a new version, a **version update notice** appears ab
     **Inline truncation of large files**: apart from archives (which are not parsed — the agent gets only their sandbox path), attachments reach the agent as extracted text. When the extracted text exceeds **64 KB**, only the first **32 KB** is inlined (cut at a valid UTF-8 boundary), and the attachment envelope carries a pointer to the full file staged in the sandbox (like `~/.flashduty/attachments/...`) — if the full content matters, ask the agent to read the file from the sandbox with the read / bash tools; nothing is lost. In addition, PDFs larger than **3 MB** are no longer passed natively to the model; they fall back to text extraction under the same truncation rule.
   </Accordion>
   <Accordion title="Context references" icon="link">
-    When you enter AI SRE from an incident, alert, monitor rule, monitor target, or datasource page, the related object is embedded into the input box as a **reference capsule** — a small inline tag indicating the kind of object referenced — an incident, alert event, alert, monitor rule, host, monitor target, datasource, or on-call analytics — that travels with the message so the agent can start its analysis from that object directly. Click the capsule to open the referenced object in a new tab, or click its close button to remove the reference before sending.
+    When you enter AI SRE from an incident, alert, monitor rule, monitor target, datasource, or RUM issue detail page (its **AI fix** button at the top right), the related object is embedded into the input box as a **reference capsule** — a small inline tag indicating the kind of object referenced — an incident, alert event, alert, monitor rule, host, monitor target, datasource, on-call analytics, or RUM issue — that travels with the message so the agent can start its analysis from that object directly. Click the capsule to open the referenced object in a new tab, or click its close button to remove the reference before sending.
 
-    **These entry points also carry a default question**, and the capsule sits at the spot the entry marks inside that sentence. Entering from a monitor target page, for instance, pre-fills "请分析这个监控对象 〈reference capsule〉：基于真实观测数据判断当前是否有问题或隐患，说明依据与影响面，并给出下一步排查或处置建议。请区分已确认事实、合理推断和待确认项；证据不足时明确说明不确定，不要过度归因"; entering from the datasource list pre-fills "调用 〈reference capsule〉 的 overview tool，校验 overview tool 是否可用". The prefill is only a draft — edit it, delete it, or send it as-is.
+    **These entry points also carry a default question**, and the capsule sits at the spot the entry marks inside that sentence. Entering from a monitor target page, for instance, pre-fills "请分析这个监控对象 〈reference capsule〉：基于真实观测数据判断当前是否有问题或隐患，说明依据与影响面，并给出下一步排查或处置建议。请区分已确认事实、合理推断和待确认项；证据不足时明确说明不确定，不要过度归因"; entering from the datasource list pre-fills "调用 〈reference capsule〉 的 overview tool，校验 overview tool 是否可用"; entering from a RUM issue detail page by clicking **AI fix** pre-fills "Use the rum skill to fix this RUM issue 〈reference capsule〉: follow the issue-fix workflow to fetch the issue context, then locate the failing code in the repositories linked to the application. Only when the root cause is confirmed and you are confident in the change, create a branch and open a Draft PR that links this issue in its description; otherwise give the analysis and fix suggestions without opening a PR. Never push directly to the default branch. Distinguish confirmed facts, reasonable inferences, and items to confirm.", and that button only appears when AI SRE is enabled for the account. The prefill is only a draft — edit it, delete it, or send it as-is.
 
     **A handoff carrying exactly one reference pre-fills its question**: when the merged context refs resolve to a single ref that carries the entry's default question, the input box is pre-filled with that question and the `[[ref]]` placeholder becomes the reference capsule. Clicking **AI analysis** on several incidents from the incident list, for example, pre-fills "Batch-analyze these incidents 〈reference capsule〉: first determine how they relate to each other (a shared root cause, a cascading chain, or fully independent) and group them accordingly; then give the likely root cause and impact for each group; finally give an overall remediation recommendation with priority. Fetch a single incident's details with tools only when needed, rather than expanding every incident up front. Separate confirmed facts, reasonable inferences, and open questions; state clearly when the evidence is insufficient, and never claim to have performed actions that were not performed.", with the capsule titled "Incident list (N)". A handoff carrying several references pre-fills nothing and leaves the input box as it is. A single message can carry multiple references. Besides objects carried in automatically from a related page, you can also type `@` directly in any session's input box to trigger an incident search dropdown (supporting fuzzy keyword search and a list of recent incidents); selecting one inserts the same kind of reference capsule — a standalone entry point available at any time. Typing an email address does not false-trigger it: when the `@` directly follows an email-address character (a letter, a digit, or one of `._%+-`), the picker does not open; an `@` after a space or adjacent to Chinese text still triggers it.
   </Accordion>

en/changelog/changelog.mdx

@@ -4,17 +4,41 @@ description: "This page documents important updates and feature releases for Fla
 keywords: ["Changelog", "Product Release", "Feature Updates", "Flashduty", "Version History"]
 ---
 
+<Update label="2026-09-30" description="📊 Dashboard comparisons and cross-panel cursor linking, RUM apps link to code repositories, on-prem License expiry reminders">
+
+### Monitors dashboards: comparisons, cross-panel cursor linking and point-value filtering
+
+A dashboard panel's query options gain **Compare** (period-over-period): "Previous 1 day / Previous 1 week" re-runs the same query over the window one period earlier — a time-series panel overlays a same-colour dashed line (the legend reads "N days ago / N weeks ago") and a stat panel shows the change against that period; only time-series and stat panels offer the setting, and a failed comparison query only drops the comparison line without affecting the current result. Time-series panels on one dashboard now share a cursor: moving the pointer over any of them draws the vertical line and dots at the same timestamp on all of them, with the tooltip only on the hovered panel (panels with a relative time or a time shift do not take part). When a data point's label — or a table's label column — has the same name as a dashboard variable, the click menu offers "Filter by k = v", which is the same as selecting that value in the variable bar and refreshes the whole dashboard (datasource variables are excluded); version history now matches an alert rule's change log — tick two versions, **Compare** their saved JSON, then restore. See [Dashboards](/en/monitors/dashboards/dashboards).
+
+### RUM applications can link to code repositories
+
+The RUM application detail page gains a **Code repositories** tab that links an application to the GitHub repositories that build it, so AI analysis can go straight to the code: up to 10 repositories, kept in order with the first one primary (use **Set as primary** to reorder), each entered as `owner/name` (a GitHub web or clone URL is accepted too) plus the directory holding the app inside that repository (defaults to `.`, at most 255 characters). Linking **grants no access by itself**: cloud AI sessions can only read repositories granted to the account's GitHub App installations, entries outside that grant carry a warning and a link to grant more, and manually entered repositories only help local (BYOC) AI; the tab appears only when AI SRE is enabled for the account. See [Application Management](/en/rum/quickstart/app-management#code-repositories).
+
+### Remote Configuration opens to every account
+
+The RUM application **Remote Configuration** tab is now open to every account instead of rolling out account by account: the account-level switch that decided which accounts could see the tab has been removed, and whether the tab appears depends only on whether the application's platform supports that channel. The previous advice to contact support when the tab is missing no longer applies. See [Application Management](/en/rum/quickstart/app-management#remote-configuration).
+
+### AI SRE sessions understand RUM issues as context
+
+AI SRE sessions gain a **RUM issue** context-ref kind (bug icon): entering a session through the **AI fix** button at the top right of a RUM issue detail page carries that capsule into the input box and pre-fills a fix question — fetch the issue's context through the issue-fix flow, then locate the failing code in the repositories linked to the application; when the root cause is confirmed and the change is safe, create a branch and submit a Draft PR that links the issue, and otherwise report only the analysis and recommendation, never pushing to the default branch. See [Sessions · Attachments and Context References](/en/ai-sre/sessions#attachments-and-context-references).
+
+### On-premises License expiry reminders
+
+Before an on-premises License expires, the platform reminds the contacts registered for the deployment: once each when **10, 3 and 1 days** remain (at most three per License), every contact's email address receives the reminder email and contacts with a valid mainland China phone number also receive an SMS, sent only between **08:00 and 22:00 Beijing time**, and Licenses that expired more than 7 days ago are skipped. The reminder email is fixed Chinese copy, and once the License expires the platform **stops ingesting data**; to renew, paste the new License into the License prompt in the console sidebar — the console reports "License updated, will take effect in 5 minutes" — with no service restart. See [Pricing · On-Premises License expiry and renewal](/en/platform/pricing#on-premises-license-expiry-and-renewal).
+
+### 46 new alert sources and 9 new change integrations
+
+This window registered **46 alert sources** (CrowdStrike, BigPanda, Monte Carlo, Falco, Gatus, OpenSearch and more) and **9 change integrations** (Argo Rollouts, Azure DevOps, Bitbucket, CircleCI, Flagsmith, Gitea, Octopus Deploy, Rundeck and Unleash). How to connect them and what they map are covered by [Alert sources](/en/on-call/integration/alert-integration/alert-sources/standard-alert) and [Change integrations](/en/on-call/integration/change-integration/custom-event).
+
+</Update>
+
 <Update label="2026-09-29" description="🎯 RUM remote configuration gains Data collection switches: unsampled sessions report their error after all">
 
-### RUM: unsampled sessions now upload once they error
 
-On the **Remote Configuration** tab of a Browser application, the section that used to hold only the sampling rates is now titled **Data collection** and carries two three-state switches (on / off / empty, which keeps the SDK setting):
 
-- **Error session capture** — a session the session sample rate did not draw is no longer dropped; it is buffered on the client, and when the SDK detects an error it uploads the data covering up to one minute before the error and keeps uploading what follows. A session that never errors is never uploaded, never stored, and never billed. It only applies to the sessions the sample rate missed, so it does nothing when that rate is 100
-- **Error session replay capture** — the same for Session Replay: a session the replay sample rate did not draw is still recorded locally and uploaded only once it errors, and how far back it reaches depends on view switches and buffer capacity. It is set separately from the session-events switch because replay is billed and masked on its own
-- Such a session is an **error-captured session**, with detail starting at the buffered window before the error. The full timeline in the session detail inserts a boundary row marking that start, so a list that reads shorter than the counts above it is not mistaken for missing data
+</Update>
 
-With these two switches you can keep your sampling rate at its usual value and let only the sessions that error send extra data, instead of pushing the rate to 100 to preserve errors. Both appear for Browser applications only. See [Application management](/en/rum/quickstart/app-management) and [Sampling strategy](/en/rum/best-practices/sampling).
+<Update label="2026-09-23" description="🤖 AI SRE queries Monitors data sources directly, similar-incident merge analysis, configurable Jira status mapping, and more">
 
 ### AI SRE queries Monitors data sources directly
 
@@ -92,7 +116,6 @@ A new Checkly synthetic-monitoring alert integration is available, so Checkly ch
 
 See [Checkly alert integration](/en/on-call/integration/alert-integration/alert-sources/checkly) for the full setup and troubleshooting steps.
 </Update>
-</Update>
 
 <Update label="2026-09-16" description="💰 AI SRE billing goes live, the plugin catalog consolidates onto Overview">