Businesses around the world have been forced to adopt remote working policies in response to the COVID-19 outbreak. In just two months, a vast number of employees around the world shifted to a work-from-home environment. Although some businesses already had many of their IT operations available on the cloud before the pandemic—with the help of cloud-hosted email and collaboration suites such as Office 365—no one expected such a sudden and widespread transition into teleworking.

In the past two months, companies everywhere have shifted their workforces from office cubicles and conference rooms to home offices and dining room tables. The coronavirus pandemic’s thunderous impact – bolstered by government mandates to maintain social distancing protocols and shut down non-essential workplaces – has forced companies to pivot hard and fast to a new reality, whether they’re ready for it or not.

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.

Grafana v7.0 is coming next month! Here’s a sneak peek of one of its features: a brand-new table panel. The current (old) table panel has accumulated a ton of feature requests over the years, and we are excited to finally close many of them in 7.0 with this new table panel. Among the many new things this panel can do is to include other visualizations inside cells. For example, you can configure a cell style (per column) to render the value as a bar gauge.

So, you are considering moving to the cloud. Or, likely, have already transitioned your services. If you are wondering what the next steps are, you have many options on how to move towards cloud infrastructure. This blog will cover what to consider when using public clouds. Specifically, we will focus on monitoring a hybrid cloud set up using the big 3 cloud providers, Amazon Web Services (AWS), Microsoft Azure, and Google Cloud Platform (GCP).

As with all other companies, the Blameless team is adapting to a world of remote work where distributed teams will need to get better than ever at staying aligned and efficient. We’ve been relying on Blameless more and more to improve how we collaborate virtually. Here are some of the top workflows and tips on how we have been using Blameless internally to streamline remote productivity.

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.

“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.

“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.

Kubernetes adoption comes with a lot of challenges. One of them is consistently deploying applications to the platform. GitOps is a strategy which solves this problem and solves it at scale. In this blog, we will share how to leverage TravisCI and ArgoCD to design a highly scalable production-ready CI/CD workflow.