An alerting system earns its keep by what it does not send. Outpost evaluates alerts on the server, keeps one open alert per problem rather than one per check, and routes by rule so that the person who can fix something is the person who hears about it. This guide is for whoever is on the receiving end and whoever decides who that is.
Follow the how-to template.
Content is licensed CC BY 4.0. Code samples are MIT. Outpost and the Outpost mark are trademarks of Outpost Business Solutions, PBC and are not covered by either licence.