The latest News and Information on DevOps, CI/CD, Automation and related technologies.
We’re constantly looking for new ways to help DevOps, SREs, and operations teams automate operations workflows, secure infrastructure and applications, and rapidly deliver their products at scale. This commitment to our customers — and yours! — led us to redesign the way you experience groups in xMatters.
A few years ago I’d just moved to London and started out at my first software job. I was having a great time building things and making new friends, and one evening a friend and I decided there was a new problem we wanted to solve: we really didn’t like the expenses software. We thought it was confusing and over-complex, and decided we could do better.
API Observability isn't exactly new, however it's popularity has seen rapid growth in the past few years in terms of popularity. API Observability using open source is different from regular API monitoring, as it allows you to get deeper and extract more valuable insights. Although it takes a bit more effort to set up, once you've got an observability infrastructure running it can be immensely helpful not only in catching errors and making debugging easier, but also in finding areas that can be optimized.
We try hard to make our products as intuitive and familiar as possible, but there will always be “advanced” options and rarely-used features. Giving users choice and control over their experience will naturally lead to features that are used less frequently or settings that only a small percentage of users will change. So how do we decide what order and prominence to give to these lesser-used features?