Operations | Monitoring | ITSM | DevOps | Cloud

Migrating to 2.0: the good, the bad & the ugly

The Sensu 2.0 release is dropping in October, and we’re already excited! As the version numbering implies, Sensu 2.0 includes significant changes from Sensu 1.x. Not only has the software been entirely re-engineered in Go — easing deployment significantly — the exposed APIs and internal data structures have changed to accommodate new features.

Raygun and Java: Better error monitoring with Breadcrumbs and more

Raygun Crash Reporting has supported the Java Framework since we launched. As a Java customer, you’ve always been able to catch errors pre and post-production, receive alerts, and provide one source of truth for errors on your whole team. Now, Raygun provides full feature support for Raygun4Java. Java customers now have access to all our favorite Raygun features, like Breadcrumbs, offline support, web service support, and sensitive data filtering.

Set Up for Success: Service Taxonomies in PagerDuty

It’s 2:37 a.m. on a Tuesday night, you’re asleep—but it’s also your turn to be on call. You receive a phone call from PagerDuty. Your partner hits you with a pillow in an attempt to wake you up. It worked. You groggily answer the call and hear your favorite robo-guy on the other end of the line.

Share Context With Collaboration: Suggested Query Boards

Nobody knows your services/infra better than you, not even Honeycomb. If there’s one maxim for Honeycomb, it’s that context is king. Context determines the questions you can ask. The only way to make complex systems truly tractable is to make all questions possible. Ergo: more context. Context everywhere. Context coming out of the walls. You should be awash in context.

Monitoring Server Performance

This is the first in a series on server monitoring. The primary focus of these posts is monitoring in a *nix environment. Monitoring servers is important. Whether it be finding an issue in a test environment prior to deploying or debugging an issue in production, we need access to information on our server to be able to tease apart what went wrong.

Minimize Risk with Continuous Integration (CI) and Deployment (CD)

Ahoy there. Continuous shipping: a concept many companies talk about but never get around to implementing. In the first post of this three-part series, we discussed the use case for continuous shipping. Let’s move on to part two: the integration and deployment stages of the continuous shipping process. Part three will wrap up the series with a look at the monitoring and feedback phases. All aboard that’s coming aboard.