Skip to main content

​
What It Does

Monk gives you logs, shell access, metrics, and troubleshooting directly in your IDE. You ask questions in plain English. Monk pulls the answers from your running system. That’s it. No dashboards, no log aggregation setup, no query languages.

​
How It Works

​
System Understanding

Monk maintains a live picture of your entire deployment:
  • 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 per 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
Monk streams live logs, pulls historical logs, and filters by time range, severity, or keywords. You can tail multiple services at once. Everything stays in your IDE.

​
Log Analysis

Don’t want to read logs yourself? Let Monk do it: 
check the API server logs for errors
Monk reads the output, finds patterns, and suggests fixes.

​
Shell Access

Get a shell into any container instantly: 
give me shell access to the API server
This isn’t SSH. Monk opens a shell connection over its intra-cluster encrypted P2P network. No SSH keys to manage, no bastion hosts, no port forwarding. It works across all clouds because the connection runs through Monk’s own mesh — not through your cloud provider’s networking.

​
Resource Metrics

Track resource consumption across your stack: 
what's the resource usage?
Monk tracks CPU, memory, disk, and network for every service. It also surfaces application-level metrics: queue depth, connection pools, cache hit rates, database query times, slow queries, API response times, and webhook deliveries.

​
Autonomous Troubleshooting

Something’s wrong? Describe the problem: 
users are reporting slow page loads
Monk reads logs across all services, checks metrics and resource usage, examines workload state, correlates the data, and identifies the root cause. It suggests fixes — and can apply them if you say the word. Monk has full system context. It investigates across every component 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.

​
Observability Integrations

Integrations with Datadog, New Relic, Grafana Cloud, and other observability platforms are on the roadmap. Vote on what to prioritize.

​
Go Deeper

Watcher

24/7 autonomous monitoring with Slack alerts

Security

How Monk secures shell access and cluster communication