Over the past several years, status pages have become more and more commonplace. They are not just a feature of the behemoth cloud providers like Google, Amazon, and Microsoft, but common among the multitudinous rank-and-file SaaS companies that every modern business depends on. Having a well-maintained status page is not just a luxury anymore.

Here are short instructions how to integrate your AppBeat Monitoring with PagerDuty.

As serverless application architectures have gained popularity, AWS Lambda has become the best-known service for running code on demand without having to manage the underlying compute instances. From an ops perspective, running code in Lambda is fundamentally different than running a traditional application. Most significantly from an observability standpoint, you cannot inspect system-level metrics from your application servers.

When most people hear ‘dynamic thresholds’ in the context of monitoring, they think of the ability to trigger alerts based on a non-static threshold. While this can be incredibly useful, it’s really only half the picture.

You have just deployed a new Virtual Apps and Desktops Site for your customer. You thought about what policies should apply in the environment, however you can’t possibly know them all. So, what you will want to do is to before deploying anything to end-users is shift through all the Citrix Policies on offer and configure them appropriately based on business needs and end-user requirements. There are many policies available. Luckily, you will likely not need to touch 80% of them.

Today's IT and DevOps teams have not one, but two, feature-rich open source Web servers to choose from: NGINX and Apache HTTP Server (which is often called simply "Apache"). At a high level, both platforms do the same core thing: Host and serve Web content. Both also offer comparable levels of performance and security. Yet when you dive into the details, you'll find that there are many differences between NGINX and Apache.

As you monitor the health and performance of your infrastructure and applications, you also need to be able to identify potential threats to the security of those components. To help address this challenge, we’re pleased to announce that Datadog now integrates with AWS Identity and Access Management (IAM) Access Analyzer, a new IAM feature that helps administrators ensure that they have securely configured access to their resources.

The networking field is changing quickly with the emergence of new technologies. This change, along with the onset of digital transformation and increasing cloud-adoption, highlights how businesses have realized the importance of the third platform, as it interconnects mobile computing, cloud computing, social media, and information analytics. 2019 has been the year of edge computing and the dawn of the SD-WAN.

This is a writeup of the talk I gave at PromCon 2019. TSDB is the storage engine of Prometheus 2.x. Based on the Gorilla compression, it started out in an independent repo, which eventually attracted 60+ contributors and 771 stars. There were 500+ commits after the Prometheus 2.0 release. The repo was archived in August 2019, and now it’s a part of the Prometheus repo, inside the tsdb directory. Here are some highlights of the development over the past year.