![]() ![]() How does maintenance affect uptime?Įrrors that occur during a maintenance period are excluded from the uptime calculations, as long as the Maintenance type of the maintenance period is set to Disable monitoring entirely versus disabling notifications only.You don't quite supply enough information in your specific question (that is, "50RPM for 10 minutes with 39x23 with 10% hill") to provide a full answer in absolute terms but, if we assume you're riding a standard sized 700c bike there's enough information to make a good estimate in relative terms.įirst I'll give a short answer, then a rule of thumb that's easy to calculate and will put you within about 10%, then a longer more detailed answer. For the uptime percentage, use the formula uptime / (uptime + downtime), where uptime and downtime are given in seconds. If you want to exclude the unknown time from the uptime calculation, you can retrieve the total number of uptime and downtime seconds to do your own calculation. ![]() This has been a deliberate choice, because a lot of customers requested this. The formula for the uptime percentage is (uptime + unknown) / (uptime + downtime + unknown), where uptime, downtime, and unknown are given in seconds. When the uptime percentage is being calculated, please keep in mind that the total number of unknown seconds is included as well, and marked as uptime. When you pause a monitor, this time is being registered as ‘unknown’. Although your website is not actually down (but performing below your limits), it will show an uptime of less than 100% because the performance condition generated an error. Please keep in mind that all errors are taken into account when calculating downtime.įor example, when you define performance limits in the monitor’s error conditions and that limit is reached, an error is generated for that condition. Which errors contribute towards downtime? The time between the two measurements is being considered as up. The time between the two measurements is being considered as up, because it is not sure there is an actual error yet. A monitor is considered to be up only from the moment an OK indication is detected. The time between the two measurements is being considered as down. ![]() A monitor will be in error until an OK indication is detected. The time between the two measurements is being considered as down, because the monitor is still in an error condition. On a detailed level, the check results can change in these ways: However, all results can be broken down into the following situations: Of course, when continuously monitoring a service or server, there will be many check results in a row. The illustration below shows the possible sequences of check results and how the periods are considered. How does Uptrends mark the period between different monitor check results (OK, unconfirmed error, and confirmed error)? Is the time between an unconfirmed error and a confirmed error considered as up, or down? Go to a tile and open the three-dot menu to access the tile settings, including the different metrics you can select. The custom report tiles of type data list and data chart allow you to display the number of seconds of when your monitors were up or down. Tip: Play around with the data in your account to retrieve the actual number of seconds. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |