As time goes by, I’m looking for solutions that require as little maintenance as possible. One of those is deploying our client web app and our homepage directly on the CDN edge, with GitHub Actions. Not only we don’t need a server to host the app, but the deployment script is also serverless and maintenance-less. This allows me to focus on important tasks, knowing that deployment and serving of the app is always blazing fast.

Sharing information about the health and performance of an application is a critical part of any team’s daily workflow. That’s why we’re excited to announce the Datadog Slack App, which simplifies crucial communication tasks by deepening the integration between Datadog and Slack.

Do you want to know how to measure the full impact of third-party scripts and page contents on your website? In this article, we step you through the process as we analyze the performance impact third-party elements have on a popular content marketing site. We go beyond looking at how a single third-party supplier affects page performance and show you how to measure how the different types of third-party content affect page performance.

Making sense out of logs is not an easy task. Log management solutions, such as Sematext Cloud, gather and accept data from multiple sources. Those sources can have different log events structures, providing a different granularity. They may not follow common, logging good practices and be hard to get some meaning from. Because of that, it is important that the application we develop and follow best practices. One of those is keeping meaningful log levels.

As you adopt SRE practices, you’ll find that there are optimization opportunities across every part of your development and operations cycle. SRE breaks down silos and helps learning flow through every stage of the software lifecycle. This forms connections between different teams and roles. Understanding all the new connections formed by SRE practices can be daunting. Building a model of SRE specific to your organization is a good way to keep a clear picture in your head.

A key topic of conversation that comes up again and again with our customers is the challenge of collaboration in a remote work environment. Too many channels of communication or documentation are ineffective, and IT professionals are starting to feel fatigued by never feeling quite “in the know” with business decisions that are happening in real-time. When separated from colleagues, teams can feel distant and unmotivated or find it hard to stay focused.

Your monitoring system provides a comprehensive overview of any infrastructure. To effectively monitor your infrastructure and systems, you’ll need to get all of your data into one place - regardless if you have 1 node or 10 nodes. This centralization of data inevitably creates a vulnerable point that attackers can potentially target and exploit. In this article, we look at how to design your infrastructure in a secure way, as well as focus in on how to secure your nodes.

If you use Kubernetes in production, you should already know that monitoring and logging solutions are essentials if you want to make sure that your cluster is healthy at all times. Lack of computing resources and capacity misconfigurations are one of the most common causes of failed deployments. Especially if you are an operator, you always need to know the load of your cluster in order to perform capacity planning and setup autoscaling.

There are many articles and videos about practicing Continuous Delivery (CD) with applications, but not nearly as many for infrastructure. The same can be said for GitOps applied to infrastructure. That is a bit strange given that applications and infrastructure are almost the same today. Both are defined as code, and everyone stores code in Git repositories. Hence, GitOps is just as good of a fit for infrastructure as for anything else.