Now

Dear Flashduty users,

Today, we officially launch the Flashduty mobile app! No matter where you are, you can control everything just like at your workstation.

Key Feature Highlights

1. Incident Management at Your Fingertips

• Full Mobile Workflow: Supports incident retrieval, detailed viewing, claiming, closing, escalating, and manual triggering, with deep optimization for mobile interaction, increasing key operation response speed by 40%.
• Multi-dimensional Information Aggregation: Incident timeline, handling records, and associated logs are centrally displayed to aid quick decision-making.

Scenario Value: What you can do at your workstation, you can do just as efficiently on your phone.

2. Critical Notifications, Never Miss a Beat

• iOS Critical Alerts: Based on Apple's official Critical Alerts protocol, breaks through Do Not Disturb mode restrictions, ensuring 100% delivery of severe alerts.
• Android System-level Channels: Supports system-level channels on all major Android manufacturers, allowing alerts to reach you even when the app is closed, preventing any misses.

Scenario Value: "Sleeping? In a meeting? Severe incidents will still notify you."

3. Voice Notifications, More Reliable

• Smart Whitelist Synchronization: Automatically adds Flashduty voice numbers to your phone's contacts, avoiding the risk of operator misinterception.

Take Action Now

1️⃣ Download and Install
👉 Go to the app store or click to download the Flashduty App (iOS/Android)
2️⃣ Permission Configuration Suggestions

• iOS users: Go to "Settings - Notifications" and enable Critical Alerts for Flashduty.
• All users: In the app, go to "Settings - Voice Notifications" and enable Sync Contacts permission.

Incidents don't wait, but you can always be one step ahead.

— The Flashduty Team

Since its launch, the Label Enrichment feature has been well received, especially for mapping labels using mapping data. However, managing mapping schemas and handling data uploads/downloads was previously only possible via the API, which posed a challenge for some users.

Now, we’ve added a Mapping Data Management feature to the console, allowing you to manage data easily through the UI—no API required!

📖 Learn more in our guide: Label Enrichment.

The new insights dashboard is now live! Thank you for your patience.

Improvement

Enhanced metric dimensions:

Metric aggregation dimensions have been expanded from global and time-based views to include team, channel, and individual perspectives. This allows you to drill down from the global view into various sub-dimensions for metric analysis.

Time period segmentation:

For 24/7 on-call coverage, treating each hour equally is not fair. In this new version, we've divided time into three segments, allowing you to analyze metrics across these dimensions:

• Work hours: Weekdays 8am~7pm
• Rest hours: Weekdays 7pm11pm, Non-workdays 8am11pm
• Sleep hours: Daily 11pm~8am

New workload metrics

When tracking team incident handling workload, looking at incident and alert counts alone is insufficient. We now support interruptions and response effort metrics.

• Interruptions: High-priority messages like SMS, phone calls, and app notifications are marked as interruptions, which can disrupt flow state and reduce team efficiency and satisfaction.
• Response effort: The sum of time between incident acknowledgment and resolution. This metric roughly estimates time spent on incident response.

Report download and data export

You can now print reports directly from the console for work summaries. Below each report, we provide detailed data that can be exported to CSV for further analysis.

Many users have reported that Flashduty's incident permission control was relatively weak. We have now made improvements to address this.

Improvement

1. Collaboration spaces now support access levels. When set to private, incident data is only accessible to team members and account administrators. Other members can only view incidents in private spaces through shared links.

2. The incident list now supports My Channels filtering. When selected, it only shows incidents from your spaces.

Best Practices for Data Isolation

We believe platform data isolation has three levels, in descending order of strictness. Each level has recommended implementation methods:

1. Personnel Isolation: For teams requiring separate personnel and encrypted information.

   Register multiple entities, with complete isolation of personnel and resources, managed separately.

2. Resource Isolation: When you don't want other members to see or handle your incidents.

   Set channel access level to private, preventing other members from seeing this channel and its incidents. Note that account administrators still have access.

3. Visual Experience: When you don't want to see alerts unrelated to you or your team.

   Keep the My Channels filter selected in the incident list. When you need to view all data, simply remove this filter.

We look forward to your feedback!

Many users have reported common issues with their internal alert configuration policies, such as missing alert information, numerous duplicate reports, and unclear severity levels. These problems have caused significant concerns for alert management personnel.

Today, we are officially launching the Alert Pipeline along with comprehensive improvements to the integration experience. You can now easily implement multiple operations including severity reset, title modification, filtering, and CMDB integration. Properly configured alert processing rules not only enhance alert readability but also effectively reduce alert noise and improve problem identification efficiency.

Highlights:

1. New Alert Pipeline: Supports various execution actions for more flexible and efficient alert handling.
2. Improved Label Enrichment and Alert Routing Configuration: Added a new right-side alert history panel for more intuitive rule debugging.

Try it out now!

We have comprehensively upgraded our on-call management system, with improvements in notifications, scheduling, and UI design.

New

1. Rotation notifications now support scheduled notifications, commonly used in scenarios where weekly on-call duties require daily reminders

2. Rotation notification content and style have been optimized to highlight current on-call information and show the next shift

3. Added date mask mode, where only selected dates participate in on-call duties, typically used for separate scheduling of weekday and weekend shifts

Improvement

1. On-call preview now includes a 2-week mode, similar to the 1-week view but showing more rotation information, especially useful for weekly on-call scenarios
2. In the calendar view of on-call preview, colors now follow rotations instead of rules, making it easier to track rotation members by color
3. Added highlight my on-call button to instantly highlight personal on-call schedules

1. Add alert integration for StateCloud

2. Add alert integration for Guance.

We now offer full English support across the console, help docs, and developer documentation so more users can use the product without language barriers.

What’s new

1. Browser language
   Every member can switch the console display language and pick the experience that fits them.

2. Notification language
   Account admins can set a default notification language under account settings. When incident notifications are sent, we render from your templates first; any content not covered by a template uses your notification language so messages stay consistent.

Try the new English experience today.

1. Brand new UI/UX design
2. Redesigned incident list with enhanced filtering options
3. Revamped incident details page with quick actions and custom operations
4. New incident creation feature with escalation rules and direct assignment
5. New dark mode support

Try it now!

We've launched a series of AIOps capabilities. Try them out now!

Intelligent Grouping

Introducing intelligent grouping mode for alerts. No manual rules needed - the system automatically identifies and groups similar alerts, reducing alert noise and helping you focus on critical events. Experience more efficient alert management and say goodbye to alert storms!

Rare Incidents

When a new incident doesn't match any incidents from the past 30 days in your channel, it's marked as a "Rare Incident." These incidents require extra attention as their system impact and resolution steps are unknown.

Past Incidents

The past incidents feature shows you similar past incidents, helping with root cause analysis and resolution recommendations to speed up incident response. Leverage rich historical data for better problem-solving insights!

Note: These features are available in Pro version only. Contact us if you'd like to upgrade.

Before Changes

• Silence/inhibit rules were matched during incident notification, intercepting notifications if matched
• Intercepted incidents generated interception records

After Changes

• Silence/inhibit rules are now matched during alert processing, preventing incident creation if matched
• Intercepted alerts will not trigger or merge into incidents
• You can choose to retain or drop intercepted alerts; retained alerts will generate interception records
• Intercepted alerts can be filtered in the console

Why This Change

When an incident aggregates multiple alerts, its labels may differ from the original alerts. Matching silence/inhibit rules at the incident level caused these issues:

1. Unwanted alerts couldn't be intercepted when merged into valid incidents
2. Valid alerts had notifications blocked when merged into silenced/inhibited incidents
3. When silence period ended, alerts belonging to an open silenced/inhibited incident still had notifications blocked
4. Intercepted incidents couldn't be filtered as interception status changed over time

Impact

• ❌ If you have active silence/inhibit rules:
  • Intercepted alerts will be retained with silence/inhibit reasons recorded but won't generate incidents
• ✅ If you have no active silence/inhibit rules:
  • No impact

1. Added confirmation dialog for custom actions in console to prevent accidental high-risk operations
2. New channels now appear at the top of the list
3. Enhanced incident creation page:
   • Added escalation rule selection
   • Added Markdown support for description
   • Added hints for schedule and responder selection
4. Added dynamic reset indicators in assignment history
5. Added video tutorial links near core features
6. Escalation rule updates:
   • Individual chat configurations now support empty channels for specific levels
   • Clarified loop notification text to avoid ambiguity
7. Removed current responder from reassignment options