openclaw - 💡(How to fix) Fix Community tool: openclaw-watchdog (cross-platform self-healer) [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#72559Fetched 2026-04-28 06:34:31
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Participants
RAW_BUFFERClick to expand / collapse

Hey - built a community watchdog tool that goes a fair bit further than the reference implementation in the workspace tools folder.

Repo: https://github.com/simonlpaige/openclaw-watchdog

What it does:

  • Monitors the gateway HTTP health endpoint and restarts it when it goes down
  • Works on Windows, macOS, and Linux (uses Node's os module and fs.statfs, no PowerShell)
  • Circuit breaker: won't restart more than 3 times in 15 minutes, then backs off and alerts
  • Fix ladder: soft wait first, then gateway restart, then kill-port-and-start, then alert
  • Tracks incidents in a JSONL log and summarizes top patterns every 100 incidents
  • Self-tunes memory and disk alert thresholds based on whether they predicted real outages (purely empirical - just arithmetic on false positive rates)
  • Notification hooks for Telegram, Discord, Slack, and generic POST webhooks
  • Config file at ~/.openclaw-watchdog/config.json with documented keys

CLI: \
openclaw-watchdog check # one-shot health check openclaw-watchdog fix # check and auto-heal openclaw-watchdog watch # daemon mode openclaw-watchdog status # JSON status report openclaw-watchdog patterns # learned incident patterns openclaw-watchdog reset # clear circuit breaker after manual fix \\

Zero external deps. Pure Node stdlib. Node 18+. npm install -g works.

Would it make sense to link this from the docs, or would you want to pull it into a community/ folder in this repo? Happy to adjust anything that would make it fit better.

extent analysis

TL;DR

Consider adding the community watchdog tool to the documentation or a community folder in the repository to increase visibility and adoption.

Guidance

  • Review the tool's functionality and ensure it aligns with the project's goals and standards.
  • Evaluate the benefits of including the tool in the repository, such as increased visibility and maintainability.
  • Discuss with the community and maintainers to determine the best approach for integrating the tool, whether through documentation or a community folder.
  • Consider creating a pull request to add the tool to the repository, following the project's contribution guidelines.

Example

No code snippet is provided as it is not necessary for this issue.

Notes

The decision to add the tool to the repository or documentation depends on the project's specific needs and goals. It is essential to consider factors such as maintenance, support, and potential conflicts with existing tools.

Recommendation

Apply workaround: Add the tool to the documentation, allowing users to access and utilize it while maintaining the repository's integrity and avoiding potential conflicts. This approach enables the community to benefit from the tool without introducing unnecessary complexity to the repository.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING