alive365: Monitor Logins, Checkouts, and Uptime
Resumo
Pixel shares a look at alive365, an uptime monitoring service that checks websites and APIs with HTTP requests and browser journeys for login or checkout flows. The announcement explains scheduled checks, incident tracking, recovery confirmation after five successes, and daily email or webhook reports—helpful details for small teams keeping services reliable.
DEV Community
alive365: An Uptime Monitor That Checks Past the Login Page
A homepage can return 200 while nobody can log in. A plain uptime check will report that site as healthy. alive365 is the uptime monitoring SaaS we build at EarthLink Network. It calls your sites and APIs on a schedule and runs a real browser through the login or checkout steps, so the "the page loads but nothing works" kind of outage shows up too. alive365 is not open for sign-up yet. This post shows what it does and who it is for, screen by screen, using our development environment; every target in it is a demo. The short version alive365 checks from the outside, on a schedule, that your site and API are up. There are two kinds of checks: a browser check that replays a login or checkout in up to 50 steps, and an HTTP check that calls a URL (it can sign in first). An outage becomes one incident, listed under "Incidents" in the dashboard. Repeated failures are added to it instead of opening new ones, and recovery is confirmed after five successes in a row. A daily report can go to email or a webhook (Slack, for example) every morning. It fits small teams that run their own site, shop or SaaS with no one on monitoring duty. If you want to try it, contact us (end of section 9). 1. The monitor list and the two kinds of checks The Monitors page lists every check: its type (HTTP or BROWSER), the URL, and how often it runs (Interval). "New Monitor" asks for the type. Two are available: HTTP Request calls a URL with GET or POST and checks that the status code is the one you expect, such as 200. Use it for API health endpoints and for pages that should open. Browser Journey drives a real browser through a flow and checks that it reaches the end. More on this in section 2. Intervals are 1, 3, 5, 10, 15, 30 or 60 minutes. 2. Browser checks for login and checkout A 200 from the homepage does not tell you that the login button works or that the cart opens. A browser check does. You list the steps a customer takes, and alive365 runs them in order in a real browser (Chromium, driven by Playwright). The steps are built in the Journey Builder. There are six step types: Navigate opens a URL. Type fills in a field. Click presses a button or link. Wait waits for a set time or until an element appears. Assert checks that an element is on the page. Screenshot captures the page at that point. One journey can have up to 50 steps. If a step is missing its URL or selector, the screen shows "Journey is not valid" and will not move on. A password does not go into the step itself; the step can point to a stored secret with {{secrets.}}. The browser only starts when a check runs. Nothing sits running in between. 3. HTTP checks behind a login Member pages and admin APIs need a login. The Authentication tab of an HTTP check signs in before the request. The five options: None: no login. Basic Auth: a user name and password. Bearer Token: a token, as most APIs use. API Key: a key sent in a header you name, such as X-API-Key. Form Login: posts the user name and password to the login form, keeps the session, then checks the target page. Passwords and tokens are encrypted before they are stored, and neither the screen nor the API ever returns them afterwards. "Login URL" can be left blank. alive365 then opens the target page without logging in and uses the page it is redirected to as the login page. The encryption keys are separate for each environment and kept in AWS SSM Parameter Store. The stored value is decrypted only when a check runs. Form Login is for ordinary login forms. As the screen says, sites built as single-page apps or protected by MFA cannot be logged into this way, and alive365 points you to a browser check instead. 4. What to check, and how often: an online shop For a small online shop, a setup could look like this: Homepage: HTTP check, every minute. The fastest way to learn the site itself is down. Order API: HTTP check, every minute. Pages can load while order processing alone has stopped. Member pages: HTTP check with Form Login,...

Powered by Readybot.io