From 225aced1e1c7d23a61bf1505e0ac1781cba276ea Mon Sep 17 00:00:00 2001 From: Flashduty AI-SRE Date: Wed, 2 Sep 2026 09:02:52 +0000 Subject: [PATCH] =?UTF-8?q?docs:=20daily=20doc-review=202026-09-02=20?= =?UTF-8?q?=E2=80=94=20multi-time-zone=20support,=20member=20detail=20page?= =?UTF-8?q?,=20RUM=20remote=20configuration?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - platform: org/personal/schedule time-zone settings (f002,f005) + member list time zone column - platform: new member detail page (f003) - rum: application remote configuration (sampling rates, privacy level, rules, versioning) (f001) - on-call: incident list filter bar revamp — three-state assignment toggle (f004) - ai-sre: on-prem public-share requires CDN base (f006) - changelog: 2026-09-02 entry (f007-f009) --- en/ai-sre/artifacts.mdx | 4 ++ en/changelog/changelog.mdx | 36 ++++++++++++++++ .../configuration/personal-settings.mdx | 10 +++++ en/on-call/configuration/schedule.mdx | 5 +++ en/on-call/incident/search-view-incident.mdx | 15 ++++--- en/platform/organization-info.mdx | 9 ++++ en/platform/team-members.mdx | 18 +++++++- en/rum/quickstart/app-management.mdx | 42 +++++++++++++++++++ zh/ai-sre/artifacts.mdx | 4 ++ zh/changelog/changelog.mdx | 36 ++++++++++++++++ .../configuration/personal-settings.mdx | 12 +++++- zh/on-call/configuration/schedule.mdx | 5 +++ zh/on-call/incident/search-view-incident.mdx | 15 ++++--- zh/platform/organization-info.mdx | 9 ++++ zh/platform/team-members.mdx | 18 +++++++- zh/rum/quickstart/app-management.mdx | 42 +++++++++++++++++++ 16 files changed, 261 insertions(+), 19 deletions(-) diff --git a/en/ai-sre/artifacts.mdx b/en/ai-sre/artifacts.mdx index ca47320e..fcb9a25e 100644 --- a/en/ai-sre/artifacts.mdx +++ b/en/ai-sre/artifacts.mdx @@ -124,6 +124,10 @@ Once you generate a public link, anyone who gets the link can view this artifact On success, the link is copied to your clipboard automatically (a "Public link generated and copied to clipboard" toast appears). The public link takes the form `https:///share/artifact/` — it's identified by the artifact's own ID and carries no token; anonymous access is served entirely by the CDN, without going through any endpoint that requires sign-in. + +On private deployments, public links require the instance to be configured with a reachable share static-asset base (CDN). When it is not configured, the share panel does not offer the **Public link** option and only "Account only" sharing is available; public links generated earlier remain manageable and revocable. SaaS is not affected by this restriction. + + Visitors who open a public link see a read-only content page: next to the title, the top of the page carries the disclaimer "**Content is user-generated and unverified.**" and a "**Feedback**" entry — clicking it opens a report form (pre-filled with the current link) so anyone can report inappropriate content to Flashduty. The page also provides a "Sign in" entry that leads visitors to the console. | Action | Description | diff --git a/en/changelog/changelog.mdx b/en/changelog/changelog.mdx index 1ec8a9f0..ef8f953c 100644 --- a/en/changelog/changelog.mdx +++ b/en/changelog/changelog.mdx @@ -4,6 +4,42 @@ description: "This page documents important updates and feature releases for Fla keywords: ["Changelog", "Product Release", "Feature Updates", "Flashduty", "Version History"] --- + + +### Multi-time-zone support + +Console times now render in the *viewer's* time zone, with settings at three levels: + +- **Organization time zone**: set by the subject account or an Account.Admin under **Settings → Organization Information**. Changing it requires a confirmation dialog spelling out the impact — members without a personal time zone switch immediately, while organization-level on-call schedules keep their original wall-clock time and do not shift. +- **Personal time zone**: members pick their own under **Settings → Personal Information → Display Preferences**; leaving it empty **follows the organization time zone**. When the detected browser zone differs, a one-click "Use" hint appears — saved settings are never overwritten automatically. +- **Schedule time zone**: a schedule must choose a time zone at creation; shifts and rotations are computed on that zone's wall-clock time and cannot be changed afterwards. The schedule list gains a **Time Zone** column, and the member list shows each member's zone (following or custom). + +See [Organization Information](/en/platform/organization-info), [Personal Settings](/en/on-call/configuration/personal-settings), and [Schedules](/en/on-call/configuration/schedule). + +### RUM application remote configuration + +Browser applications gain a **Remote Configuration** tab to tune collection parameters online, without shipping a new client build: + +- **Session / session-replay / trace sample rates**: integers 0–100 (%); leaving a field empty means it is not delivered and the SDK init value applies. The trace rate samples again at session level within already-collected sessions. +- **Replay privacy level**: `mask` / `mask-user-input` / `allow`; loosening the level requires an extra confirmation before publishing (uploaded replays cannot be retroactively masked). +- **Conditional rules**: split delivery by exact (AND) matching on `env`, `app_version`, and `sdk`; rules are evaluated top-down, first full match wins, up to 20 rules. +- **Versioned publishing**: diff preview before publish, change history (latest 50 versions), one-click revert, and a per-session adoption progress panel. +- **Custom entries**: up to 5 typed key–value pairs (string/number/boolean/JSON) passed through to client code. + +On SaaS the feature is rolled out account by account — contact support if the tab is not visible yet; private deployments have it enabled by default. See [Application Management](/en/rum/quickstart/app-management). + +### Member detail page + +Member rows in the member list and inside team detail pages are now clickable, opening a **member detail page**: + +- Contacts (with unverified warnings), roles and teams, current on-call status and the next shift, and incident notification channels per severity level — all in one place +- Admins may edit a member's notification email/phone and roles, resend invitations, and manage licenses on the member's behalf; admin-edited contacts must be re-verified by the member before they receive notifications +- Profiles and roles of SSO-synced members are maintained by the identity provider; the in-page edit entries stay locked + +See [Teams and Members](/en/platform/team-members). + + + ### React Native app support diff --git a/en/on-call/configuration/personal-settings.mdx b/en/on-call/configuration/personal-settings.mdx index 680c83d2..6fa8d6b3 100644 --- a/en/on-call/configuration/personal-settings.mdx +++ b/en/on-call/configuration/personal-settings.mdx @@ -49,6 +49,16 @@ Profiles of SSO-synced members are maintained by their identity provider; the ed For supported phone number regions, refer to [FAQ](/en/on-call/quickstart/faq). +### Display Preferences + +| Item | Description | +| --- | --- | +| **Time Zone** | Member accounts can set their own time zone; all times in the console are displayed in it. Leaving it empty means **follow the organization time zone**. When the detected browser time zone differs from the effective one, a "Detected you are in *zone* · Use" hint appears below the selector — click **Use** to adopt it in one click; the system never overwrites a time zone you have saved on its own. The subject account has no personal time zone — its display time zone *is* the organization time zone, which is changed on the **Organization Information** page | + + +The organization time zone is maintained by the subject account or an Account.Admin on the [Organization Information](/en/platform/organization-info) page. Changing it affects the time display of every member who follows the organization. + + ## Notification Preferences --- diff --git a/en/on-call/configuration/schedule.mdx b/en/on-call/configuration/schedule.mdx index d177fe03..16e4f70c 100644 --- a/en/on-call/configuration/schedule.mdx +++ b/en/on-call/configuration/schedule.mdx @@ -43,6 +43,11 @@ Understanding these concepts before configuration will help you better plan your - **Schedule Name**: 1–40 characters, must be unique within the account - **Owning Team**: Specifies which team manages this schedule; team members gain edit permissions for this schedule - **Schedule Description**: Supports Markdown syntax, content can be included in notifications; up to 500 characters + - **Time Zone**: Required. The schedule's rotations and shifts are computed on the **wall-clock time of this zone** (e.g. "handover at 09:00 daily" means 09:00 in the schedule's own zone). **It cannot be changed after creation**; to use a different zone, create a new schedule and migrate the dispatch policy references + + + The schedule list shows a **Time Zone** column. The roster page labels two zones side by side: "times on this page are shown in your time zone" is the viewer's effective zone (personal time zone, or the organization zone when none is set), while the **schedule time zone** is the zone the shifts are defined in; concrete times on screen are converted to the viewer's zone. + The Free plan allows you to create only 1 schedule. Upgrade to the Standard plan or higher to create more. diff --git a/en/on-call/incident/search-view-incident.mdx b/en/on-call/incident/search-view-incident.mdx index ca14552a..329a733a 100644 --- a/en/on-call/incident/search-view-incident.mdx +++ b/en/on-call/incident/search-view-incident.mdx @@ -13,14 +13,13 @@ Flashduty On-call provides two entry points to view the incident list. One is wi | # | Feature | Description | | :---: | :--- | :--- | -| 1 | Assignee | Defaults to incidents **Assigned to Me**, can switch to view all incidents in the account | -| 2 | My Channels | Defaults to all channels, can switch to view incidents in **My Channels** | -| 3 | Processing Progress | Filter incidents by progress, defaults to **All** | -| 4 | Time Filter | Supports relative time and custom range filtering | -| 5 | Search | Supports searching by incident title, ID, labels, and custom fields. After an incident's title, labels, or custom fields are updated, query results may be slightly delayed | -| 6 | More Filters | Supports rich dimension filtering, including severity, responders, related to me, creator, acknowledger, closer, snooze status, ever converged due to flapping, rare incidents, labels, and custom fields. The **Channels** and **Teams** filters are only visible under the global Incident Management entry, and Teams narrows incidents by the team that owns each channel; **Related to me** matches incidents where you are the creator, acknowledger, closer, or a responder | -| 7 | View Settings | Supports rich rendering options including **custom display attributes** and even aggregate views | -| 8 | Pagination | Pagination and items per page adjustment | +| 1 | Assignment toggle | A three-state control at the head of the filter bar: **All** / **Assigned to Me** (incidents where I am a responder) / **My Teams** (incidents in channels I belong to). It is mutually exclusive with the **Responders** and **Channels** filters in More Filters: manually selecting either one resets the toggle to **All** (manual selection takes precedence and is kept); the toggle only applies once those manual filters are cleared | +| 2 | Processing Progress | Filter incidents by progress, defaults to **All** | +| 3 | Time Filter | Supports relative time and custom range filtering | +| 4 | Search | Supports searching by incident title, ID, labels, and custom fields. After an incident's title, labels, or custom fields are updated, query results may be slightly delayed | +| 5 | More Filters | Supports rich dimension filtering, including severity, responders, related to me, creator, acknowledger, closer, snooze status, ever converged due to flapping, rare incidents, labels, and custom fields. The **Channels** and **Teams** filters are only visible under the global Incident Management entry, and Teams narrows incidents by the team that owns each channel; **Related to me** matches incidents where you are the creator, acknowledger, closer, or a responder | +| 6 | View Settings | Supports rich rendering options including **custom display attributes** and even aggregate views | +| 7 | Pagination | Pagination and items per page adjustment | For query performance, the query time range is limited based on your subscription tier: diff --git a/en/platform/organization-info.mdx b/en/platform/organization-info.mdx index df332e84..d1039d51 100644 --- a/en/platform/organization-info.mdx +++ b/en/platform/organization-info.mdx @@ -33,6 +33,15 @@ The Organization Profile section maintains the organization's identity. Only the | **Name** | Organization name, displayed in invitation emails and SMS messages | | **ID** | Unique identifier of the organization; provide it when integrating APIs or contacting support | | **Domain** | Dedicated subdomain for login and email integration push | +| **Time Zone** | The organization time zone. Members without their own personal time zone see all times in it. Only the subject account or an Account.Admin can change it | + +### Organization Time Zone + +The organization time zone determines what "organization-following" members see across the console. Changing it requires confirming the blast radius: + +- Every member **without** a personal time zone switches to the new zone **immediately**. +- **Organization-level on-call schedules keep their original wall-clock time** and do not shift when the organization time zone changes — a rotation written as "09:00 every day" in the schedule's own time zone stays 09:00 there. +- Members can override the display zone for themselves via the **Display Preferences** section of [Personal Settings](/en/on-call/configuration/personal-settings). ### Domain diff --git a/en/platform/team-members.mdx b/en/platform/team-members.mdx index f5c46464..0caaf17a 100644 --- a/en/platform/team-members.mdx +++ b/en/platform/team-members.mdx @@ -59,7 +59,7 @@ Click a team name to enter the team detail page, where you can: --- -In the member list, a warning icon appears next to unverified email addresses or phone numbers. Unverified contact methods cannot receive alert notifications. Please remind members to complete verification promptly. +In the member list, a warning icon appears next to unverified email addresses or phone numbers. Unverified contact methods cannot receive alert notifications. Please remind members to complete verification promptly. The list also shows each member's **Time Zone**: members without a personal time zone follow the organization time zone — see [Organization Information](/en/platform/organization-info) and [Personal Settings](/en/on-call/configuration/personal-settings) for details. ### Invitation Methods @@ -126,6 +126,22 @@ You can perform the following actions in the License column of the member list: The total number of licenses depends on your subscription plan. When all licenses are allocated, you need to release another member's license or upgrade your subscription to assign one to a new member. +### Member Detail Page + +In the member list (including the member list inside a team's detail page), click a member's name to open the **member detail page**, where that member's information is centralized: + +| Section | Capabilities | +| --- | --- | +| **Contact** | View the notification email and phone and their verification status; an admin with the right permissions may edit them on the member's behalf. **Note**: a contact edited by an admin becomes **unverified** again, and the member must verify it in person before it can receive notifications | +| **Roles & Teams** | Change the member's account roles; view the teams the member belongs to | +| **On-call Status** | See whether the member is on shift right now, the current shift's start/end and remaining time, and the next upcoming shift | +| **Incident Notification Settings** | View the channels enabled for the member at each incident severity level (critical / warning / info) | +| **Account Actions** | Edit the member's profile, resend the invitation, manage the License | + + +For members auto-created via SSO, the profile and roles are maintained by the identity provider; the corresponding edit entries on the member detail page are unavailable. + + ### Deleting Members diff --git a/en/rum/quickstart/app-management.mdx b/en/rum/quickstart/app-management.mdx index 36522ea8..710fb3e4 100644 --- a/en/rum/quickstart/app-management.mdx +++ b/en/rum/quickstart/app-management.mdx @@ -292,6 +292,48 @@ Privacy settings allow you to control the scope of user privacy data collected b After disabling geo-location or IP address collection, the related filter and analysis dimensions will no longer be available. Please adjust carefully based on your business requirements and compliance needs. +## Remote Configuration + +The **Remote Configuration** tab of a Browser application lets you adjust collection and privacy parameters online, without code changes or a new release. When enabled, the configuration on this page overrides SDK initialization settings. When disabled, clients fall back to their SDK initialization settings and data collection continues uninterrupted. + + +- Remote Configuration is currently available only for **Browser** applications. Other platform types will be enabled as their SDKs ship support. +- On SaaS the feature is rolled out account by account. If the **Remote Configuration** tab is not visible on the application detail page, contact support to enable it. On private deployments it is available by default. + + +### Configuration values + +| Field | Values | Description | +|------|------|------| +| **Session sample rate** | Integer 0–100 (%) | Percentage of sessions collected. Leave it empty to skip delivering this field; clients keep the value set at SDK initialization | +| **Session replay sample rate** | Integer 0–100 (%) | Percentage of sessions recorded by Session Replay. If empty, the SDK setting applies | +| **Trace sample rate** | Integer 0–100 (%) | A second session-level sampling pass within already-collected sessions, deciding which sessions inject trace headers into eligible requests; the outcome is consistent within one session. Overall trace coverage is roughly *session sample rate × trace sample rate*. If empty, the SDK setting applies | +| **Replay privacy level** | `mask` / `mask-user-input` / `allow` | Default masking of page content in Session Replay: `mask` obscures text and hides input values; `mask-user-input` keeps page text and hides only what users typed; `allow` records the page as it is. Loosening the level starts collecting content that was not collected before, and replays already uploaded cannot be retroactively masked. The console asks you to confirm again before publishing | +| **Custom configuration keys** | Key–value pairs typed as string / number / boolean / JSON | Delivered to clients together with the remote configuration and read by your application code; the platform does not interpret them. Up to 5 keys; each key name is at most 64 characters, each value at most 4 KB, and all custom entries together at most 16 KB | + + +Custom entries are delivered to clients and may be readable by end users. Never put secrets, access tokens, or personally sensitive information in them. + + +### Conditional rules + +Besides the default values, you can add conditional rules that deliver different configurations to different clients: + +- Match conditions support the `env`, `app_version`, and `sdk` dimensions, ANDed with exact comparison; a dimension the SDK does not report can never match. Each match value is at most 256 bytes. +- Rules are evaluated top-down and the **first fully matching rule wins**; its overrides are merged on top of the defaults, and fields the rule does not set keep the default values. +- Each application supports at most 20 rules. + +### Publishing and activation + +- Before publishing, the page shows a per-field diff against the live configuration and lets you inspect the raw JSON. Publishing creates a new version. +- By default the change activates on the **next new session**: sessions already running are unaffected, and new sessions gradually pick up the configuration — clients that support remote configuration usually finish switching within about 4 hours after a publish. +- You can choose **immediate activation** instead: when the new configuration arrives, the client ends the running session so a new session starts under the new values. This is intended for urgent situations — stopping an over-collection flood or ramping collection up right away — at the cost of splitting one visit into two sessions; visitors not collected previously will start producing data mid-visit. + +### Version history and adoption + +- Change history keeps the most recent 50 versions; older versions are cleaned up automatically and cannot be rolled back to. You can revert any retained version to make it the current configuration; a revert also produces a new version. +- The rollout panel reports the version distribution and adoption progress across recently arrived sampled sessions, distinguishing *waiting for new sessions*, *rolling out*, and *fully switched*, as well as sessions that *never received a configuration* or *did not report a version* (SDK too old or config never fetched), so you can confirm the release actually landed. + ## Delete Application If you no longer need an application, you can find the delete button at the bottom of the "Basic Info" tab in the application details. diff --git a/zh/ai-sre/artifacts.mdx b/zh/ai-sre/artifacts.mdx index 58754b77..9e4ee6ca 100644 --- a/zh/ai-sre/artifacts.mdx +++ b/zh/ai-sre/artifacts.mdx @@ -124,6 +124,10 @@ Agent 会先向你确认目标读者、内容/数据来源、交互与视觉风 生成成功后链接会自动复制到剪贴板（提示「公开链接已生成，已复制到剪贴板」）。公开链接的形式为 `https://<控制台域名>/share/artifact/<产物 ID>`——它以产物自身的 ID 为标识，不携带令牌；匿名访问完全由 CDN 提供，不经过任何需要登录的接口。 + +私有化部署下，公开链接依赖实例配置了可达的分享静态资源地址（CDN）。未配置时，分享面板不会出现「公开链接」选项，仅可「仅账户内」分享；此前已生成的公开链接仍可正常管理与撤销。SaaS 环境不受此限制。 + + 打开公开链接的访问者会看到只读的内容页：页面顶部在标题旁标注「**内容由用户生成，未经核实。**」声明，并提供「**反馈**」入口——点击跳转到举报表单（已自动预填当前链接），任何人都可以向 Flashduty 举报不当内容；页面同时提供「登录」入口，引导访问者登录控制台。 | 操作 | 说明 | diff --git a/zh/changelog/changelog.mdx b/zh/changelog/changelog.mdx index e2a20eed..7970c49b 100644 --- a/zh/changelog/changelog.mdx +++ b/zh/changelog/changelog.mdx @@ -4,6 +4,42 @@ description: "本页面记录 Flashduty 产品的重要更新和功能发布" keywords: ["更新日志", "产品发布", "功能更新", "Flashduty", "版本记录"] --- + + +### 多时区支持 + +控制台时间按「查看者时区」显示，新增三层时区设置： + +- **组织时区**：主体账号或 Account.Admin 在「设置 → 组织信息」中设置；修改前会弹确认框说明影响面——未单独设置个人时区的成员立即改按新时区显示，组织级值班表保留原有墙上时间、不随组织时区平移 +- **个人时区**：成员在「设置 → 个人资料 → 显示偏好」设置自己的时区，留空即**跟随组织时区**；检测到浏览器时区与生效时区不一致时可一键采用，系统不会自动改写已保存的设置 +- **值班表时区**：创建值班表时必须选择时区，班次与轮转按值班表时区的墙上时间计算，创建后不可修改；值班表列表新增「时区」列，成员列表同样展示每位成员的时区（跟随或自设） + +详见 [组织信息](/zh/platform/organization-info)、[个人设置](/zh/on-call/configuration/personal-settings) 与 [值班表](/zh/on-call/configuration/schedule)。 + +### RUM 应用远程配置 + +Browser 类型应用新增「远程配置」页签，无需客户端发版即可在线调整采集参数： + +- **会话采样率 / 会话回放采样率 / Trace 采样率**：0–100 百分比整数，留空表示不下发该项、沿用 SDK 初始化设置；Trace 采样率在已采集会话内再做会话级采样 +- **回放脱敏级别**：`mask` / `mask-user-input` / `allow` 三档，放宽级别发布前需二次确认（已上传的回放无法事后补脱敏） +- **条件规则**：按 `env`、`app_version`、`sdk` 精确匹配（AND）分流下发，规则自上而下首个完全匹配者生效，最多 20 条 +- **版本化发布**：发布前差异预览、变更历史（最近 50 个版本）、一键回滚，并提供按会话统计的采用进度面板 +- **自定义配置项**：最多 5 个键值对（字符串/数字/布尔/JSON）随配置透传给客户端代码读取 + +该功能在 SaaS 按账号逐步放量，未看到入口请联系支持开通；私有化部署默认可用。详见 [应用管理](/zh/rum/quickstart/app-management)。 + +### 成员详情页 + +成员列表与团队详情中的成员行现在可点击进入**成员详情**页： + +- 集中查看联系方式（含未验证提醒）、角色与团队、当前值班状态与下次值班、各级别故障通知渠道 +- 管理员可代成员修改通知邮箱/手机与角色、重发邀请、管理 License；代改后的联系方式需成员本人重新验证后才能收通知 +- SSO 同步成员的资料与角色由身份提供方维护，页面内编辑入口锁定 + +详见 [组织管理](/zh/platform/team-members)。 + + + ### React Native 应用支持 diff --git a/zh/on-call/configuration/personal-settings.mdx b/zh/on-call/configuration/personal-settings.mdx index 22a1318d..469fad2a 100644 --- a/zh/on-call/configuration/personal-settings.mdx +++ b/zh/on-call/configuration/personal-settings.mdx @@ -21,7 +21,7 @@ keywords: ["个人设置", "联系方式", "通知偏好", "API密钥", "账户 --- -个人设置入口为左下角用户图标 → **个人信息**。页面顶部为**账号名片**，下方为**登录与安全**设置。 +个人设置入口为左下角用户图标 → **个人信息**。页面顶部为**账号名片**，下方为**登录与安全**与**显示偏好**设置。 ### 账号名片 @@ -50,6 +50,16 @@ SSO 同步成员的资料由身份提供方维护，页面上的编辑入口不 支持的手机号地区，请参考 [常见问题](/zh/on-call/quickstart/faq)。 +### 显示偏好 + +| 配置项 | 说明 | +| --- | --- | +| **时区** | 成员账号可设置自己的时区，控制台各页面的时间按此时区显示；留空表示**跟随组织时区**。当检测到的浏览器时区与当前生效时区不一致时，下方会出现「检测到你在某个时区 · 使用」提示，点击 **使用** 即可一键采用；系统不会自动改动你已保存的时区。主体账号没有个人时区——它的显示时区就是组织时区，请前往 **组织信息** 页修改 | + + +组织时区由主体账号或 Account.Admin 在 [组织信息](/zh/platform/organization-info) 页统一维护；修改组织时区会影响所有「跟随组织」的成员的时间显示。 + + ## 通知偏好 --- diff --git a/zh/on-call/configuration/schedule.mdx b/zh/on-call/configuration/schedule.mdx index 6c90f31c..005f1044 100644 --- a/zh/on-call/configuration/schedule.mdx +++ b/zh/on-call/configuration/schedule.mdx @@ -44,6 +44,11 @@ Flashduty On-call 提供极具灵活性的值班编排能力，支持按天、 - **值班名称**：长度为 1~40 个字符，同一账户下不可重复 - **管理团队**：指定该值班表归属哪个团队管理，团队成员将获得该值班表的编辑权限 - **值班描述**：支持 Markdown 语法，该区域的内容可以在通知时携带，长度不超过 500 字符 + - **时区**：必填。该值班表的轮转与班次按**此时区的墙上时间**计算（例如「每天 09:00 交接」即值班表时区的 09:00）。**创建后不可修改**；确需更换时区时，请新建一张值班表并迁移分派策略的引用 + + + 值班表列表提供**时区**列。排班页面会同时标注两个时区：「本页时间以你的时区显示」指当前查看者的生效时区（个人时区，未设置则跟随组织时区），「值班表时区」指该表定义班次所用的时区；页面上展示的具体时刻均已换算为查看者时区。 + 免费版最多可创建 1 个值班表，升级至标准版及以上后可创建多个。 diff --git a/zh/on-call/incident/search-view-incident.mdx b/zh/on-call/incident/search-view-incident.mdx index 4b3ab59f..cb24d98f 100644 --- a/zh/on-call/incident/search-view-incident.mdx +++ b/zh/on-call/incident/search-view-incident.mdx @@ -14,14 +14,13 @@ Flashduty On-call 提供了两个入口查看故障列表。一个是协作空 | 序号 | 功能 | 说明 | | :---: | :--- | :--- | -| 1 | 分派人员 | 默认聚焦为 **分派给我** 的故障，可切换为查看整个账户下的故障 | -| 2 | 我的协作空间 | 默认聚焦为全部协作空间，可切换为查看**我的协作空间**的故障 | -| 3 | 处理进度 | 按照处理进度筛选故障，默认为 **全部** | -| 4 | 时间筛选 | 支持相对时间和自定义区间筛选 | -| 5 | 键入检索 | 支持搜索故障标题、ID、标签和自定义字段。故障标题、标签、自定义字段更新后，查询结果可能存在短暂延迟 | -| 6 | 更多筛选 | 支持丰富的维度筛选，包括严重程度、处理人员、与我相关、发起人员、认领人员、关闭人员、暂缓状态、抖动收敛过、新奇故障、标签和自定义字段等。其中**协作空间**和**团队**筛选仅在全局故障管理入口下可见，团队按协作空间归属的团队过滤故障；**与我相关**匹配我作为发起人员、认领人员、关闭人员或处理人员的故障 | -| 7 | 视图设置 | 支持丰富的渲染形式，包括引入 **自定义的展示属性**，甚至是聚合视图 | -| 8 | 分页设置 | 分页和单页条数调整 | +| 1 | 分派切换 | 筛选条行首的三态切换：**全部** / **分派给我**（处理人员是我的故障）/ **我的团队**（我所在协作空间内的故障）。该切换与「更多筛选」中的 **处理人员**、**协作空间** 互斥：手动选择这两个筛选任一有值时，切换自动归为「全部」（手动选择优先并保留）；清空手动筛选后切换方可继续生效 | +| 2 | 处理进度 | 按照处理进度筛选故障，默认为 **全部** | +| 3 | 时间筛选 | 支持相对时间和自定义区间筛选 | +| 4 | 键入检索 | 支持搜索故障标题、ID、标签和自定义字段。故障标题、标签、自定义字段更新后，查询结果可能存在短暂延迟 | +| 5 | 更多筛选 | 支持丰富的维度筛选，包括严重程度、处理人员、与我相关、发起人员、认领人员、关闭人员、暂缓状态、抖动收敛过、新奇故障、标签和自定义字段等。其中**协作空间**和**团队**筛选仅在全局故障管理入口下可见，团队按协作空间归属的团队过滤故障；**与我相关**匹配我作为发起人员、认领人员、关闭人员或处理人员的故障 | +| 6 | 视图设置 | 支持丰富的渲染形式，包括引入 **自定义的展示属性**，甚至是聚合视图 | +| 7 | 分页设置 | 分页和单页条数调整 | 为了查询性能，查询的时间范围存在限制。不同订阅版本对应不同的最大查询时间窗口： diff --git a/zh/platform/organization-info.mdx b/zh/platform/organization-info.mdx index f1e697b9..cb976ae4 100644 --- a/zh/platform/organization-info.mdx +++ b/zh/platform/organization-info.mdx @@ -34,6 +34,15 @@ keywords: ["组织信息", "组织资料", "通知设置", "故障处理", "暂 | **名称** | 组织名称，展示在邀请成员的邮件和短信中 | | **ID** | 组织的唯一标识，对接 API 或联系技术支持时提供 | | **域名** | 用于登录和邮件集成推送的专属子域名 | +| **时区** | 组织时区，未单独设置个人时区的成员按此时区看到所有时间。仅主体账号或 Account.Admin 可修改 | + +### 组织时区 + +组织时区决定控制台中「跟随组织时区」的成员所看到的时间。修改组织时区需要确认影响范围： + +- 所有未单独设置个人时区的成员，会**立即**改按新时区显示时间 +- **组织级值班表保留原有的墙上时间**，不会随组织时区改动而平移。换句话说，排班里写在值班表时区上的「每天 09:00」仍然是那个 09:00 +- 需要单独控制自己时间显示的个人时区，可在 [个人设置](/zh/on-call/configuration/personal-settings) 的「显示偏好」中设置 ### 域名 diff --git a/zh/platform/team-members.mdx b/zh/platform/team-members.mdx index 7a4d693c..7756f9af 100644 --- a/zh/platform/team-members.mdx +++ b/zh/platform/team-members.mdx @@ -60,7 +60,7 @@ keywords: ["团队管理", "成员管理", "邀请成员", "组织架构", "角 --- -成员列表中，未验证的邮箱或手机号旁会显示警告图标。未验证的联系方式无法接收告警通知，请提醒成员及时完成验证。 +成员列表中，未验证的邮箱或手机号旁会显示警告图标。未验证的联系方式无法接收告警通知，请提醒成员及时完成验证。列表同时展示每位成员的**时区**：未单独设置个人时区的成员显示为跟随组织，按组织时区生效，详见[组织信息](/zh/platform/organization-info)与[个人设置](/zh/on-call/configuration/personal-settings)。 ### 邀请方式 @@ -127,6 +127,22 @@ License 决定了成员是否可以查看和处理故障。在成员管理列表 License 总数取决于你的订阅版本。当所有 License 已分配完毕时，需要先释放其他成员的 License 或升级订阅才能为新成员分配。 +### 成员详情 + +在成员列表（含团队详情的成员列表）中点击成员名称，即可进入**成员详情**页，集中查看和管理该成员的信息： + +| 区块 | 能力 | +| --- | --- | +| **联系方式** | 查看通知邮箱与通知手机及其验证状态；拥有权限的管理员可代为修改。**注意**：管理员代改后，该联系方式会变为**未验证**状态，须成员本人完成验证后才能用于接收通知 | +| **角色与团队** | 变更成员的账户角色；查看成员所属的团队 | +| **值班状态** | 查看成员当前是否正在值班、本班起止与剩余时间，以及下次值班安排 | +| **故障通知设置** | 查看成员在 critical / warning / info 各级别故障下启用的通知渠道 | +| **账号操作** | 编辑成员资料、重发邀请、管理 License | + + +通过 SSO 自动创建（同步）的成员，其资料与角色由身份提供方维护，成员详情页中的对应编辑入口不可用。 + + ### 删除成员 diff --git a/zh/rum/quickstart/app-management.mdx b/zh/rum/quickstart/app-management.mdx index cc147347..d9a4d209 100644 --- a/zh/rum/quickstart/app-management.mdx +++ b/zh/rum/quickstart/app-management.mdx @@ -293,6 +293,48 @@ Link 集成会从当前事件上下文中提取变量并替换到 URL 模板中 关闭地理位置或 IP 地址采集后，相关筛选和分析维度将不再可用。请根据业务需求和合规要求谨慎调整。 +## 远程配置 + +Browser 应用的「远程配置」页签允许你在线调整采集与隐私参数，而无需改代码、重新发版。启用后，本页配置覆盖 SDK 初始化设置；停用后，各端恢复使用 SDK 初始化设置，数据采集不会停止。 + + +- 远程配置目前仅 **Browser** 类型应用支持，其他平台类型将随各端 SDK 发布逐步开放。 +- SaaS 环境下该功能按账号逐步放量。如果应用详情页未显示「远程配置」页签，请联系支持团队开通；私有化部署默认可用。 + + +### 配置项 + +| 配置项 | 取值 | 说明 | +|------|------|------| +| **会话采样率** | 0–100 整数（%） | 采集会话的比例。留空表示不下发该项，各端沿用 SDK 初始化时设置的值 | +| **会话回放采样率** | 0–100 整数（%） | 录制会话回放的比例。留空时沿用 SDK 设置 | +| **Trace 采样率** | 0–100 整数（%） | 在已采集的会话中再按此比例做一次会话级采样，决定哪些会话为符合条件请求注入 trace 头；同一会话内的结果一致。整体 Trace 覆盖率约为「会话采样率 × Trace 采样率」。留空时沿用 SDK 设置 | +| **回放脱敏级别** | `mask` / `mask-user-input` / `allow` | 会话回放对页面内容的默认遮蔽程度：`mask` 遮蔽文本并隐藏输入值；`mask-user-input` 保留页面文本、仅隐藏用户输入；`allow` 按原样录制。放宽级别会开始录制此前未采集的内容，且已上传的回放无法事后补充脱敏，发布前系统会再次确认 | +| **自定义配置项** | 键值对，类型支持字符串 / 数字 / 布尔值 / JSON | 随远程配置下发到客户端、由应用代码读取，平台不解析其内容。最多 5 个；键名最长 64 字符，单个值最大 4 KB，全部自定义项合计最大 16 KB | + + +自定义配置项会下发到客户端，可能被终端用户读取。请勿填写密钥、访问令牌或个人敏感信息。 + + +### 条件规则 + +除默认值外，你可以添加条件规则，向不同客户端下发不同配置： + +- 匹配条件支持 `env`、`app_version`、`sdk` 三个维度，条件之间为 AND 精确匹配；SDK 未上报的维度永不匹配该规则。单个匹配值最长 256 字节。 +- 规则自上而下求值，**第一条完全匹配的规则生效**；规则的覆盖值叠加在默认配置之上，规则未设置的字段沿用默认配置。 +- 每个应用最多 20 条规则。 + +### 发布与生效 + +- 发布前页面会逐项展示新版本与线上配置的差异，并可查看原始 JSON。确认后发布生成新版本。 +- 生效方式默认是「下一个新会话生效」：进行中的会话不受影响，新会话逐步使用新配置；支持远程配置的客户端通常在发布后约 4 小时内完成切换。 +- 也可选择「立即生效」：新配置到达时客户端会结束进行中的会话，让新会话立即按新配置采集。适用于需要立刻止血（停止过量采集）或立刻放量采集的应急场景；代价是一次访问被拆分为两个会话，此前未被采集的访客会从访问中途开始产生数据。 + +### 版本历史与采用情况 + +- 变更历史保留最近 50 个版本，更早的版本将自动清理且无法回滚。你可以将任一保留中的历史版本回滚为当前配置，回滚同样会生成新版本。 +- 发布面板按最近到达的采样会话展示版本分布与采用进度，并区分「等待新会话」「逐步生效中」「已全部切换」，以及「未接收到配置」「未上报版本」（SDK 版本过低或尚未拉取过配置）的会话，帮助你确认这一版是否真正铺开。 + ## 删除应用 如果您不再需要某个应用，可以在应用详情的「基础信息」页签底部找到删除按钮。