Over the last 12 months, we’ve seen growing momentum around several disruptive trends in the cloud SIEM market. One of the most pervasive and obvious developments for Logz.io is the frequency with which we encounter customers seeking to replace dated and legacy on-premises SIEMs with a solution such as our Cloud SIEM. The traditional provider that comes up most often is LogRhythm—for numerous different reasons.
When developing the new exception landing pages we recently launched (like insert exception link here), I wanted to pull some statistics from Reddit. While looking through various ways to integrate, I found an easy approach that I want to share with you in this post. You probably already know Reddit, the highly active social news aggregation and discussion forum. I've found myself using Reddit more and more over the last couple of years, with the dotnet subreddit in particular.
Lionel Ritchie thinks Sunday morning is easy. Ella Fitzgerald thinks living is easy when it’s summertime. Loving is easy too, according to Rex Orange County. I haven’t heard anyone sing about customer experience just yet (Alexa?). But every time I preorder my Starbucks latte so it’s waiting for me at the store on my way to work, I’m reminded just how important easy is. If easy is the on/off switch for great experience, then speed controls the volume.
A few weeks ago we had a major incident. We were releasing our Practical Guide to Incident Management, and after posting about it online an incident.io employee noticed that the page wasn’t loading. Just to set the scene, I’ve been at incident.io for 3 months and don’t have any experience of incidents in my previous role. When the team got paged I expected this to be one of those “follow along and learn how the wizards work their magic” exercises.
IT experts and techies are constantly devising new ways to do more with less in our rapidly evolving world. Traditional platforms monitoring and modern technological maintenance take a large portion of a conventional organization’s IT budget. This leaves limited resources to develop new standards-based and adaptive applications that fulfill core business demands.
To err is human. The process of software development can’t be error-free; fixing errors is part and parcel of building software applications. And, no matter how much you dislike those harsh error messages when your code fails and exits, you have to admit that they save you from a lot worse.
This post is the third in a series of deeper dive articles discussing DORA metrics. In previous articles, we looked at: The third metric we’ll examine, Change Failure Rate, is a lagging indicator that helps teams and organizations understand the quality of software that has been shipped, providing guidance on what the team can do to improve in the future.
