You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<summary>What are active and inactive users?</summary>
23
+
<summary>How does Flashduty On-call pricing work?</summary>
24
24
25
+
Flashduty On-call's pricing model is based on the number of licenses purchased, where each license corresponds to one account member. For example, if you only purchase one license, only one member can use all features of Flashduty On-call. However, you can still invite more members to join, but only members with licenses can perform operational configurations on the platform, while other members **cannot use any platform features** (limited to receiving incident notifications only). The specific differences are as follows:
25
26
26
-
FlashDuty's pricing model is based on the number of purchased licenses, with each license corresponding to an active user account. For example, if you only purchase one license, only one member can use all FlashDuty features as an active user. However, you can still invite more members to join, but only members with licenses can become active users and enjoy all features. The specific differences are as follows:
27
+
#### License Allocation Methods
27
28
28
-
#### Active User
29
+
- Administrators can actively allocate licenses to different members.
30
+
- When allocating licenses, you can set the license type.
31
+
- Fixed type: Valid for the entire purchase period, cannot be preempted, suitable for scenarios requiring participation in incident handling and business configuration.
32
+
- Temporary type: Automatically released at the end of each cycle, can be occupied through allocation or preemption when sufficient licenses are available.
29
33
30
-
- A user who has used the product in the current month is considered an active user, with each active user occupying one license. The count resets at the beginning of the next month.
31
-
- Logging in will occupy one license, making the user an active user.
32
-
- When an active user is deleted, their corresponding license will be released.
33
-
- Active users have full access to all features (subject to version and role permission limitations).
34
-
- Active users can transfer their own license to other inactive users.
34
+
#### Members Without Licenses
35
35
36
-
37
-
#### Inactive User
38
-
39
-
- Inactive users do not have any feature usage permissions, including viewing incident lists/details, **only passively receiving alert messages** via email, SMS, and IM group messages.
40
-
- In the configuration of the escalation policy, you can choose to notify the incident message to inactive users.
41
-
- Inactive users cannot view or close incidents.
42
-
- Inactive users share the email, SMS, and phone notification quota with active users.
43
-
- When logging in to the console for viewing/processing, they will be prompted with no permissions.
36
+
- Cannot use any features, including viewing incident lists/details, **can only passively receive alert messages**, such as receiving incident messages via email, SMS, phone calls, or IM group messages.
37
+
- When configuring assignment strategies, you can choose to notify members without licenses about incident messages.
38
+
- Members without licenses, even if they receive incident messages, cannot view, close, or perform other operations on them.
39
+
- Members without licenses share the tenant's email, SMS, and phone package quotas.
40
+
- Members without licenses will be prompted that they don't have permission when trying to view/handle operations after logging into the console.
44
41
45
42
</details>
46
43
47
-
48
44
<details>
49
45
<summary>What notification methods does Flashduty On-call support?</summary>
Copy file name to clipboardExpand all lines: flashduty/en/1. On-call/4. Configure On-call/4.1 Channels.md
+9-1Lines changed: 9 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,11 +35,18 @@ Log in to the console and navigate to: **Incident Management => Channel => Creat
35
35
-**Channel Name:** Recommended to name and plan based on department, team, or business type for better understanding of the channel's purpose.
36
36
-**Description:** Briefly summarize the business handled by this channel and the types of alerts it receives.
37
37
-**Management Team:** Set the management team during creation. **Team members have full operational permissions** for the channel, while non-creators have read-only access to channel configurations.
38
-
-**Auto-close Timeout:** Incidents not closed within N minutes will be **automatically closed by the system** (applies to all new incidents in this channel). Timeout-closed incidents will also **receive corresponding closure notifications** (notification channels depend on [escalation rule](https://docs.flashcat.cloud/en/flashduty/escalate-rule-settings?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5) configuration).
38
+
-**Auto-close Timeout:**
39
+
- Auto-close after incident trigger: Starts timing from the first incident trigger and automatically closes the incident after the specified time.
40
+
- Auto-close after stopping new alert merging: Starts timing from the last new alert merge and automatically closes the incident after the specified time.
39
41
-**Access Level:** The channel is visible to which users, **public** means all users can view and operate incidents within the channel, **private** means only the creator, management team, and main account can view and operate incidents within the channel.
40
42
- If incident assignment planning isn't ready, you can **skip setting escalation rules** and configure them after creation.
41
43
- Integration types added during creation are **exclusive integrations** that only apply to this channel and can be configured later after creation.
42
44
45
+
:::caution
46
+
Auto-close after stopping new alert merging is generally effective in alert grouping scenarios. For example, if grouping strategies are enabled within this channel, the alert closing time will be determined based on when the last alert was grouped into the incident.
47
+
48
+
:::
49
+
43
50
## Managing Channels
44
51
---
45
52
### Channel Overview
@@ -78,4 +85,5 @@ Log in to the console and navigate to: **Incident Management => Channel => Creat
78
85
- Alert grouping combines similar or related alerts into one incident.
79
86
- Configure grouping by alert title, severity, or label dimensions.
80
87
- Incident suppression automatically blocks notifications for identical incidents within a time period.
88
+
- Flapping detection can automatically suppress notifications for identical incidents within a time period.
81
89
- For more about **reduce noise**, see [Reduce Noise Settings](https://docs.flashcat.cloud/en/flashduty/noise-reduction-settings?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5).
Copy file name to clipboardExpand all lines: flashduty/en/1. On-call/4. Configure On-call/4.10 Alert Routing.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,6 +25,7 @@ Configuration path: **Integration Center => Alert Events => Select Integration D
25
25
**6. Insert Routes:** With multiple routing rules, you can insert new routes before or after existing ones, eliminating the need to adjust order manually.
26
26
**7. Default Route:** Shared integrations require at least one routing rule to receive alerts. A default routing rule is provided to distribute alerts to corresponding channels when no rules are configured or matched.
27
27
**8. Target Channels:** You can select multiple channels to receive matched alerts.
28
+
**9. Edit History:** Supports viewing historical configurations and quickly restoring to a specific version (the configuration button only appears when routes have been edited multiple times).
Access path for shared integration: **Integration Center => Alert Events**.
29
+
- When creating an integration, you can select the management team for that integration. If a management team is configured, only tenant administrators and team members will have permission to edit/configure that integration.
29
30
- Alert event types created in the Integration Center are global and **must use routing rules to direct alerts to one or multiple channels**.
30
31
- Each integration **must be configured with at least one receiving channel, otherwise the integration will not be effective and cannot receive alert events**.
31
32
- Shared integrations can be configured with [label enrichment](https://docs.flashcat.cloud/en/flashduty/label-enrichment-settings?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5), [alert Pipeline](https://docs.flashcat.cloud/en/flashduty/alert-pipelines?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5), [routing rules](https://docs.flashcat.cloud/en/flashduty/alert-routings?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5).
The system will only mark an incident as flapping when the same incident frequently triggers and recovers, and flapping detection is enabled. A "same incident" refers to incidents with the same Alert Key. The calculation method for Alert Key may vary across different alert sources, typically using the alert ID pushed from upstream systems as the unique identifier for the incident.
81
+
82
+
-**Disabled by default:** No flapping detection is performed.
83
+
-**Remind Only:** Incidents entering flapping state will continue to be notified according to the assignment strategy, serving as a reminder only.
84
+
-**Remind and Suppress:** Incidents entering flapping state will not trigger notifications after the initial alert.
- Access Account Center: Hover over the user icon in the top right corner and select Account Settings.
17
+
- Access Personal Center: Hover your mouse over the user icon in the bottom left corner, select Basic Information, or click Platform Management in the bottom left corner.
18
18
- View your account's personalized settings and configure personal contact information, account password, APP Key, notification methods, etc.
19
19
- You can configure the following items in Account Settings:
20
20
- Basic Information: Such as nickname, email, password, etc.
- There are two types of account identities: primary account and member account.
29
29
- Account nicknames support both Chinese and English characters, mainly used for display purposes.
30
30
- Verification code is required when modifying email or phone.
31
31
- Currently supported regions for phone numbers: mainland China, United States, Canada, Indonesia, Germany, Malaysia, Australia, Singapore, Thailand, Russia, South Korea, Saudi Arabia, Vietnam, Japan.
32
32
33
+
34
+
## Notification Methods
35
+
---
36
+
- Different notification methods can be configured for different alert severity levels.
37
+
- Notifications will follow personal preferences **only when incidents are directly assigned to an individual, or when assigned through an escalation rule with personal chat enabled and set to follow personal preferences**.
38
+
- When configuring IM applications like Dingtalk, WeCom, or Feishu/Lark, you need to first associate the application to receive corresponding notifications.
39
+
33
40
## APP Key
34
41
---
35
42
- APP key is an essential credential for API requests.
- Different notification methods can be configured for different alert severity levels.
49
-
- Notifications will follow personal preferences **only when incidents are directly assigned to an individual, or when assigned through an escalation rule with personal chat enabled and set to follow personal preferences**.
50
-
- When configuring IM applications like Dingtalk, WeCom, or Feishu/Lark, you need to first associate the application to receive corresponding notifications.
56
+
- iOS users can download the app from the App Store, while Android users can download it from major app stores (HarmonyOS is not currently supported).
57
+
- After downloading, open the Flashduty APP and choose different login methods. Once logged in, your account will be linked.
58
+
- Regarding app settings: You need to enable system notifications, and in Do Not Disturb mode, you can allow notifications for urgent incidents.
0 commit comments