GKGJ Kiminstatus-notes.hashnode.dev·Jun 30 · 5 min readHow Far Should Monitoring Go Beyond Detecting a Problem?Monitoring products are designed to tell us when something goes wrong. They send an alert when a website becomes unavailable, slows down, or starts returning errors. That part is fairly clear. What co00
GKGJ Kiminstatus-notes.hashnode.dev·Jun 29 · 4 min readMy Website Is Up. Why Do I Still Need Monitoring?The pages load. The buttons work. So why would you need website monitoring at all? We found ourselves asking the same question. If the website is already working, continuously checking its status can 00
GKGJ Kiminstatus-notes.hashnode.dev·Jun 17 · 2 min readURL Monitoring Looked Simple. Then I Looked Closer.At first, the challenge sounded simple. Could URL monitoring become easier and more useful? URL monitoring may look like a straightforward product. You enter a URL, check it regularly, and send an ale00
GKGJ Kiminstatus-notes.hashnode.dev·Jun 16 · 6 min readAfter Monitoring, What Should Users Do Next?The monitoring ran. The status was checked. A problem was found.But the user may still be stuck. So what should I do now? At first, it is easy to think of monitoring as “checking the status of a web00
GKGJ Kiminstatus-notes.hashnode.dev·Jun 15 · 7 min readWhere Non-Developers Get Lost in Website MonitoringIn the previous post, we wrote that whenever we think about website monitoring, we keep coming back to one standard: making it easy. That naturally leads to the next question. Where do users feel los00