Brummer MCP Server

--- sidebar_position: 2 --- # Intelligent Monitoring Brummer goes beyond simple log viewing with intelligent monitoring features that help you understand what's happening in your development environment. ## Overview Intelligent monitoring automatically detects patterns, events, and anomalies in your process output, providing actionable insights and notifications. ## Event Detection ### Build Events Brummer recognizes build lifecycle events: ``` ┌─ Build Events ──────────────────────────────┐ │ 10:23:45 [webpack] Build started │ │ 10:23:47 [webpack] Modules resolved │ │ 10:23:52 [webpack] Bundle generated │ │ 10:23:53 [webpack] Build completed (8.2s) │ │ Status: ✅ Success │ │ Size: 1.2 MB → 1.1 MB (-8.3%) │ └─────────────────────────────────────────────┘ ``` Detected frameworks: - Webpack - Vite - Rollup - Parcel - ESBuild - Next.js - Create React App ### Server Events Monitor server lifecycle and requests: ``` ┌─ Server Status ─────────────────────────────┐ │ Process: dev-server │ │ Status: 🟢 Running │ │ Uptime: 2h 34m 12s │ │ Port: 3000 │ │ URL: http://localhost:3000 │ │ │ │ Recent Requests: │ │ GET /api/users 200 (45ms) │ │ POST /api/login 201 (123ms) │ │ GET /api/data 500 (5ms) ❌ │ └─────────────────────────────────────────────┘ ``` ### Test Results Automatic test result parsing: ``` ┌─ Test Summary ──────────────────────────────┐ │ Test Suite: integration.test.js │ │ │ │ Total: 45 │ │ ✅ Passed: 43 │ │ ❌ Failed: 2 │ │ ⏭️ Skipped: 0 │ │ │ │ Duration: 12.3s │ │ Coverage: 87.5% │ └─────────────────────────────────────────────┘ ``` ## Performance Monitoring ### Memory Usage Track memory consumption patterns: ``` ┌─ Memory Monitor ────────────────────────────┐ │ Process: node (PID: 12345) │ │ │ │ Current: 156 MB │ │ Peak: 234 MB │ │ Average: 142 MB │ │ │ │ Trend: ↗️ Increasing (12 MB/hour) │ │ ⚠️ Warning: Potential memory leak detected │ └─────────────────────────────────────────────┘ ``` ### CPU Usage Monitor CPU utilization: ``` ┌─ CPU Monitor ───────────────────────────────┐ │ Process: build │ │ │ │ Current: 45% │ │ Average: 32% │ │ Cores: 2/8 │ │ │ │ Graph: ▁▂▄█▆▃▂▁▂▃▄▅▆▇█▆▄▃▂▁ │ └─────────────────────────────────────────────┘ ``` ### Response Times Track application performance: ``` ┌─ Performance Metrics ───────────────────────┐ │ Endpoint Performance (last 5 min) │ │ │ │ /api/users │ │ P50: 45ms P95: 123ms P99: 234ms │ │ │ │ /api/products │ │ P50: 67ms P95: 189ms P99: 445ms │ │ ⚠️ Degraded (2x slower than baseline) │ └─────────────────────────────────────────────┘ ``` ## Pattern Recognition ### Dependency Changes Detect when dependencies are modified: ``` ┌─ Dependency Alert ──────────────────────────┐ │ Package.json changed! │ │ │ │ Added: │ │ + axios@1.6.0 │ │ + lodash@4.17.21 │ │ │ │ Updated: │ │ ~ react@18.2.0 → 18.3.0 │ │ │ │ Action required: Run 'npm install' │ └─────────────────────────────────────────────┘ ``` ### Configuration Changes Monitor configuration file updates: ``` ┌─ Config Change Detected ────────────────────┐ │ File: webpack.config.js │ │ Changed: 2 minutes ago │ │ │ │ Affected processes: │ │ - dev-server (restart required) │ │ - build (will use new config) │ │ │ │ [R] Restart affected processes │ └─────────────────────────────────────────────┘ ``` ### Code Changes Track file changes and their impact: ``` ┌─ File Watcher ──────────────────────────────┐ │ Recent changes: │ │ │ │ 10:45:23 src/App.js (modified) │ │ → Triggered: Hot reload │ │ │ │ 10:45:45 src/api/users.js (modified) │ │ → Triggered: Server restart │ │ │ │ 10:46:12 tests/unit/App.test.js (added) │ │ → Triggered: Test run │ └─────────────────────────────────────────────┘ ``` ## Smart Notifications ### Notification Types 1. **Success Notifications** - Build completed - Tests passed - Server started 2. **Warning Notifications** - Memory usage high - Slow response times - Deprecation warnings 3. **Error Notifications** - Build failed - Test failures - Runtime errors ### Notification Rules Configure when to receive notifications: ```yaml monitoring: notifications: - event: "build_failed" priority: high actions: - desktop_notification - sound_alert - event: "memory_high" threshold: "80%" priority: medium actions: - tui_alert - event: "test_complete" condition: "failed_count > 0" priority: high ``` ## Anomaly Detection ### Unusual Patterns Brummer detects deviations from normal behavior: ``` ┌─ Anomaly Detected ──────────────────────────┐ │ Type: Unusual Error Rate │ │ │ │ Normal rate: 0.5 errors/min │ │ Current rate: 15.3 errors/min (30x) │ │ │ │ Started: 5 minutes ago │ │ Possible cause: Recent deployment │ │ │ │ [I] Investigate [S] Snooze [D] Details │ └─────────────────────────────────────────────┘ ``` ### Performance Degradation Detect performance issues: ``` ┌─ Performance Alert ─────────────────────────┐ │ Build times increasing! │ │ │ │ Historical average: 8.2s │ │ Last 5 builds: │ │ 12.1s, 13.4s, 14.2s, 15.8s, 16.2s │ │ │ │ Possible causes: │ │ - Growing codebase │ │ - New dependencies │ │ - Configuration issues │ └─────────────────────────────────────────────┘ ``` ## Log Analysis ### Log Summarization Automatically summarize verbose logs: ``` ┌─ Log Summary (last 1000 lines) ─────────────┐ │ Categories: │ │ - HTTP Requests: 412 (41.2%) │ │ - Database Queries: 234 (23.4%) │ │ - Warnings: 89 (8.9%) │ │ - Errors: 12 (1.2%) │ │ - Other: 253 (25.3%) │ │ │ │ Top patterns: │ │ 1. "GET /api/*" (156 occurrences) │ │ 2. "Query executed" (89 occurrences) │ │ 3. "Cache hit" (67 occurrences) │ └─────────────────────────────────────────────┘ ``` ### Trend Analysis Identify trends over time: ``` ┌─ Trend Analysis ────────────────────────────┐ │ Error Rate Trend (24 hours) │ │ │ │ 12 | ▃ │ │ 10 | ▂█▅ │ │ 8 | ▂███▇▄ │ │ 6 | ▃█████▆▃ │ │ 4 | ▄███████▇▅▃▂ │ │ 2 |▆████████████▇▅▄▃▂▁▁▂▃▄▅ │ │ 0 |━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ │ │ 00:00 06:00 12:00 18:00 24:00 │ └─────────────────────────────────────────────┘ ``` ## Integration Features ### Slack Integration Send important events to Slack: ```yaml monitoring: integrations: slack: webhook_url: "https://hooks.slack.com/..." events: - build_failed - test_failed - server_crash ``` ### Metrics Export Export metrics to monitoring systems: ```yaml monitoring: metrics: prometheus: enabled: true port: 9090 statsd: enabled: true host: localhost port: 8125 ``` ### Custom Webhooks Send events to custom endpoints: ```yaml monitoring: webhooks: - url: "https://api.myapp.com/brummer-events" events: ["error", "warning"] headers: Authorization: "Bearer token" ``` ## Dashboard View Access the monitoring dashboard with `Ctrl+D`: ``` ┌─ Monitoring Dashboard ──────────────────────┐ │ ┌─ Processes ─┐ ┌─ Errors ──┐ ┌─ Perf ───┐ │ │ │ ● dev ✅ │ │ Last hour │ │ CPU: 23% │ │ │ │ ● test 🔄 │ │ Errors: 3 │ │ MEM: 45% │ │ │ │ ● build ⏸️ │ │ Warns: 12 │ │ I/O: Low │ │ │ └─────────────┘ └───────────┘ └──────────┘ │ │ │ │ ┌─ Recent Events ───────────────────────┐ │ │ │ 10:23:45 Build completed successfully │ │ │ │ 10:22:12 Test suite passed (45/45) │ │ │ │ 10:20:33 Server started on port 3000 │ │ │ └───────────────────────────────────────┘ │ │ │ │ ┌─ Alerts ──────────────────────────────┐ │ │ │ ⚠️ High memory usage in 'dev' process │ │ │ │ ℹ️ 3 deprecation warnings found │ │ │ └───────────────────────────────────────┘ │ └─────────────────────────────────────────────┘ ``` ## Configuration ### Enable/Disable Features ```yaml monitoring: features: memory_tracking: true cpu_tracking: true event_detection: true anomaly_detection: true performance_tracking: true ``` ### Thresholds ```yaml monitoring: thresholds: memory_warning: 80 # percentage memory_critical: 95 cpu_warning: 70 cpu_critical: 90 error_rate_warning: 5 # errors per minute response_time_warning: 1000 # milliseconds ``` ### Retention ```yaml monitoring: retention: metrics: 24h events: 7d logs: 1h ``` ## Best Practices 1. **Start with defaults** - Brummer's defaults work well for most projects 2. **Customize gradually** - Add custom patterns as you learn your app's behavior 3. **Set meaningful thresholds** - Base them on your application's normal behavior 4. **Use notifications wisely** - Too many alerts lead to alert fatigue 5. **Review trends regularly** - Weekly review of trends can prevent issues 6. **Export important metrics** - Integrate with your existing monitoring stack 7. **Document patterns** - Share custom patterns with your team