> Projects_

Sentinel started life as an internal plugin for JPSNT.

As JPSNT grew, basic error logging stopped being useful. The site was no longer failing in obvious ways. Problems showed up as patterns instead. Repeated warnings. Memory usage creeping up over time. Hooks firing more than once. Requests that were fine most of the time and slow at exactly the wrong moment.

Debugging became reactive. Something would break, and then time would be spent trying to reconstruct what led up to it using partial logs and guesswork. The information needed to understand the problem usually existed, but it was scattered or missing when it mattered.

The original goal was not to build a monitoring product. It was to answer simple questions consistently. What happened. When it started. Whether it was new or recurring. Whether something changed shortly before.

As the internal tooling expanded to include better error categorisation, request context, memory tracking, and batch logging to reduce overhead, it became clear the system being built was not specific to JPSNT. The same failure patterns showed up across most WordPress projects, especially those maintained by one person or a small team.

Sentinel was split out into its own plugin once it became obvious it was solving a wider problem. Sentinel+ exists as the extended version of that system, focused on providing useful signals early, without adding noise or operational complexity.