More FMEA, Reports

It’s not Monday Night Football, it’s Monday Night FMEA. Well, I’m behind on documenting and need to work on a monday night. No biggie.

We’re doing the FMEA on the Report Generator now.

I wrote about this in an earlier post, but not from a FMEA perspective. One thing this architecture handles, that the previous one (with a new Container Instance for each Report Generation) is the issue that LibreOffice, by default, wants to auto update when there’s a new version available. We found that setting and turned it off, but when starting a new Instance that needed to update Libre Office, it would always fail to generate the report. This always on Instance would handle the update with a minor outage, but as I said, we turned that off.

The Container Instance exits unexpected.
The Container is configured with a Retry Policy, making it start over if it exits unexpected. If it fails while generating a report, that report will fail, and the User will need to try again.

The API is unresponsive/unavailable
The UI must show a message alerting the User there is a problem, but if this problem isn’t temporary (like perhaps caused by an unexpected exit with followed restart) actions will have to be taken.
We will monitor the API:s health endpoint to make sure it’s healthy, and restart the container if it’s not responsive.