> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flashcat.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Insights

> Use insights for data analysis, with statistics and analysis of incident data across multiple dimensions such as channels, teams, and individuals. Supports data download and export to enable data-driven business growth

<Tip>**Plan requirement**: This feature requires an On-call Standard or higher subscription. [Learn more](https://flashcat.cloud/flashduty/price/)</Tip>

## Key Features

<CardGroup cols={2}>
  <Card title="Multi-dimensional Analysis" icon="chart-pie">
    Expand from global and time dimensions to viewing by team, channel, individual, and other dimensions for a comprehensive understanding of team operations efficiency
  </Card>

  <Card title="Flexible Drill-down" icon="magnifying-glass-chart">
    Support drilling down from the global view to sub-dimensions for in-depth metric analysis and quick issue identification
  </Card>

  <Card title="Data Comparison" icon="code-compare">
    Compare data across different dimensions to discover differences and areas for improvement between teams
  </Card>

  <Card title="Data Export" icon="file-export">
    Support exporting data to CSV files for further data analysis and report generation
  </Card>
</CardGroup>

<Frame>
  <img src="https://download.flashcat.cloud/flashduty/doc/zh/fd/insight-2.png" alt="Insights Dashboard Interface" />
</Frame>

## Filter Conditions

When customizing filter conditions, the system remembers your selections. Even after refreshing the page, selected conditions are retained, but current user's operations do not affect other users.

| Filter        | Description                                                                                                                                                |
| :------------ | :--------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Team          | Select team names to query, supports multiple selection. Dashboard data updates based on selected teams                                                    |
| Channel       | Select channel names to query, supports multiple selection. Dashboard data updates based on selected channels                                              |
| Severity      | Select severity levels to query, supports multiple selection. Dashboard data updates based on selected severity levels                                     |
| Time Range    | Select time range to query. Supports this week, last two weeks, this month, last month, and custom time ranges, but only up to the last **1 year** of data |
| Data Interval | Supports day, week, and month dimensions. Defaults to hourly queries, but when time range exceeds 31 days, daily preview is not available                  |
| Sorting       | Team, channel, and individual dimension dashboards support ascending and descending order. Defaults to showing TOP 10 data; expand to show more            |

## Time Period Segmentation

When performing 24-hour on-call, to distinguish the different impacts on team members at different times, we divide time into three periods:

| Period      | Time Range                                    | Description                                                                      |
| :---------- | :-------------------------------------------- | :------------------------------------------------------------------------------- |
| Work hours  | Monday-Friday 8am-7pm                         | Prime working hours for the team                                                 |
| Rest hours  | Monday-Friday 7pm-11pm, Non-workdays 8am-11pm | Team members' rest or leisure time                                               |
| Sleep hours | Every day 11pm-8am                            | Interruptions during this period significantly impact team members' rest quality |

<Frame>
  <img src="https://download.flashcat.cloud/flashduty/doc/zh/fd/insight-1.png" alt="Time Period Segmentation Diagram" />
</Frame>

## Metric Definitions

<Note>
  Converged incidents do not trigger notifications, as they are typically defined as ignorable incidents. Therefore, all metrics exclude converged incidents.
</Note>

| Metric          | Description                                                                                                                                                                                                                                             |
| :-------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Incidents       | Number of incidents generated, excluding converged incidents                                                                                                                                                                                            |
| MTTA            | Mean time to acknowledge an incident (acknowledgment time minus incident trigger time). Incidents without acknowledgment are not included in the calculation                                                                                            |
| MTTR            | Mean time to resolve an incident (incident close time minus incident trigger time). Individual metrics do not include MTTR                                                                                                                              |
| Response Rate   | Response rate calculation formula: Response Rate = (Acknowledged Incidents / Total Incidents) × 100%                                                                                                                                                    |
| Response Effort | Total time responders spend handling incidents. Calculated by summing the time between incident acknowledgment and resolution for each member, providing a rough estimate of actual time invested in incident response                                  |
| Interruptions   | Only counts assignment notifications via SMS, voice calls, and app push. Multiple channel notifications to the same responder simultaneously count as one interruption. Notifications within 1 minute of the previous one do not count as interruptions |

<AccordionGroup>
  <Accordion title="About MTTR">
    When calculating Mean Time To Resolve (MTTR), the system cannot precisely determine whether an incident was resolved due to personnel intervention. Therefore, individual MTTR data is not included when calculating overall MTTR.

    Incident resolution may involve various scenarios:

    * Automatic recovery triggered by automatic alerts
    * Manual closure by personnel
    * Automatic system timeout closure
    * Multiple members participating in handling the same incident

    To ensure MTTR accuracy, the system focuses on the total time from incident occurrence to resolution, rather than evaluating individual member contributions.
  </Accordion>

  <Accordion title="About Data Latency">
    Since the system needs time to calculate data, there may be approximately one hour of delay when querying current data.
  </Accordion>
</AccordionGroup>

## Alert TOP

The global dimension allows viewing TOP 20 data for alert check items and alert resources:

| Dimension        | Description                                                                     | Recommendation                                |
| :--------------- | :------------------------------------------------------------------------------ | :-------------------------------------------- |
| Alert Check Item | Aggregate and sort alert events by check item (from the alert's `check` label)  | Adjust frequently occurring alert check items |
| Alert Resource   | Aggregate and sort alert events by resource (from the alert's `resource` label) | Optimize frequently occurring alert resources |

## Data Download and Export

<Tabs>
  <Tab title="Data Download">
    All dimensions support downloading dashboards in PDF format for further data analysis and report generation.

    <Frame>
      <img src="https://download.flashcat.cloud/flashduty/doc/zh/fd/insight-4.png" alt="Data Download Diagram" />
    </Frame>
  </Tab>

  <Tab title="Data Export">
    Export incident list data in CSV format. Supports exporting incident list, team, channel, and individual dimension data, but exported data may not match displayed fields.

    <Frame>
      <img src="https://download.flashcat.cloud/flashduty/doc/zh/fd/insight-5.png" alt="Data Export Diagram" />
    </Frame>
  </Tab>
</Tabs>

### Export Limitations

<Warning>
  * Incident list exports do not include Labels data. For more detailed data, we recommend querying via the [Incident List API](/en/api-reference/on-call/incidents/incident-list)
  * Maximum data list query and export is 10,000 records. For more data, we recommend exporting in time segments
</Warning>

## Usage Statistics

In addition to the insights dashboard, Flashduty On-call provides a **Usage Statistics** page to view overall resource usage trends. Usage statistics include charts for the following dimensions:

| Dimension              | Description                                                              |
| :--------------------- | :----------------------------------------------------------------------- |
| **Notification Count** | Trends of notification volume sent through various notification channels |
| **Incident Count**     | Trends of incident creation volume                                       |
| **Change Count**       | Trends of change event volume                                            |

Usage statistics help you understand overall platform usage for capacity planning and cost assessment.

## FAQ

<AccordionGroup>
  <Accordion title="How can I query older data?">
    Currently, insights only supports querying the last 1 year (depending on your plan's data retention period) of data. For older data, use the [API Query](/en/api-reference/on-call/analytics/insight-incident-list).
  </Accordion>

  <Accordion title="Why can't I view data at daily granularity when the time range exceeds 31 days?">
    The dashboard line chart supports a maximum of 31 data points, so when the query time range exceeds 31 days, daily granularity viewing is not available.
  </Accordion>
</AccordionGroup>

## Related Topics

<CardGroup cols={2}>
  <Card title="What is an Incident" icon="circle-exclamation" href="/en/on-call/incident/what-is-incident">
    Learn about basic incident concepts and lifecycle
  </Card>

  <Card title="Search and View Incidents" icon="magnifying-glass" href="/en/on-call/incident/search-view-incident">
    Master incident list and details page usage
  </Card>
</CardGroup>