Today we are releasing Graylog v2.5.1 to fix a few bugs. Many thanks to our community for reporting issues and contributing fixes!

Observing modern applications is challenging. Microservices allow for applications that are not only more distributed but are made up of a number of different languages, frameworks, and backend services. DevOps teams have far greater flexibility in where and how they deploy applications,but when it comes time to collect logs, this flexibility can quickly become a hurdle.

Although technology continues to evolve, the processes that support Information Technology Service Management (ITSM) have remained relatively unchanged for several decades. One of the main challenges to delivering high-quality IT services in this long-established approach is reactivity – that is, focusing on incident management as a means to resolve something that should never have happened in the first place.

Dotcom-Monitor continues to add advanced features and functionality to its unparalleled monitoring and testing platforms. The most recent enhancement to announce is console logging, a boost to the EveryStep Web Recorder.

A massive data breach at Marriott and Starwood Hotels and Resorts has put the General Data Protection Regulation (GDPR) back in the spotlight. As the hotel chain faces record fines under the GDPR, privacy experts are again extolling the importance of secure log management practices to avoid suffering a similar fate as Starwood.

Over the last couple of weeks, we’ve prioritized some sustaining product goals to polish the codebase and update some big ticket dependencies. Among those updates were: React, Redux, and Webpack - the biggies. The first two were pretty painless and inspired the confidence to approach updating Webpack from v2 to v4 like maybe no big deal! Though confidence level was on high, I felt a slight chill and a twinge of doubt by the prospect of making changes to our build configs.

Last week, I wrote A Beginner’s Guide to Deadlocks in Amazon RDS. This week, I’d like to lay out my 10 years of experience about how to avoid deadlocks altogether. Often times, this will be out of the hands of operations people, but you can still move for dev changes based on issues in production. The more knowledgeable you are about deadlocks in general, the more they will lean on you as a resource with wisdom, not a totalitarian barking rules.

2018 has been an amazing year for RapidSpike, we have been super busy helping people deliver awesome website performance and we’ve built some amazing new features. Here’s this year’s rundown on our brilliant digital experience monitoring platform.

At least 10 major data breaches occurred in 2018 including Facebook, Google Plus, WordPress, and healthcare sectors. The surge in breaches proves we need to do a better job detecting foul play. User data and our own IP are crucial assets to safeguard in this environment. We also observed major downtime incidents from companies like Facebook and Microsoft.