- random clients on the Internet poking around at stuff, which you have no control over and causes no harm so should not alert
- an error in the links or code of the pages you ship to clients, which will cause a consistent degraded user experience and you should be notified about.
In practice, the best way to solve this I'm aware of is not via observation of server-emitted 404s at all... It's via a back-channel for clients to report errors (possibly authenticated, so randos on the web can't fudge your stats) and then tie alerting to that back channel. So you don't track 404s to /foo, but you do alert on your clients screaming at you that they got a 404 trying to access /foooo.
Of course, this solution requires your end-users to enable JavaScript.