When we talk about IoT (or the Internet of Things), we immediately imagine a series of devices – although IoT is much more than that, we often think of household appliances – working in a coordinated way, as if by magic. But those who work with magic (like those who work with engineering) know that behind a great effect there is a complicated and laborious mechanism designed to make the trick work perfectly, and the audience is first surprised and then breaks into applause.

It is easy to communicate when you are only two. That was us when starting off WebGazer. The easiest way to decide on an issue was to discuss it in person or on the phone. We did not need to think on in-house culture, values and so on. This is mostly due to the fact that we, two of us, were all those at once. We were walking-ethics, values and everything you would expect from a website monitoring service.

Like all good IT organizations, you religiously measure the performance and availability of your services and applications. But if those apps run in the cloud, critical components are often delivered by a third party or the cloud provider. In the case of a service disruption or degraded performance, how do you know what the problem is—your code, the network, or the provider? And, if the problem is with the service provider, how do you convince them to take action as quickly as possible?

Thomas Stocking, co-founder and vice president of product strategy, recently wrote an article titled How to Efficiently Discover Network Resources, featured in The Data Center Journal. The article talks about network discovery tools and processes, and why it’s important to automate and standardize. Many business processes (security management, service delivery and service support) depend on the administrator’s knowledge of the network details.

Enterprises are increasingly moving their applications to the cloud and Amazon Web Services (AWS) is the leading cloud provider. Our 20 extensions provide expanded AWS monitoring.

Windows hosts make up a significant portion of the infrastructure of many organizations, and visibility into Windows systems can be a vital observability need. We’re pleased to announce that Datadog’s Live Process monitoring is now available for Windows.

Your application is deployed. You checked a few endpoints, and they work as expected. You can log in and see the generic home page. There aren’t any exceptions in the logs—or at least any new ones. Great! But what does that mean for your customers and partners? Does everything work for them?

When you visit a webpage that is down, most of the time you'll see an error: you'd see a 404 error if the page can't be found or a 503 if the server isn't unavailable. Although this is not what you want to see, it is helpful. You know that the site is down and have a rough idea why. But sometimes you don't see an error... just a spinning wheel.

In our appropriately named Life at Sentry series, we talk to Sentry employees about what life is like at Sentry (and how they ended up here). In this edition, we’re chatting with Chloe Condon, Developer Evangelist(a) at Sentry, about stumbling into tech, imposter syndrome, and not getting cast as Carrie in “Carrie: The Musical.” Take a look at our available jobs if you’re interested in joining us.

One of the key performance indicators of any system, application, product, or process is how certain parameters or data points perform over time. What if you want to monitor hits on an API endpoint or database latency in seconds? A single data point captured in the present moment won’t tell you much by itself. However, tracking that same trend over time will tell you much more, including the impact of change on a particular metric.