In our previous piece 10 Essential Steps for Configuring a New Server we walked through some of the best practices to follow when setting up a new Linux server. But how can you tell if your server is setup correctly? More importantly, how can you ensure those initial configurations don’t drift over time? With UpGuard, you can do both at any scale, so we’ve created a policy within our cyber resilience platform to match our 10 essential steps as an example of how we can help organizations control their IT environments.
Linux admins have always relied on the command line to manage their systems. While not as immediately intuitive as a GUI, command line interfaces (CLIs) open up the real power of computing with a slew of versatile commands that can be chained together for nearly any purpose. GUIs, on the other hand, are limited to the nearly always reduced functionality developers built into the buttons and screens. This model makes sense, since only some people will need the “advanced” capabilities of the command line, while others perform only a few tasks over and over with a minimum of knowledge about the software. Regular command line users develop a sense of how to best use the commands over time, but with this UpGuard primer, even dabblers can take advantage of some quick tricks using these five basic Linux commands.
You’re monitoring your IT infrastructure for changes and errors, right? Of course! You need to know every time something hits the fan; it comes with the territory. You can barely pull up an incognito tab at work without getting an error message. The problem is, a lot of alerts don't apply to you. Hey, but at least you get paged in the middle of the night when a backup server reads low on memory! And that weekend trip you cut short only to find a fix had already been checked in? What a rush!