Today is a very proud day for PagerDuty and PagerDuty fans around the world—we rang the bell at the New York Stock Exchange to begin our first day of trading as a public company. Today, as a community, we celebrate the collective success of our users and customers and an incredible milestone few companies achieve. While our IPO is a huge milestone, our journey together is just beginning.
Most modern web apps end up sprouting some subset of tasks that happen in the “background”, i.e., when a user is not directly waiting on the request from a server to finish. These types of tasks range across all kinds of use cases – processing media, generating aggregate statistics for later view in the front end, and syncing data to 3rd party providers are just a few of many examples.
Ever have this experience? After a miserable commute in stormy weather, you get to your college campus only to find out that that it’s been closed for a snow day. Fortunately, this no longer has to be an issue! Mass notification tools enable academic institutions to send timely and urgent notifications to their faculty members or students. In this way, campus communities will always know when an event or situation will affect their academic schedules.
Democratizing data is one of our key product goals, and we share a similar approach to content. With over half a million words, our Sumo Logic documentation set is a substantial amount of information to provide to our users on the various ways you can collect logs and metrics, query that information, and turn it into meaningful visualizations. But the real trick is making sure that people can find what they need quickly.
Logging your virtual machines (VMs) is important, but what’s even more important is logging the hypervisors that run them. Hypervisors generate extremely useful data about the operation of your virtual machines and the environments that they run in. While VMs provide some information about their state, details such as VM performance, changes in state, errors, and security can only be found through hypervisor logs.
I’m in a position where I converse with our customers and cloud service providers, and I keep track of conversations happening through blogs and social media. I then sift through all this data to identify patterns and trends. Lately, I’ve seen some talk about an architectural pattern that I believe will become prevalent in the near future.
Google Cloud’s Stackdriver Logging is a managed service that centralizes and stores logs from your Google Cloud Platform services and applications. We are excited to announce that Datadog’s GCP integration now includes Stackdriver Logging. You can collect all your GCP logs using Datadog so you can search, filter, analyze, and alert on them along with your metrics and distributed request traces in a single platform.
In the midst of all the turmoil and debate around Open Distro for Elasticsearch, Elastic continues to produce, and last week announced both a new major release of the Elastic Stack — version 6.7 (and also the first release candidate for 7.0!). As usual, I’ve put together a brief overview of the main features introduced. One change I’ve applied this time is adding a comment for each feature detailing what license it falls under.
Spiceworks examines computer hardware leasing and the shift to the “as-a-service” model among organizations across North America and Europe.
Uptime.com and the Nagios monitoring tool serve similar functionality from a surface view. Both alert users to downtime, both offer extensive notification options, and both maintain an API for a variety of flexible use cases. However, these surface distinctions are the extent of the similarities between the two. Nagios Core and Uptime.com serve very different user types, and offer different benefits. You can think of Nagios as your internal safeguard, and there are some challenges to scaling.
