DevOps with Asthavi

When a production database CPU hits 95%, you need to act fast. Here are the exact terminal commands and infrastructure metrics to check immediately, categorized by the top database engines and monitoring tools: 1. Active Processes & Runaway Queries Identify and stop the specific query that is consuming all the CPU cycles. PostgreSQL : Run SELECT pid, age(clock_timestamp(), query_start), usename, query FROM pg_stat_activity WHERE state != 'idle' ORDER BY age DESC; to find long-running queries. If a query is stuck, kill it safely using SELECT pg_cancel_backend(pid); . MySQL : Run SHOW FULL PROCESSLIST; . Sort by the Time column. Look for queries stuck in "Sending data" or "Sorting" states. Terminate the rogue process using KILL [process_id]; . MongoDB : Run db.currentOp({"active": true, "secs_running": {$gt: 5}}) to list operations running for more than 5 seconds. Terminate them using db.killOp(opId) . 2. Traffic Spikes & Conn...

  Sharing Terraform plans in Pull Requests (PRs) is a standard DevOps practice designed to give reviewers visibility into infrastructure changes before they are applied. You can achieve this using specialized GitOps tools, managed platforms, or custom CI/CD pipelines . [ 1 , 2 , 3 , 4 , 5 ] 1. Dedicated GitOps Tools (Recommended) Dedicated GitOps tools specialize in integrating Terraform operations directly into your repository's PR comment section. They handle plan visibility and state-locking natively. [ 1 , 2 , 3 ] Atlantis : An open-source, self-hosted framework that automates Terraform via PR comments. When you open a PR, Atlantis automatically runs terraform plan and prints the output as a Markdown comment. Reviewers can type atlantis apply directly in the comment section to deploy the changes. [ 1 , 2 , 3 , 4 , 5 ] Digger : An open-source alternative that allows you to orchestrate Terraform within your existing CI/CD provider (like GitHub Actions) rather than hosting a s...