Sign In

Incident Volume Report

The Incident Volume report helps you understand incident patterns and frequency. Use this data to identify trends, peak times, and areas needing attention.

Report Sections

Overall Statistics

The report shows key incident metrics:

  • Total Incidents - All incidents in the period
  • New Incidents - Incidents created during the period
  • Resolved Incidents - Incidents resolved during the period

A line chart displays incident counts by day, showing:

  • New incidents created each day
  • Patterns over the 30-day period
  • Spikes or unusual activity

Heat Map

The heat map visualization shows incident distribution by:

  • Hour of day (vertical axis)
  • Day of week (horizontal axis)
  • Color intensity indicating incident count

Use this to identify:

  • Peak incident times
  • Patterns by day of week
  • Quiet periods for maintenance

Severity Breakdown

View incidents grouped by severity level:

  • SEV-1 (Critical)
  • SEV-2 (High)
  • SEV-3 (Medium)
  • SEV-4 (Low)

This helps understand the distribution and impact of incidents.

Status Distribution

See the current status of all incidents:

  • Open
  • Acknowledged
  • Resolved
  • Other custom statuses

Using the Report

Reading the Heat Map

The heat map uses color intensity to show incident concentration:

  • Darker colors = More incidents
  • Lighter colors = Fewer incidents
  • White = No incidents

Common patterns to look for:

  • Business hours concentration
  • Weekend vs weekday differences
  • Overnight incident patterns

The daily trend chart helps you:

  • Spot increasing or decreasing patterns
  • Identify specific problem days
  • Correlate with deployments or changes
  • Plan capacity based on volume

Exporting Data

Click Export to download a CSV containing:

  • Daily incident counts
  • Hourly distribution data
  • Severity breakdowns
  • Status summaries

Best Practices

Regular Review

  • Check weekly for emerging patterns
  • Compare current month to previous
  • Look for seasonal trends
  • Monitor after major changes

Pattern Analysis

Common patterns and what they might indicate:

  • Monday spikes - Weekend issues discovered
  • Friday peaks - Pre-weekend deployments
  • Night incidents - Automated system issues
  • Lunch dips - Natural work patterns

Taking Action

Use insights to:

  • Schedule on-call coverage appropriately
  • Plan deployments during low-incident times
  • Investigate root causes of spikes
  • Adjust monitoring thresholds

Interpreting Results

Healthy Patterns

  • Consistent or decreasing volume
  • Most incidents during business hours (when staff available)
  • Low percentage of critical incidents
  • High resolution rate

Warning Signs

  • Increasing incident trends
  • Many overnight incidents
  • High percentage of critical severity
  • Low resolution rates