After 2020, there are only two types of businesses: those who have retained customers or grown, and those who lost customers to more nimble competitors. There are many reasons. The transition away from traditional retail, shifting customer expectations, and internal operations challenges due to increasing complexity all play their parts. However, the main reason is simple. 2020 affirmed that there’s no such thing as a non-digital business.

As the digital-first operating world evolves, IT organizations are struggling to decide which practices to maintain and which to phase out. This transition from a “plan/build/run” lifecycle to a more agile, team-oriented structure has become the catalyst for organizational conflict, challenging the very foundation of how companies should operate.

As organizations experience increasing complexity and expanding perimeters, IT professionals are looking to get a better understanding into their distributed software and hardware assets. IT teams need immediate access to detailed information in context of services and underlying assets they run on to make more intelligent decisions about their IT investments. Having asset visibility at their fingertips enables them to maximize cost savings, secure assets, and improve the employee experience.

AWS tags are a bit like flossing your teeth every day — or getting eight hours of sleep a night. Everyone agrees they’re good habits that will make life easier down the road. But sometimes life gets in the way, and those habits fall a little short. Most teams set out with the intention to tag their infrastructure, but in our experience, it’s rare that companies have a perfect, thorough AWS tagging strategy.

When I asked Charlie for permission to attend this year’s AICon (virtual, natch) I thought it would be a shoo-in; learning’s part of my OKRs after all. But he never makes things easy and his ‘yes’ came with a caveat that’s typical when dealing with him. This time, he claimed he didn’t have the budget for the ticket (a likely story!) and I’d have to find another way to get one.

It’s the end of AWS Lambda support for Node.js v10. AWS Lambda support for Node.js 10 is due to end in August 2021. It’s time to switch! In this article, we’re discussing and comparing the differences of working with Node.js 10 and Node.js 14 + AWS Lambda, the impacts, and benefits of this change. AWS Lambda supports multiple versions of programming language runtimes, but not forever.

The ransomware campaign against the Colonial Pipeline highlights the dangers and real-life consequences of cyberattacks. If you want to understand how to use Splunk to find activity related to the DarkSide Ransomware, we highly recommend you first read “The DarkSide of the Ransomware Pipeline” from Splunk’s Security Strategist team. In short, according to the FBI, the actors behind this campaign are part of the “DarkSide” group.

That's a wrap! We hosted "WTF is Incident Management" on May 12, 2021. We invited four very knowledgeable panelists to discuss how they define incident management, what changes they'd make if they could start again from scratch, how to manage team stress after an incident, and other subjects. Our panelists were: host Matt Stratton (Staff Developer Advocate at Pulumi), Emily Ruppe (Incident Commander at Twilio), Alina Anderson (Sr.

Server monitoring is important for optimum server performance to ensure no disruptions to your business. However, server performance monitoring can be dispersed and complex. Keeping an eye on everything has become an uphill battle. Information on the server allows you to better understand what went wrong. Tools, like Retrace, that make this uphill battle more streamlined and manageable. Let’s learn how to monitor server performance.