|
By Max Rozen
Chances are, you've heard one of the main promises of serverless compute: "you only pay for what you use". While convenient when starting a new project, once you start to get continuous usage on that compute, you start to realize you're paying a hefty premium for that convenience. If you're using AWS Lambda like I am, chances are that "for what you use" part isn't completely true either.
|
By Max Rozen
A quieter month this time around: you can now customize your status pages, there are additional overall statuses for status pages, and I fixed a few bugs.
|
By Max Rozen
This month I continued adding features to OnlineOrNot's status page functionality, while also taking the time to fix bugs, and add an integration for Pingdom.
|
By Max Rozen
If you remember the last update, I originally planned to ship quite a few features in June. Life and family had to take priority for me, so they didn't get done. Thankfully, I'm building OnlineOrNot for the extremely long term, so there's no rush to ship as fast as possible. A fair few things did get shipped though.
|
By Max Rozen
In May I mostly took the time to plan out the rest of the year, as well as one big feature to make OnlineOrNot's incident management more realistic.
|
By Max Rozen
In April I kept focusing on making Status Pages better than ever, and added a new on-call integration: incident.io.
|
By Max Rozen
March was a fun month for OnlineOrNot. I spoke to more customers than ever before, developed a long roadmap for OnlineOrNot's status page functionality (it's going to be an even better stand-alone product), heartbeat checks are going to support cron expressions, and more.
|
By Max Rozen
Incidents are a stressful time for your team: your service isn't working the way you expect and your customers/stakeholders want to know what's going on. The last thing you want to do is let your team improvise everything when it comes to responding to incidents. Google's own SRE book has great overall tips for incident management, part of which involves "develop(ing) and document(ing) your incident management procedures in advance", which this article dives into.
|
By Max Rozen
Over December and January I focused on OnlineOrNot's public API, making it possible to see what OnlineOrNot saw when it detected a failing uptime check, as well as fixing bugs and cleaning up tech debt across all of OnlineOrNot (it's getting faster and faster to release updates).
|
By Max Rozen
You might be thinking “building HTTP API docs from scratch? in 2024? wtf?”, and you’re probably right. After all redoc has been around since 2016, and there are hundreds of “generate beautiful documentation from your OpenAPI spec” startups around, some even use AI now. To be honest, I didn’t even know it was possible to do-it-yourself when I started looking into it.
- October 2024 (2)
- September 2024 (1)
- August 2024 (1)
- June 2024 (1)
- May 2024 (1)
- April 2024 (1)
- March 2024 (1)
- February 2024 (1)
- January 2024 (1)
- December 2023 (2)
- October 2023 (2)
- September 2023 (1)
- July 2023 (1)
- June 2023 (4)
- March 2023 (3)
- February 2023 (1)
- November 2022 (1)
- August 2022 (1)
- July 2022 (1)
- June 2022 (1)
- February 2022 (2)
- January 2022 (4)
- December 2021 (2)
- November 2021 (1)
- August 2021 (2)
- July 2021 (2)
- June 2021 (1)
- May 2021 (3)
- April 2021 (3)
- March 2021 (3)
- February 2021 (1)
OnlineOrNot monitors your website, letting you know instantly if anything goes wrong.
OnlineOrNot is an website monitoring service. In particular, it monitors whether your site is online, or not (hence the name). It allows you to continuously monitor any website or API server. It notifies you instantly in the case of any problems - whether that's a timeout, 4xx error, or 5xx error.
Monitor With Confidence:
- Configurable Alerts: You don't want alerts for sites that aren't really down for everyone. Configure retries, and how many minutes of downtime to wait before sending an alert.
- Fast Alerts: Getting alerts ages after your site goes down isn't great. We use email deliverability best-practices so your alerts get delivered, fast.
- Alerts where you need them: Get notified when your site goes down, and when it comes back via Email and Slack. Alerts via SMS and phone call coming soon!
- Text Search: Want to detect when your page stops showing certain text? OnlineOrNot can search your page for text to catch error pages that don't send error codes.
- Global Monitoring: Monitor from any one of 10 major cities around the world. Check out our supported regions.
- Bring the whole team: Monitoring is your whole team's job, not the responsibility of just one person. Bring your whole team at no extra cost.
Everything you need to be sure that your website is running smoothly.