I’ve seen my share of terrible status updates. As Founder and CEO of a SaaS platform for database performance management, VividCortex, I know the power of a great status update to build or destroy trust. Unfortunately, I see more bad status updates than good ones.
We just finished refactoring the code that we use for integrating DNS Check with services like Slack and PagerDuty. It felt good to take some of the bespoke code that had accumulated over the past couple years as integrations got added in and generalize it.
One of the main challenges we faced when developing Downtime Monkey was internationalization (or depending on your point of view: internationalisation, internacionalización, internasjonalisering). The aim was to provide our services to as many people as possible across the world - we learned a few things in the process and we thought we'd share some tips...
This article introduces an idea of stateless end-to-end tests using Google Chrome’s Lighthouse and automatic snapshots. This approach enables fast development experience and tests availability, performance, and quality regressions. For practical examples the article uses Treo.
As you already know, PM2 is a production process manager. In this post I will show you how and why PM2 is best fit to deploy microservices-oriented applications.
There’s this rumor going around that ChatOps was the invention of start-ups. I don’t know about you, but I can think of several enterprise IT/Ops teams who started using chat to coordinate and troubleshoot over a decade ago. (Ok, back then we called it “instant messenger”. But still.) So I hope I don’t spoil the rest of this post by letting you in on a little secret: if you’re in enterprise IT, you’re probably doing some ChatOps already.
React 16 introduces bunch of features, most interesting one is “error boundary”. In this article, we will see what is error boundary, and how to log errors from error boundary to Atatus.
The IT team at Samsung’s Austin R&D Center had the talent to be successful. Yet, there were bottlenecks getting in the way of their efficiency and productivity. Poor communication, lack of visibility, bad process, and unorganized tools were hampering their ability to support the rest of the organization and realize their full potential. Sound familiar?
