The latest News and Information on DevOps, CI/CD, Automation and related technologies.
VictorOps is an incident response tool whose mission is straightforward: “To make being on call suck less.” It enables teams to quickly detect and respond to problems like a service degredation or outage. VictorOps supports a wide range of external integrations to extend its capabilities by connecting different parts of your DevOps toolchain.
It makes it easier to validate any server’s status without flipping between program and tools if you have one platform to track the servers. Besides, every server with remote server monitoring from a single application viewing window is provided with an accurate and real-time status. You will have the option of simplicity to decide what sort of services you want to track on each server. For instance, only a network storage server used for data backups could control a drive storage area.
If you are a part of an engineering organization it is highly likely that you have heard the latest buzz words “containers”, “docker” and “kubernetes”. Today we will try to demystify these terms for you. Sit tight, it's going to be very interesting.
A lot of engineers think a project is done once the code is live. In a perfect world, that could be true—alas, commits are rarely free of problems. For companies that have a lot of focus on dev but little on ops, this can quickly turn into a nightmare. Fortunately, there are a lot of infrastructure monitoring tools out there that can help marry DevOps and keep your apps, websites, and processes running smoothly.
HAProxy provides an easy and straightforward way to add HTTPS to your website. As a load balancer positioned in front of your web servers, it can handle all of the encryption and decryption duties, offloading those tasks from your upstream servers. That’s good because in today’s age of privacy awareness, the consensus is that every website must implement HTTPS, regardless of whether sensitive or private information is being exchanged.
Before we dive into the gap in cloud network security, let’s take a step back. If you’ve been in Operations for a while, you might remember how it used to be. “Network” was a team. When you needed to open a port on the network, you had to provide an exhaustive definition of the change, explaining what port you needed, what external addresses should be able to reach it, and where it should be routed to internally.
The first time I created a cloud compute instance, then still called a “Cloud VM”, was an almost transcendent moment. It was like magic. I was at my first organization which had adopted the cloud, in my first DevOps position, and I immediately knew that the world had changed.
