Operations | Monitoring | ITSM | DevOps | Cloud

“I want to look them in the eye.” It’s a common saying about the importance of body language. In the past, that “look” might take a day of travel and cost most of a day of productivity. Today, however, modern enterprises are turning to real-time unified communication solutions to get meeting participants engaged—and cloud technology is the key.

“With sustainability our primary focus, our technology strategy has to mirror our overall approach. With Rancher we’re driving real transformation to prime us for long-term growth.” – Zach Dunn, Senior Director of Platform Operations and CSO, Optoro. Have you ever considered what happens to items you return to etailers? In retail, especially ecommerce, nearly 25 percent of all goods are returned or don’t sell.

Editor's note: This blog is part two of our series on launching an app to AWS. For the first installment, "How to deploy an app to AWS: Getting started," click here. So, your application is ready for production. You’ve taken an inventory of your applications, dependencies, and configuration. Now, you’re ready to create a new AWS account and start launching resources.

If you’re using Linux, I’m sure you bumped into journald: it’s what most distros use by default for system logging. Most applications running as a service will also log to the journal. So how do you make use of these logs to: In this post, we’ll answer all the above and more. We will dive into the following topics: There are lots of other options to centralize journal entries, and lots of tools to help.

Cloud-native is the new standard for modern applications. This usually means container-based applications, using the popular Docker and Kubernetes platforms, and increasingly also service mesh platforms such as Istio and Envoy. With that, container security in general—and Kubernetes security in particular—is at the forefront of engineers’ minds. Docker popularized containers based on the good-old but little-used LXC Linux containers.

Service alarms are going off and you are on the hook to restore stability, but you need to prevent any more changes to production while you dig further. You could "freeze" production by announcing it in the office, sending a message on Slack, or sending an email to the affected teams, but that may not be enough or may require extra work that would distract you from debugging and fixing the problem.

Modern-day life is fast, hectic, demanding. Time is precious, and we often need to be able to squeeze every atom of efficiency from our environment and our tools. But sometimes, the best thing you can do for your productivity is – to do nothing. Sometimes, less is more. In this article, we want to show you a number of nice, fun and not-strictly-productivity-focused apps that can help you relax, forget about the time-efficiency continuum, and recharge your cells for the next lap in the race.

This is the second blog in our series releasing the WSLConf recordings. Earlier this year, Canonical had the pleasure of hosting WSLConf, a virtual conference dedicated to the Windows Subsystem for Linux (WSL). The conference highlighted ideas and projects from presenters from around the globe with attendees from at least eight different time zones.

One of the challenges when you’re starting out with DevOps is getting the lay of the land. There are a lot of tools out there. And when one of the goals of DevOps is continually improving your processes, it’s important for you to understand how those tools might fit in your infrastructure. At the same time, you want to be efficient. You don’t want to add tools that overlap with one another. Or tools that cost more than other effective alternatives.