Overview
The Location MTTR MTBF widget shows two figures, in hours, for the Locations and period you choose: MTTR (Mean Time To Repair) and MTBF (Mean Time Between Failures). It answers "how much operating time does a breakdown cost, and how long do we run between breakdowns?"
For what the metrics mean and how to act on them, see MTTR and MTBF — Mobaro's reliability metrics. For the same figures per Location, use the MTTR MTBF Details widget or the Location Jack Knife widget.
At a glance |
|
Who can do this | Super Users, or a Role with Dashboard Templates › Manage, add it. Viewers see data only for Locations they can see. |
Where | Dashboard Templates › a template › Add a widget › Operational › Location MTTR MTBF |
Works on | Backend (web) |
Availability | All organizations. Uptime and Downtimes are recorded for Locations with Enable Operational Logging. |
What it shows
Figure | How it's calculated |
MTTR | The total recorded duration of the Downtimes that started in the period, divided by their number. |
MTBF | The uptime in the period divided by the number of Downtimes that started in it. |
Both figures cover all the selected Locations together; they aren't an average of per-Location figures. They show in hours (h) with two decimals, or whole hours above 99, so 0.75 h is 45 minutes. A dash (-) means there's nothing to calculate: no Downtimes started in the period; for MTTR, none has a duration yet; for MTBF, no uptime period has ended.
Downtimes: every Downtime that started in the period, whatever its state (Open, Blocking, Resolved or Closed). Deleted Downtimes don't count. A Downtime's duration is the Actual Downtime confirmed when it's closed.
Uptime: the time the Locations were open, from uptime periods that have ended, cut to the period.
Locations: every Location you can see that matches the Locations filter. Deleted Locations don't count.
⚠️ Heads-up: Downtimes that aren't closed yet have no duration but still count, so they pull MTTR down. Uptime only counts once an uptime period has ended: a Location that's open right now adds none of its current opening to MTBF (known issue). Close Downtimes promptly, and report on periods that have ended.
Settings and filters
Setting | What it does | Default |
Time range (button at the top left) | The period. A Downtime counts in the period it started. Options: Today, Yesterday, Last week, Current week, Current month, Last a number of Days, Weeks or Months, Specific month or Custom Time Range. No All Time. | Last 12 months |
Category | Count only Downtimes with the selected Downtime Categories; only shown if your organization has them. Uptime isn't filtered, so MTBF becomes time between failures of that kind. Known issue: a Downtime with more than one of the selected categories is currently counted once for each. | None: all Downtimes |
Locations | Pick Locations or Location Groups and click Apply Filter. The bin icon clears the selection. | None: every Location you can see |
Title | Click the widget's title to rename it; the cross resets it. | Location MTTR MTBF |
Reading the widget
Click MTTR or MTBF to open the details: a table with one row per Location and the columns Location, Uptime, Downtime, Downtime Count, MTTR and MTBF, in hours and minutes. Click a column header to sort. It's the same table as the MTTR MTBF Details widget. When nothing matches, the dialog shows No data is available for this widget. Please try changing your filtering.
Super Users and Users with Locations › View see every Location; other Users see the Locations they're a member of, directly or through a User Group or Location Group. Two people can therefore see different figures on the same dashboard. See How access works in Mobaro.
The widget reloads with the dashboard every 10 minutes (there's no setting to turn this off) and when you change a filter; times are in the dashboard's time zone. Bulk filtering and the Location Switcher can change its filters, and a Personal filter keeps your changes. See How to use the Dashboard.
Best practices
Close Downtimes promptly and check the Actual Downtime before you confirm it.
Report on periods that have ended, such as Last week or a Specific month, so open Downtimes and open uptime periods don't skew the figures.
Use Downtime Categories consistently, and filter one category at a time for exact counts.
Frequently asked questions
What does MTTR stand for?
Mean Time To Repair: the total recorded duration of the Downtimes that started in the period, divided by their number. Its partner, MTBF (Mean Time Between Failures), is the uptime in the period divided by the number of Downtimes that started in it. See MTTR and MTBF.
Recorded downtime isn't pulling through to MTTR and MTBF. Why?
Check the widget's time range (Downtimes count by start time), its Category and Locations filters, and that you can see the Location. A Downtime that isn't closed counts but has no duration, so it adds nothing to the repair time.
How long does it take on average to resolve a downtime?
That's MTTR. It averages the recorded duration (Actual Downtime) of the Downtimes that started in the period, not the clock time from fault to fix. Click MTTR to see it per Location.
Why don't the numbers match the Location Operational History widget?
That widget counts only closed Downtimes; this one counts every Downtime that started in the period, whatever its state. Close open Downtimes and compare the same period and Locations. See Location Operational History widget.