watchdog

Monitor application logs for errors and generate JSON incident files with Telegram alerts.

3|2|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/fluxforgeai/ARTEMIS --skill watchdog-fluxforgeai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: watchdog
Source: https://github.com/fluxforgeai/ARTEMIS/tree/main/.claude/skills/watchdog
Command: npx skills add https://github.com/fluxforgeai/ARTEMIS --skill watchdog-fluxforgeai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides an autonomous background monitor that watches application logs for errors after a fix, creates structured incident files, de-duplicates repeated errors, and pushes timely Telegram alerts so teams can receive immediate notifications without keeping sessions open.

Core Features & Use Cases

  • Passive Background Monitoring: Runs as an independent bash daemon that polls logs every 60 seconds and survives the AI session lifecycle.
  • Incident Creation & Tagging: Writes JSON incident files and tags each incident as "fix-related" or "system" using fix-specific and system-wide regex patterns.
  • De-duplication & Status Surfacing: Avoids alert spam by hashing error signatures and writes a status JSON file for quick CLI or AI-driven checks.
  • Telegram Notifications: Sends different alert types (high-priority fix-related vs system warnings) directly to a configured Telegram chat.
  • Use Case: Start after deploying a retry-logic or upload fix to verify the patch in production; receive push alerts for regressions while you sleep.

Quick Start

Start the watchdog to monitor the backend container for the recent fix by invoking: /watchdog Monitor extraction after retry logic fix - watch for timeout errors

Frequently Asked Questions about watchdog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor application logs for errors with Telegram alerts?

To monitor application logs for errors with Telegram alerts, run an autonomous bash daemon that polls logs, tags incidents as system or fix-related, and sends push notifications directly to a configured Telegram chat.

How do I run a background monitoring process after deploying a fix?

Run a background monitoring process after deploying a fix by starting a bash daemon that polls logs every 60 seconds, de-duplicates repeated errors, and alerts you to regressions even after the session lifecycle ends.

Can I de-duplicate repeated application errors to avoid alert spam?

Yes, you can de-duplicate repeated application errors to avoid alert spam by hashing error signatures, which prevents duplicate notifications while still writing structured JSON incident files for each unique error.

What is the best way to verify a production fix without keeping a terminal session open?

The best way to verify a production fix without keeping a terminal session open is using an independent background bash daemon that continuously monitors container logs and sends push notifications for regressions.

Does the log watchdog support containerized backends?

Yes, the log watchdog supports containerized backends, allowing you to monitor application logs within containers for errors and receive immediate Telegram notifications for post-fix verification.

How do I check incident status without parsing raw application logs?

You can check incident status without parsing raw logs by reading a generated status JSON file that surfaces current monitoring state, allowing quick CLI or AI-driven checks for recent system or fix-related incidents.