Failure Modes Effects Analysis - FMEA - Step One - throwing down failures.

We can make it better if we measure or analyze it. Let's analyze a small program in order to determine how it might fail and what we can do about it. 

We will break down a software program into smaller modules and look at how each phase or component might fail.  We will also look for silent failures or a lack of success metrics where something didn't occur at a time when there should have been some activity.

Sample System Under Analysis

Our example system is a data lake sink that 
  1. Reads streaming data 
  2. Validates the data
  3. Bundles the data into micro-batch sets
  4. Writes the data to a data lake. 
  5. Each lake write has a corresponding metrics push that updates our metrics store statistics and other features.

Video Walkthrough

In this video, we throw down as many failures as we can think of. We can worry about detection and remediation in a later phase



Worksheet Template

We will record the identified failure modes using a worksheet like this one.
ComponentFaultSeverityLikelyDetection RemediationTech or Business

  • Component: A subsystem or module we can tie the possible failure to
  • Fault: A specific failure.  We define these as specific as possible.
  • Detection: This describes how we would detect this problem. It could be automated or manual as part of some regular process. The worst situation is if your detection method is angry customers call us.
  • Remediation: A manual or automated process that can be used to fix the problem or park the problem for later work
  • Severity: The risk / damage that occurs with this type fo failure
  • Likelihood: Pretty much the frequency of this problem.  
Severity and Likelihood are used to determine the order for creating remediation processes.

Streaming Sink Worksheet

Faults identified during our 10 minute session.  The analysis moved from left to right through the components in the diagram.

We primarily went after the Faults in this section.  We took half-hearted attempts at Remediation and detection.

You can see a couple Ingestion lines in the middle of the sheet. That is because we discovered a couple additional ingestion problems while looking at something else. We can always re-order the fault list.  Don't stop to be orderly in the first pass. Just capture everything that comes to mind.

Missing functionality

Identified missing modules

We identified that the diagram above is missing a metrics collection box at the beginning of the flow. We want to capture metrics around the number of messages received to match up against the metrics bound to the data lake writer.

Vide

Created 2021/01/31
Title UPdated 2024/03

Comments

Post a Comment

Popular posts from this blog

Installing the RNDIS driver on Windows 11 to use USB Raspberry Pi as network attached

Image
I do a lot of my development and configuration via ssh into my Raspberry Pi Zero over the RNDIS connection. Some models of the Raspberry PIs can be configured with  gadget drivers  that let the Raspberry pi emulate different devices when plugged into computers via USB. My favorite gadget  is the network profile that makes a Raspberry Pi look like an RNDIS-attached network device.  All types of network services travel over an RNDIS device without knowing it is a USB hardware connection. A Raspberry Pi shows up as a Remote NDIS (RNDIS) device when you plug the Pi into a PC or Mac via a USB cable. The gadget  in the Windows Device Manager picture shows this RNDIS Gadget connectivity between a Windows machine and a Raspberry Pi. The Problem Windows 11 and Windows 10 no longer auto-installs the RNDIS driver that makes magic happen. Windows recognizes that the Raspberry Pi is some type of generic USB COM device. Manually running W indows Update  or  Update Driver  does  not  install the RNDI
Read more

Understanding your WSL2 RAM and swap - Changing the default 50%-25%

Image
The Windows Subsystem for Linux operates as a virtual machine that can dynamically grow the amount of RAM to a maximum set at startup time.  Microsoft sets a default maximum RAM available to 50% of the physical memory and a swap-space that is 1/4 of the maximum WSL RAM.  You can scale those numbers up or down to allocate more or less RAM to the Linux instance. The first drawing shows the default WSL memory and swap space sizing. The images below show a developer machine that is running a dev environment in WSL2 and Docker Desktop.  Docker Desktop has two of its own WSL modules that need to be accounted for.  You can see that the memory would actually be oversubscribed, 3 x 50% if every VM used its maximum memory.  The actual amount of memory used is significantly smaller allowing every piece to fit. Click to Enlarge The second drawing shows the memory allocation on my 64GB laptop. WSL Linux defaults to a maximum RAM size of 5
Read more

Almost PaaS Document Parsing with Tika and AWS Elastic Beanstalk

Image
The Apache Tika project provides a  library capable of parsing and extracting data and meta data from over 1000 file types.  Tika is available as a single jar file that can be included inside applications or as a deployable jar file that runs Tika as a standalone service. This blog describes deploying the Tika jar as an auto-scale service in Amazon AWS Elastic Beanstalk.  I selected Elastic Beanstalk because it supports jar based deployments without any real Infrastructure configuration. Elastic Beanstalk auto-scale should take care of scaling up and down for for the number of requests you get. Tika parses documents and extracts their text completely in memory. Tika was deployed for this blog using EC2 t2.micro instances available in the AWS free tier. t2.micro VMs are 1GB which means that you are restricted in document complexity and size. You would size your instances appropriately for your largest documents.   Preconditions An AWS account. AWS access id and secret key.
Read more