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?

Nothing fills out the “worst-case scenario” column quite like a data breach. For the countless teams out there who work hard to protect their customers’ data, the idea of compromising that trust is a nightmare. Data breaches are on a lot of minds lately with the 2017 Equifax data breach, which exposed personal data from 143 million American consumers. The company, security industry, and regulators have a huge task of working out the details on how something like this happens.