Troubleshooting Issues

users are reporting errors, investigate

why is the API slow?

the frontend isn't loading, what's wrong?

check the database performance

the API server keeps crashing

services can't connect to the database

You: Users reporting 500 errors

Monk: Investigating...

      Found: API server #2 out of memory
      Cause: Memory leak in session handling
      Impact: ~150 active users affected

      Fix: Restart affected instance and scale up

      Should I proceed?

what's using all the CPU?
which service is using the most memory?

can the API reach the database?
test the connection to Redis

show me recent errors
filter logs for 500 errors

what's causing slow queries?
why is the cache hit rate low?

show me the last 100 lines of API logs
check logs from the past hour

show me resource usage for the past day
compare current vs normal performance

which services are unhealthy?
show me failed deployments

restart the API server
scale up the database
increase worker memory

Monk: The issue is your app reads REDIS_HOST but Monk provides REDIS_URL.
      I can update your code to read from REDIS_URL. Should I fix this?

You: Yes, fix it

check if the issue is resolved
test the API endpoint