Skip to main content

What It Does

Monk brings monitoring capabilities directly into your IDE. View logs, access container shells, check resource usage, and troubleshoot issues - all through chat. No SSH, no separate dashboards, no log aggregation setup.

How It Works

System Understanding

Monk maintains a complete picture of your running system:
  • Every service and its current state (running, stopped, restarting)
  • Every container and what it’s doing
  • Every database connection and query load
  • Every API integration and its status
  • Resource usage for each component (CPU, memory, disk, network)
  • Relationships between all components
Ask Monk about your system:
what's running right now?

Live Log Streaming

View logs from any service in real-time:
show me logs from the API server
Log capabilities:
  • Live streaming from any service
  • Historical logs available
  • Filter by time range, severity, or keywords
  • Logs from multiple services simultaneously
  • All displayed in your IDE

Log Analysis

Don’t want to read logs manually? Ask Monk to analyze them:
check the API server logs for errors
Monk interprets logs, finds patterns, and suggests fixes.

Shell Access

Get instant shell access to any container:
give me shell access to the API server
No SSH required:
  • Direct access to any container
  • No SSH keys to manage
  • No bastion hosts needed
  • Works across all clouds

Resource Metrics

Track and understand resource consumption:
what's the resource usage?
Metrics tracked:
  • CPU, memory, disk, network for every service
  • Application-specific metrics (queue depth, connection pools, cache hit rates)
  • Database performance (query times, connection counts, slow queries)
  • Integration status (API response times, webhook deliveries)

Autonomous Troubleshooting

When something goes wrong, describe the issue:
users are reporting slow page loads
What Monk does:
  1. Reads logs across all services
  2. Checks metrics and resource usage
  3. Examines workload state (containers, processes, connections)
  4. Correlates data to find root cause
  5. Suggests (and can apply) fixes
Monk has complete system context and investigates across all components simultaneously.

24/7 Monitoring with Watcher

For continuous monitoring and Slack alerts, set up Watcher:
set up watcher
Watcher monitors your cluster around the clock and sends AI-analyzed alerts when issues arise. Each alert includes a “Fix with Monk” button that opens your IDE with full issue context. → See Watcher for setup and configuration details. Available on Pro and Team plans.

What Makes This Different

Traditional monitoring requires:
  • Setting up log aggregation (ELK, Splunk, Datadog)
  • Configuring metric collection (Prometheus, Grafana)
  • Creating dashboards and alerts
  • SSH access for container inspection
  • Manually correlating logs and metrics
  • Jumping between multiple tools and dashboards
  • Learning query languages (PromQL, LogQL, etc.)
With Monk: Ask questions in natural language. Monk analyzes logs, metrics, and system state autonomously from your IDE.

Coming Soon

Advanced Observability Integrations COMING SOON For teams that need advanced observability, Monk will integrate with popular tools:
  • Datadog
  • New Relic
  • Grafana Cloud
  • Honeycomb
  • Sentry (error tracking)
  • Prometheus + Grafana
  • ELK Stack (Elasticsearch, Logstash, Kibana)
  • TIG Stack (Telegraf, InfluxDB, Grafana)

Key Capabilities

  • System understanding: Knows every service, container, database, API
  • Live log streaming: Real-time logs from any service
  • Log analysis: Monk interprets logs and finds patterns
  • Shell access: Direct access to any container from IDE
  • Resource metrics: Track CPU, memory, disk, network for all services
  • Application metrics: Queue depth, cache hit rates, query times, etc.
  • Autonomous troubleshooting: Report issue, Monk investigates and suggests fixes
  • IDE-native: All capabilities accessible from your editor
  • No setup required: Works automatically for all deployments