/ 目录 / 演练场 / PerformanceMonitor
← 全部服务器 ↗ GitHub
● 社区 erikdarlingdata ⚡ 即开即用

PerformanceMonitor

作者 erikdarlingdata · erikdarlingdata/PerformanceMonitor

Ask 'why is SQL Server slow?' and get wait stats, blocking chains, and plan analysis in plain English via Erik Darling's MCP.

PerformanceMonitor is Erik Darling's free SQL Server monitoring app with an embedded MCP server. It exposes 50+ read-only diagnostic tools (wait stats, blocking, deadlocks, plan analyzer, tempdb, memory) over localhost HTTP, letting an AI agent do the first-pass triage on a slow or stuck server.

▶ 观看演示 📦 安装 💡 使用场景

为什么要用

核心特性

实时演示

实际使用效果

performancemonitor.replay ▶ 就绪
0/0

安装

选择你的客户端

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "performancemonitor": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/erikdarlingdata/PerformanceMonitor"
      ],
      "_inferred": true
    }
  }
}

打开 Claude Desktop → Settings → Developer → Edit Config。保存后重启应用。

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "performancemonitor": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/erikdarlingdata/PerformanceMonitor"
      ],
      "_inferred": true
    }
  }
}

Cursor 使用与 Claude Desktop 相同的 mcpServers 格式。项目级配置优先于全局。

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "performancemonitor": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/erikdarlingdata/PerformanceMonitor"
      ],
      "_inferred": true
    }
  }
}

点击 Cline 侧栏中的 MCP Servers 图标，然后选 "Edit Configuration"。

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "performancemonitor": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/erikdarlingdata/PerformanceMonitor"
      ],
      "_inferred": true
    }
  }
}

格式与 Claude Desktop 相同。重启 Windsurf 生效。

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "performancemonitor",
      "command": "TODO",
      "args": [
        "See README: https://github.com/erikdarlingdata/PerformanceMonitor"
      ]
    }
  ]
}

Continue 使用服务器对象数组，而非映射。

~/.config/zed/settings.json
{
  "context_servers": {
    "performancemonitor": {
      "command": {
        "path": "TODO",
        "args": [
          "See README: https://github.com/erikdarlingdata/PerformanceMonitor"
        ]
      }
    }
  }
}

加入 context_servers。Zed 保存后热重载。

claude mcp add performancemonitor -- TODO 'See README: https://github.com/erikdarlingdata/PerformanceMonitor'

一行命令搞定。用 claude mcp list 验证，claude mcp remove 卸载。

使用场景

实战用法： PerformanceMonitor

Triage a slow SQL Server during an incident

👤 DBAs, SREs on call for database issues ⏱ ~5 min intermediate

何时使用： Users are reporting timeouts and you need to know what's blocking whom in the next 60 seconds.

前置条件
  • PerformanceMonitor app installed and connected to target server — Download from the GitHub releases and point it at your monitoring DB
  • Target login has VIEW SERVER STATE — GRANT VIEW SERVER STATE TO [monitor_login]
  • MCP registered with your client — claude mcp add --transport http --scope user sql-monitor http://localhost:5151/
步骤
  1. Get the health overview
    Run the health check — any red flags on waits, blocking, or memory pressure right now?✓ 已复制
    → Short list of elevated metrics
  2. Drill into the top offender
    If blocking is the top issue, show me the head blocker chain and the SQL text of the blocking session.✓ 已复制
    → Specific SPID + query text
  3. Get a recommendation
    Should I kill that SPID, wait it out, or is there a missing index that would prevent this? Be specific.✓ 已复制
    → One clear recommended action with rationale

结果： A diagnosed incident with a specific next action — kill, wait, index, or escalate — in under 5 minutes.

注意事项
  • Killing a blocker that was about to commit can cause more damage — Always ask for how long it's been running and whether it holds an open transaction before killing
  • Metrics from the monitoring DB lag the real server by the collector interval — For live view, use the 'current state' tools rather than aggregated history
搭配使用： sentry

Analyze a slow query plan with AI-assisted review

👤 Backend devs and DBAs tuning queries ⏱ ~15 min intermediate

何时使用： A query is slow and the plan is 200 operators — you don't want to read it manually.

步骤
  1. Fetch the plan
    Get the most recent plan for query hash 0xA1B2C3 and run the PlanAnalyzer against it.✓ 已复制
    → Plan + list of rule hits
  2. Explain the worst rule hit
    Explain the #1 rule hit in plain English — what's happening and why it's bad.✓ 已复制
    → 2-3 sentence explanation in English, not jargon
  3. Suggest a fix
    Suggest the smallest change to fix it: index, rewrite, or stats update. Estimate impact.✓ 已复制
    → Concrete DDL or rewrite

结果： A specific tuning action backed by both plan evidence and the PlanAnalyzer rule.

注意事项
  • Plan was cached under a different parameter sniffing path — Regenerate the plan with OPTION(RECOMPILE) before trusting its shape

Produce a weekly SQL Server health summary

👤 Database owners who want passive monitoring, not live on-call ⏱ ~20 min beginner

何时使用： Friday afternoon wrap-up; know before users tell you.

步骤
  1. Pull week-over-week stats
    Compare top waits and top queries this week vs last week. Flag anything that got materially worse.✓ 已复制
    → Deltas with percentages
  2. Draft a team-readable summary
    Write a one-page health summary — good/bad/ugly — for the engineering channel.✓ 已复制
    → Markdown post ready to paste

结果： A shareable weekly health post with concrete items to track next week.

搭配使用： sentry

组合

与其他 MCP 搭配，撬动十倍杠杆

performancemonitor + sentry

Sentry flags a timeout spike; cross-reference with SQL Server blocking at the same timestamp

Sentry event at 14:03 UTC shows SqlException. What was happening on the DB between 14:02 and 14:04 — any blocking or waits spikes?✓ 已复制
performancemonitor + github

Find the commit that introduced a slow query

Query hash 0xA1B2 started showing up in the top 10 on 2026-03-22. Find GitHub commits to the data-access layer around that date.✓ 已复制

工具

此 MCP 暴露的能力

工具输入参数何时调用成本
get_top_waits server_name?: str, hours_back?: int First stop in any triage — what is the server actually waiting on 1 SQL query on the monitoring DB
get_active_blocking server_name?: str Live blocking investigation 1 query
get_deadlocks server_name?: str, hours_back?: int Any time someone says 'we got a deadlock' 1 query
analyze_query_plan plan_handle: bin, or xml: str Tuning a specific slow query 1 query + 30 rule evaluations
get_memory_clerks server_name?: str Memory pressure investigation 1 query
get_tempdb_usage server_name?: str Tempdb filling up or spills in plans 1 query

成本与限制

运行它的成本

API 配额
No external quota; bounded by your monitoring DB capacity
每次调用 Token 数
Most tools return 200-2000 tokens; plan XML can be 10k+
费用
Free, open-source (Lite and Full editions)
提示
Lite edition is enough for most single-instance shops. Full adds cross-server monitoring.

安全

权限、密钥、影响范围

最小权限： VIEW SERVER STATE on the target instance
凭据存储： Monitoring DB connection string managed in the app's settings — stays on your box
数据出站： MCP binds to localhost only; no outbound calls from the MCP process
切勿授予： sysadmin or db_owner — VIEW SERVER STATE is enough

故障排查

常见错误与修复

Cannot connect to http://localhost:5151/

The app isn't running or MCP is disabled in Settings. Open the app, enable MCP, and confirm the port.

验证： curl http://localhost:5151/
Login failed for user

Monitoring DB credentials are wrong. Re-enter in the app and confirm VIEW SERVER STATE.

验证： sqlcmd -S <server> -U <user> -P <pwd> -Q 'SELECT 1'
Plan analyzer returns no findings on clearly slow query

Plan may not be in cache. Re-run the query with OPTION(RECOMPILE) and try again.

验证： SELECT plan_handle FROM sys.dm_exec_query_stats WHERE ...
Port 5151 already in use

Change the MCP port in Settings (range 1024-65535) and re-register with your client.

验证： netstat -an | grep 5151

替代方案

PerformanceMonitor 对比其他方案

替代方案何时用它替代权衡
sp_BlitzFirst / Brent Ozar scriptsYou prefer running T-SQL procs directly without an appNo MCP — you paste output into the chat yourself
SentryOne / Redgate SQL MonitorEnterprise environments that already have a commercial monitorPaid; most don't expose an MCP surface
postgres MCPYou're on Postgres, not SQL ServerDifferent DB entirely

更多

资源

📖 阅读 GitHub 上的官方 README

🐙 查看未解决的 issue

🔍 浏览全部 400+ MCP 服务器和 Skills