Skip to main content

[Software metrics] Mean Time Between Failure - MTBF

By
MTBF - Meantime between failure
In today post I would like to talk about a software metric that can give us information related to the quality of our product and how stable it is – Meantime Between Failure.
This metric measure the time interval between the moment when a failure was fixed (and the system is stable) until the moment when a new failure is detected. We could say that this metric measure the time interval when the system is up and running.
Using this metric, we can obtain to important information related to our system:
  • How stable our system is
  • When the next failure will occur

I think that the second point is pretty interesting, especially when we have a system in production. Theoretically, MTBF could tell to the operational and maintenance team when next fail over will have – in this way they can be prepared for it.
MTBF can be calculated in different ways, the most simple formulate for it is the sum of all the time intervals when the system didn’t had a failure divided by the numbers of failure.

In a real product, we expect to have issues open all the time, even if we don’t like this. Because of this we need to define what kind of failures we measure (for example the severity level of them). We should measure the MTBF for critical failures (system is down, clients cannot use application anymore and so on). In a normal product, this kind of failures I would expect to be counted when we would calculate the MTBF.
I calculated the MTBF for a web application that is hosted on Windows Azure from 2011. The MTBF for this web application is around 10 months. The cause of the failures that we had until now was caused by:
  • A Windows Azure Service was down and we didn't had a fail over solution for it
  • Client infrastructure was down and we our web application depended on that service

In this post we saw a software metric that can be used with success when we need to predict when the next time when we’ll have a failure is. This metric can be calculated very easily and can help us to understand how stable our system is.

I invite you to calculate this metric for your own system and see what values you get.
Labels:

Comments

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

By
After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(
Post a Comment
Read more

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

By
Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see
8 comments
Read more

Navigating Cloud Strategy after Azure Central US Region Outage

By
 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too
Post a Comment
Read more