As containers and orchestrators have surged in popularity, they have created highly dynamic environments with rapidly changing workloads—and the need for equally dynamic ways of monitoring them. After all, orchestration technologies like Kubernetes, DC/OS, and Swarm manage container workloads both at the node level and at the cluster level, which means that you need to gather insights from every layer to fully understand the state of your infrastructure.

Source maps are awesome. Namely, because they are used to display your original JavaScript while debugging, which is a lot easier to look at than minified production code. In a sense, source maps are the decoder ring to your secret (minified) code. However, they can be tricky to get working properly. If you’ve run into some trouble, the tips below will hopefully help you get everything in working order.

Service level objectives are an important tool for maintaining application performance, ensuring a consistent customer experience, and setting expectations about service performance for both internal and external users. We are very pleased to announce the availability of a new monitor uptime widget that makes it simple to monitor the status of your SLOs and communicate that status to your teams, executives, or external customers.

It is not uncommon to have multiple monitoring solutions for IT infrastructure these days as distributed architectures take hold for many enterprises. We often hear from Google Cloud Platform (GCP) customers that they use Stackdriver to monitor resources as well as Grafana and Prometheus for container monitoring. We’ve heard lots of requests from customers to be able to view Stackdriver data in Grafana effortlessly.

Growing up in Seattle, Washington, I had access to some of the best hiking in the world. If you want take on a challenge and climb a peak, then the Cascade and Olympic mountain ranges provide a variety of journeys for everyone regardless of skill level and starting point. We were taught at a very young age that everyone needed certain “essentials” before setting out to ensure safety and success.

The namespace support in 2.10 caused a regression with the registered global scope being evaluated for API permissions with filters. This release fixes the problem, next to a problem with Windows packages not fully starting up. There’s also a fixed oversight with not setting a default environment constant. This affects setups checking the SNI header in external load balancers.

Being among the first to be notified when tickets go on sale online for events with high demand is paramount if you hope to secure tickets. Given the lucrative Secondary Market that’s emerged for event tickets (especially for concerts and sporting events), it’s become increasing difficult to acquire tickets for these popular events.

With the newest updates to the StatusCake app you are now able to get a lot more done whilst on the go. We’ve added several features which we think will enhance the experience, and there’s a lot more to come over the next few weeks, so keep your eyes peeled!

This year at Sensu Summit, Fletcher Nichol and I gave a talk on systems architecture entitled Pull, don’t push: Architectures for monitoring and configuration in a microservices era. In this post, I’d like to reiterate and expand on some of the concepts in that presentation and make some more concrete recommendations for systems design in an era of complex distributed systems.

Eating your own dog food is a concept also referred to as dogfooding. This is when a company uses its own product which was made famous by Google and Microsoft who employ the tactic to test their products in real-world usage. Dogfooding can act as quality control, and can also be a kind of testimonial advertising. For leaders, it’s a way to truly understand what you have, help you set your future direction and understand the challenges your team face on a day to day basis.