官方说明3 个来源MCP 服务3 天前
nicofains1/agentwatch
📇 🏠 - Multi-agent observability for cascade failure detection, fleet-wide heartbeat monitoring, and forensic…
在 GitHub 查看 ↗直链 · 无中转页
官方说明📇 🏠 - Multi-agent observability for cascade failure detection, fleet-wide heartbeat monitoring, and forensic replay. Works as an npm library or MCP server.
- 来源明细
- 收录自 rohitg00/awesome-devops-mcp-servers 榜单（我们从中收集的条目之一） · 条目类型：MCP 服务
- 收录与活跃
- 收录于 2026-10-14 · 最近见到 2026-10-16 · 共见到 4 次 · 被 3 个来源列出
- 评分构成
- 综合分 303 · 3 个来源 · mcp
常见问题（答案都来自我们的记录）
怎么安装？
我们【没有】从该仓库取到安装命令（我们的 install 覆盖率只有约 4%）。请看它的 README 或 releases 页。
它适合谁 / 用来做什么？
我们把它归在这些标签下: MCP 服务。标签来自条目自身，不是我们强加的分类。
谁维护它、还在更新吗？
我们收录于 2026-10-14；最近见到 2026-10-16。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。
第三方质量标记
agentwatch
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
Your agent swarm crashed at 2am. You have logs from 10 agents and no idea which one started the cascade. AgentWatch tells you.
It tracks heartbeats, links actions across agents, walks backward from any failure to the root cause, and replays the full sequence. Works with any agent framework (CrewAI, AutoGen, LangGraph, PocketFlow, custom). Stores everything in a local SQLite file.
Early stage. Issues and feedback welcome: https://github.com/nicofains1/agentwatch/issues
---
See it in action
No install needed:
This seeds a 5-agent fleet, triggers a cascade failure, and shows you the full trace:
---
Install
Requires Node 18+. Uses better-sqlite3 (native bindings, no external database needed).
---
Quick start
---
What it does
**Heartbeats** - Each agent calls aw.report(name, status) on a schedule. AgentWatch tracks health over time and marks agents as stale or offline based on configurable thresholds.
**Cross-agent tracing** - Actions are linked by trace ID and optional parent event ID. When agent-c fails because agent-b sent bad data that came from agent-a, the full chain is queryable.
**Cascade detection** - correlate(failureEventId) walks backward from any failure to the root cause, returning the full chain with timing and output at each step.
**Alert de-duplication** - The same alert type from the same agent within a time window collapses into one entry with an incrementing count. Severity auto-escalates: info (1x) -> warning (3x) -> critical (10x).
**Forensic replay** - replay(traceId) returns all cascade chains within a trace. Useful for post-mortem analysis when a single trace touched multiple agents.
**OpenTelemetry export** - Export traces as OTEL spans (GenAI semantic conventions). Works with Jaeger, Grafana, or any OTEL-compatible backend. Requires optional peer deps.
---
CLI
Set AGENTWATCH_DB to point to your database file. Default: agentwatch.db in the current directory.
---
MCP server
AgentWatch runs as an MCP server. Add it to your Claude Code or Cursor config:
**Claude Code** (~/.claude/claude_desktop_config.json or .claude/settings.json):
**Cursor** (.cursor/mcp.json):
This exposes 13 tools: agentwatch_dashboard, agentwatch_report_heartbeat, agentwatch_trace, agentwatch_cascade, agentwatch_replay, agentwatch_get_alerts, agentwatch_get_failures, agentwatch_get_trace, agentwatch_fleet_health, agentwatch_create_trace_id, agentwatch_alert, agentwatch_resolve_alert, agentwatch_dashboard_text.
It tracks heartbeats, links actions across agents, walks backward from any failure to the root cause, and replays the full sequence. Works with any agent framework (CrewAI, AutoGen, LangGraph, PocketFlow, custom). Stores everything in a local SQLite file.
Early stage. Issues and feedback welcome: https://github.com/nicofains1/agentwatch/issues
---
See it in action
No install needed:
This seeds a 5-agent fleet, triggers a cascade failure, and shows you the full trace:
---
Install
Requires Node 18+. Uses better-sqlite3 (native bindings, no external database needed).
---
Quick start
---
What it does
**Heartbeats** - Each agent calls aw.report(name, status) on a schedule. AgentWatch tracks health over time and marks agents as stale or offline based on configurable thresholds.
**Cross-agent tracing** - Actions are linked by trace ID and optional parent event ID. When agent-c fails because agent-b sent bad data that came from agent-a, the full chain is queryable.
**Cascade detection** - correlate(failureEventId) walks backward from any failure to the root cause, returning the full chain with timing and output at each step.
**Alert de-duplication** - The same alert type from the same agent within a time window collapses into one entry with an incrementing count. Severity auto-escalates: info (1x) -> warning (3x) -> critical (10x).
**Forensic replay** - replay(traceId) returns all cascade chains within a trace. Useful for post-mortem analysis when a single trace touched multiple agents.
**OpenTelemetry export** - Export traces as OTEL spans (GenAI semantic conventions). Works with Jaeger, Grafana, or any OTEL-compatible backend. Requires optional peer deps.
---
CLI
Set AGENTWATCH_DB to point to your database file. Default: agentwatch.db in the current directory.
---
MCP server
AgentWatch runs as an MCP server. Add it to your Claude Code or Cursor config:
**Claude Code** (~/.claude/claude_desktop_config.json or .claude/settings.json):
**Cursor** (.cursor/mcp.json):
This exposes 13 tools: agentwatch_dashboard, agentwatch_report_heartbeat, agentwatch_trace, agentwatch_cascade, agentwatch_replay, agentwatch_get_alerts, agentwatch_get_failures, agentwatch_get_trace, agentwatch_fleet_health, agentwatch_create_trace_id, agentwatch_alert, agentwatch_resolve_alert, agentwatch_dashboard_text.
- 来源
- awesome · https://github.com/nicofains1/agentwatch
- 按领域浏览
- MCP 服务
- 收录于
- 昨天
更多MCP 服务
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。