Operations | Monitoring | ITSM | DevOps | Cloud

I’d like to take a moment to point out some of my favorite things that have come across my Twitter timeline in the last week, if you’d like to see more follow Stackery on twitter!

Kubernetes events are a resource type in Kubernetes that are automatically created when other resources have state changes, errors, or other messages that should be broadcast to the system. While there is not a lot of documentation available for events, they are an invaluable resource when debugging issues in your Kubernetes cluster. In this post we will learn how to look at events, learn about a few specific event types, and discuss how to monitor Kubernetes events.

What do a test engineer and a DevOps or SRE team member have in common? The reality is that different teams need to proactively understand what is happening in production at critical milestones along the software engineering delivery cycle. In the words of Abby Bangser, senior test engineer at Moo, “Testing has so much in common with Ops and SRE teams. We need to ask interesting questions of production. We need no more debates whether a bug gets fixed.

This article originally appeared in Jaxcenter. Canary deployments are a commonly-used DevOps practice for staggered rollouts, sending small updates to groups in order to catch and fix issues. Ultimately, experimenting with DevOps practices such as canary deployments can help IT (and IT operations) bridge the gap with the business and deliver more value, faster.

In our previous blog post we discussed the challenges with relying on external servers for downloading pre-build tools such as Curl, CLI, wget, Maven, Gradle, npm and others. We discussed how they can sometimes cause stability issues, also called “Environmental Issues”, that will break the build.

Monitoring your application from end to end is important for ensuring that core functionalities work as designed. Datadog’s browser tests help you verify that key user workflows—such as signing up for a new account—are consistent across devices and locations. Within these workflows, email often plays a key role in onboarding users and providing customers with important information about their accounts and application activity, such as profile changes and order confirmations.

At Rollbar, we care about reducing the time it takes developers to find and fix errors. This is why we’re making our integration with GitHub even stronger to provide more context around errors and reduce the mean time it takes to resolve them MTTR. Last year, we launched Code Context to show additional lines of code within each frame of the stack trace, reducing the back and forth between GitHub and Rollbar.

We’ve been busy over the last week rolling out new product features that make the cloud feel and perform as if it was right there in the building with you - specifically geographic storage and edge caching.