Overview
The Uptime Summary is a Location's record of when it was in operation: one uptime period for each time it was opened and closed. You open it from the Locations page. Use it to check that record, correct periods that were logged wrongly, and add a Downtime that wasn't logged when it happened.
Downtimes themselves aren't edited or closed here. You review, edit and close them in the Backend's Downtime list — see Using downtime in Mobaro.
At a glance |
|
Who can do this | View: anyone who can see the Location on the Locations page. Correct: Super Users, or a Role with Operations › Manage Downtime plus access to the Location. |
Where | Locations › select one Location › View Uptime Summary |
Works on | Backend (web). Uptime periods are also in the Public API. |
Availability | All organizations. Periods are only recorded for Locations with Enable Operational Logging. |
💡 Why this matters: Uptime periods are what MTBF, the operational history widgets and your uptime figures are measured against. A period left open by mistake, or a Downtime nobody logged, skews every figure built on it. The Uptime Summary is where you put the record right.
Open the Uptime Summary
1. Select the Location
In the Backend, go to Locations and select one Location in the list.
2. Click View Uptime Summary
Click View Uptime Summary in the toolbar. The Uptime Summary opens with the Location's name in its title.
What the Uptime Summary shows
Each row is one uptime period, with its Opened and Closed times and its Duration. The period the Location is in now shows Not yet closed. Use Time Zone at the bottom to change the time zone the times are shown in.
An alert icon on a row means The location was closed due to downtime. Click it to open that Downtime in the Downtime list, where you can edit or close it.
Correct an uptime period
You can only change periods that are closed. The period that's still open can't be edited until the Location is closed.
1. Select the period
Click the row of the closed uptime period you want to correct.
2. Click Edit Period
In Edit Uptime Period, change the start or end time and click Save. If the new times overlap other periods, they're listed under Overlapping uptimes, and you can't save until you fix the times.
To add a period that was never recorded, for example when a Location was opened but nobody switched it on in Mobaro, click Create Period, set the start and end, and click Save.
To remove a period recorded by mistake, select it and click Delete Period, then confirm with Yes.
🛑 Critical: Deleting an uptime period can't be undone. The time disappears from your uptime figures and MTBF. If only the times are wrong, use Edit Period instead.
Add a missed downtime
If a Location went down and nobody logged it, add the Downtime to the closed uptime period it happened in. A period can have only one Downtime.
1. Select the uptime period
Select the closed period during which the Location went down. It must not already have a Downtime.
2. Click Add downtime for this period
In Downtime Details, set Starts at and Ends at to when the interruption really happened, not when you're entering it. Add a Description, categories and attachments as needed.
3. Click Add
Mobaro ends the uptime period at Starts at and saves the Downtime as closed. If Ends at is before the period's original close, the rest of the period becomes a new uptime period starting at Ends at. Its duration is Ends at minus Starts at, not trimmed to opening hours. To change it later, use Edit Downtime in the Downtime list.
🛑 Critical: If you tick Create Assignment while adding a past Downtime, Mobaro creates a new high-priority Assignment now. If Red if one or more active high priority assignments exist is on, the Location becomes Not ready for operation until the Assignment is resolved. Leave it unticked when the problem has already been fixed.
Where this data goes
Uptime periods: the Location MTTR MTBF widget's MTBF, and the operational history widgets such as Operational History Details.
Downtimes: the Downtime list and the Downtime widgets. Widgets don't all treat unclosed Downtimes the same way; see Using downtime in Mobaro and Downtime on Dashboards.
For turning on Operational Logging and opening and closing Locations, see Utilizing Operational Logging.
Best practices
Correct the record the same day, while people still remember when the Location really opened, closed or went down.
Set Starts at and Ends at to the real times of the interruption, so durations and MTBF stay accurate.
Prefer Edit Period to Delete Period: a wrong time is easier to fix than a lost period.
Leave Create Assignment unticked when you backfill a Downtime that has already been dealt with.
Frequently asked questions
Can I log a downtime retroactively?
Yes. In the Uptime Summary, select the closed uptime period it happened in, click Add downtime for this period, set Starts at and Ends at, and click Add. The period can't already have a Downtime. No period that day? Create one first with Create Period.
Can I edit the times of a downtime that was already logged?
Yes, but not in the Uptime Summary. Open the Downtime in the Downtime list: set Actual Downtime when you close it, or use Edit Downtime once it's closed. See Using downtime in Mobaro.
Can I edit uptime like I do downtime?
Yes. In the Uptime Summary, select a closed uptime period and click Edit Period to change its times. For example, if a Location was marked closed when it was open, correct the periods on either side of the gap.
Someone can open and close locations but can't add a retroactive downtime. Why?
Correcting the Uptime Summary needs Operations › Manage Downtime (or Super User) and access to the Location. Opening and closing Locations doesn't need it. Without it, the toolbar buttons don't appear.
How can I see the total uptime for a ride over a season or a year?
Not in the Uptime Summary, which lists individual periods. Add the Operational History Details widget to a Dashboard and set its time range, or pull uptime periods through the Public API. See Utilizing Operational Logging.