Welcome to Hit Subscribe’s weekly digest post! When new posts from our authors pop on blogs, we’d like to start celebrating them and featuring their work here. So check out this week’s work below.

Data Compliance: A Detailed Guide for IT Leaders

So, As the leader of a DevOps or agile team at a rising software company, how do you ensure that users’ sensitive information is properly secured? Users are on the internet on a daily basis for communication, business, and so on. While accessing the internet, they often input sensitive information that ought to be confidential, like credit card details. So, how do you make sure that your team makes security a priority as it works to ship features to users? Ukpai Ugochi might be able to answer these questions on Enov8’s blog. 

Databases are the foundation of most software applications. And much like when building a house, consideration needs to be given to make sure the foundation is right. When we build a house, we ask a multitude of questions before laying any foundation. What type of soil is it? What size and shape are the house? Where do the services need to run? What type of weather is common in the area? Find out more from Michael de Ridder on Scalyr’s blog.

What Does Server Monitoring Mean in 2021? A Look at Modern Server Options and How to Monitor Them

A few years ago, monitoring was simple. We had all our servers somewhere in the data center; we just had to install a monitoring tool and gather all the data from every server. Things changed when we started moving to the cloud and then to containers. Today, we often need to monitor a variety of different sources. A “server” can be a physical machine, virtual machine, container, or even a serverless application. Therefore, our approach for monitoring needs to change. In this post, you’ll learn what server monitoring means in 2021 and how to monitor modern infrastructure. Learn more about Dawid Ziolkowski on Solarwinds’ blog. 

Aggregating Application Logs From EKS on Fargate

Papertrail supports most log types and is easy to configure with multiple services, applications, and cloud providers. It can aggregate from other logging services such as CloudWatch as well. It looks a lot like Log4j, so it should feel familiar to software engineers. This is great for people who have multi-cloud setups who want to aggregate logs from different CloudWatch groups. It’s also very lightweight, and the solution we’re using today doesn’t require any sidecars, ELK stacks, or the like. Once it’s all configured, it will monitor logs from all your pods across all namespaces. Find out more from Jillian Rowe on Solarwinds’ blog. 

We also updated a couple of posts. As a developer, stack traces are one of the most common error types you’ll run into. Every developer makes mistakes, including you. When you make a mistake, your code will likely exit and print a weird-looking message called a stack trace. But actually, a stack trace represents a path to a treasure, like a pirate map. It shows you the exact route your code traversed leading up to the point where your program printed an exception. But, how do you read a stack trace? How does a stack trace help with troubleshooting your code? Let’s start with a comprehensive definition of a stack trace. Learn more on Scalyr’s blog.

QA Metrics: An Introduction and 7 Examples to Help You

Finally, we updated a post on QA metrics. The technology industry is becoming more and more competitive with each passing year. Organizations around the world struggle to remain afloat. They employ strategies to improve the quality of their products and services. They adopt test automation to obtain shorter release cycles. However, many companies don’t actively track their progress (or lack thereof) when it comes to quality improvements, which threatens to make the whole effort futile. If we accept that we can’t improve what we don’t measure, then QA metrics become crucial to improving quality in our organizations. Check it out on Testim’s blog.