Beamfar

Alerts and checks

Why did I get no alert when one region saw an error?

Short answer

A site is called down only when two regions agree. If one region sees a failure and another does not, the app shows a regional issue and sends no alert, because a failure seen from one place is often a problem on the way to the site rather than the site itself.

Where you see it

  • On the portfolio and on the site’s page, regions that disagree are shown as a regional issue, not as down.
  • In the monthly report, regional issues are listed apart. The report says they are not counted as downtime.
  • A site with no valid measurement from any region is shown as data unavailable. It is never counted as up and never shown as zero.

What is proven and what is not

The rule is built into the checks and covered by automated tests. What Beamfar does not have yet is a long record of its regions on two separate real servers. Until it has, treat how the regions behave between real locations as designed, not proven. You cannot choose the regions of a check.

Other rules

The two-region rule is for outages. Other findings have rules of their own, and the incident page names the rule that opened each incident. A scheduled task is confirmed by the ping receiver, not by two regions (how).

Still stuck?

Tell us what you tried and what you saw. A person reads it and answers by e-mail.

Beamfar is in its soft launch: the 14-day trial is free and needs no card, and paid plans open soon; their prices may change before then. These answers describe what the app does today.