How To Check Linux Process Deeply With Common Sense

Apparently process checking is critical. Yes, we already have tons of linux tools and tips available. Getting familiar with your weapons is actually the first step, and the easiest part.

More importantly, what questions you ask, what for, when approaching your critical process. Fortunately even with plain common sense, we can dig out lots of valuable information.

Check Linux Process With Common Sense


9 Key Feedbacks For Prod Envs Maintenance

To break silos and improve availability, DevOps/Ops should be actively collecting useful feedback of prod env maintenance on a regular basis. Enable developers to easily access it and improve feedback loop together as a team effort.

The very first and most important part. What To Examine, Providing Developers Meaningful Feedback?

Continuous Feedback


Use Nmap To Automate Insecure Ports Check

While go cloud is a prevailing trend, security is something we can’t afford to ignore. People hate malicious access. Periodically check all widely open TCP Ports is one good practice to secure our system in cloud. Obviously DB ports can’t be exposed to the whole internet. Our internal REST API also need to be protected.

We should make sure firewall is properly configured. What’s more important, we need to be always on top of these security holes with minimum efforts. So let’s automate the audit process of insecure TCP Ports.

Use Nmap To Automate Insecure Ports Check


Compare Difference Of Two Envs

Why it’s working in my server, but fails in yours? The question is quite common. After careful check and side-by-side test, we may or may not find out the difference. The root cause may be packages conflict, mismatched versions, corrupted files, or something magic.

How we can quickly detect the noticeable differences between two servers?

Compare Env Difference