Keeping a headless browser healthy on a small server
How WhoozGot keeps its headless browser healthy on a small server. Why it records how every page was read.
What I tried
Some menus are built with JavaScript, so WhoozGot renders them in a headless browser on a small server.
Why I chose differently
Each render leaves a little behind. Over hundreds of pages that adds up to memory the browser itself needs. I noticed because one figure stopped moving while others carried on.
What I chose
Housekeeping now runs regularly and each render works on disk. The worker records how each document was read. That record matters most, because it shows directly whether rendering is working.
The principle
If a metric cannot move when the system misbehaves, it is not monitoring anything.
- Chromium
- Linux
- tmpfs
- Monitoring