The Performance MTTA (Mean Time to Acknowledge)/MTTR (Mean Time to Resolve) Report tells the story of your investment in VictorOps and the practice of DevOps. Track evolution and goals over time, and tell key stakeholders the story by relaying key metrics directly related to the cost of downtime.
By default, the MTTA and MTTR lines will be displayed in the graph view if incidents are present in a specific time period. Incidents are displayed in vertical columns to relay the aggregated incident number in a specific timeframe, while also displaying the individual incidents making up the time range. Hover over an incident to learn key metrics, and click an individual incident to get the granular information surrounding a specific data point. For the bucket averages, only the hover state is available.
Track both your organization and team’s MTTA/MTTR and incident metrics by leveraging the team filter. These are directly related to the associated team’s escalation policies.
Routing Key Filtering
Target specific or multiple routing keys to understand metrics around different components.
Add specific goals against MTTA and MTTR goals. Track these in the daily, weekly, and monthly bucketing increments.
Note: Goals are only saved on a user basis and not saved organization-wide.
Date Range and Bucketing
Aggregate MTTA and MTTR averages and incident volume by daily, weekly, and monthly buckets.
The table view adjusts to match the 100 most recent incidents associated with the selected segment filter. Click on a specific row to learn more about a specific incident, including its ACK/RES history, as well as the individual alert payload.
The data delivered in the CSV will reflect the date range and team segmenting designed in the setting views. Changing the segment by filters and date range bucketing will have no effect on the contents of the download.