“DB has Low Disk Space” alert instantly disrupts a Saturday family movie night. You rush to grab your laptop from your bag, which is somewhere in the house. After a hurried search, you finally find it, open it, and discover it’s out of charge. You quickly plug it in, waiting for it to power up. OS is booting slowly, and once the desktop wallpaper appears, you start navigating through multiple authentication steps on the corporate network. Finally, you SSH into the database server, enter a one-time code for 2FA, and you’re in.

Initial checks reveal that MySQL has consumed almost all available disk space, causing the company’s web service to stop responding. You identify the largest file in the system from the last several hours—it turns out the database logs consumed all the disk space. You quickly remove the log file to fix the issue and get back to your family.

One hour later, Bill, your team lead, calls. He says that the DB server is still experiencing issues. You reconnect and review file changes and bash history to find the root cause. After copying and pasting multiple commands from history, reading logs, and verifying configurations, you notice that someone edited the MySQL config files. You check every edited config file and finally discover that all SQL queries are being saved to a file.

You can only guess, but it seems that someone from the dev team was likely troubleshooting the database and forgot to disable the logging afterward. You revert these changes and delete the log files to free up disk space.

The server stabilizes, but your family night was ruined. You’re left wondering: is there a faster and easier way to find such issues?

Meet Logs in Termius

What if you could troubleshoot just like replying in WhatsApp without having to stand up from the couch? Instead of rushing for a laptop and searching through scattered information across knowledge bases, access systems, and command history on remote servers, you can find it all in one place. Termius saves your latest connections, executed commands, their outputs, and essential metadata like users and timestamps.

You can filter by a server, identify who connected to it, and review session logs. This gives you a full picture before you even establish a connection. Then, connect with one click from your phone or laptop and resolve the problem with a few commands.

Detailed access and session logs save you time on troubleshooting and reduce guesswork. Instead of piecing together scattered information, you have a comprehensive audit trail at your fingertips.

And it’s not just for you. Logs are synced and shared via an encrypted vault, guaranteeing that anyone on your team can access them. 

With Termius, you can now troubleshoot faster, more efficiently, and with less disruption to your personal life.