---
title: "Discussion on \"How Far Should Monitoring Go Beyond Detecting a Problem?\" | Hashnode"
description: "Discussion on \"How Far Should Monitoring Go Beyond Detecting a Problem?\". Should monitoring stop at detection—or help users figure out what to do next?"
url: "https://hashnode.com/posts/how-far-should-monitoring-go/6a436aec76b0de1a61ef5ff7"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [How Far Should Monitoring Go Beyond Detecting a Problem?](https://status-notes.hashnode.dev/how-far-should-monitoring-go?utm_source=hashnode&utm_medium=feed)

Should monitoring stop at detection—or help users figure out what to do next?

Jun 30 · 5 min read · status-notes.hashnode.dev  
Read the article

-   [#saas](https://hashnode.com/tag/saas)
-   [#monitoring](https://hashnode.com/tag/monitoring)
-   [#monitoring-tool](https://hashnode.com/tag/monitoring-tool)
-   [#ai](https://hashnode.com/tag/ai)
-   [#ai-agents](https://hashnode.com/tag/ai-agents)
-   [#uptime](https://hashnode.com/tag/uptime)
-   [#website](https://hashnode.com/tag/website)

## Written by

[GJ Kim](https://hashnode.com/@Unau)

@Unau · Seoul, South Korea

  
[View profile](https://hashnode.com/@Unau)

Field notes from Seoul on building website monitoring tools for small teams.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
