This week we’ll learn about the new Google Stackdriver core datasource in Grafana, dive into the new Postgres query editor and share some best practices.

Your monthly monitoring plan includes predefined number of monthly SMS messages which are used to notify you about outages. For some users this number may be low and for this reason we decided to write short tutorial how to add your own SMS provider which is limited only by available credit on your account. In this tutorial we will describe how to integrate with Nexmo but similar method could be applied for other SMS providers.

Mean Time To Response (MTTR) measures how long it takes a first responder to acknowledge an incident since it has occurred. There’s a lot of talk on minimizing MTTR. But take a look at the following data set. Which scenario do you prefer?

Blue-green deployment is a well-known pattern for updating software components by switching between simultaneously available environments or services. The context in which a blue-green deployment strategy is used can vary from switching between data centers, web servers in a single data center, or microservices in a Pivotal Cloud Foundry (PCF) deployment.

Traditionally in white-box monitoring, error reporting has been achieved with third party libraries, that catch and communicate failures to external services and notify developers whenever a problem occurrs. I’m here to argue that for managed services this can be achieved with less effort, no agents and without performance overhead.

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.