Earlier this year, as COVID-19 appeared, our global community of almost 800 employees became a fully remote workforce—effectively overnight. Now, all of us have had a taste of what it’s like to work from home all the time, from embracing the benefits of less time commuting and more time with our families, to the downsides of feeling isolated and missing seeing our colleagues in “real life.”
In this blog post series, I’ve explored the relationship between observability and a set of software delivery lifecycle practices that help organizations adopt DevOps practices and change their ways of working from being project centric to product-centric. I started with Site Reliability Engineering, then considered Value Stream Management (VSM) and finish with this post on Continuous Integration and Delivery (CI/CD). Defining Continuous Integration
In SCOM you can see the monitoring that generates your alerts (the contents of Health Explorer). While SCOM doesn’t always make it easy to get at the valuable context that this monitoring data provides, it is there and can help answer the "why" questions that often come up when looking at an alert in isolation.
This is the first in a two-part blog series deconstructing AIOps for ITOps leaders. If you gave me a dollar for every company that claims that they use “A.I.,” I’d be doing pretty well. But as a marketer, I can’t help but be a little skeptical about those claims. Let me explain.
This post outlines how to use Zabbix and iLert with multiple on-call teams, where each team is responsible for a set of host groups in Zabbix, and therefore, will only receive alerts for the services it is responsible for. But first, let’s start with the basic needs when being on-call.
This is the first in a series of posts we’ll be publishing on trends we’re seeing in the retail industry and how IT organizations tasked with deploying and maintaining flawless digital customer experiences can take advantage of PagerDuty to ensure always-on reliability. It’s been a tough year for retail.
Fiserv, the Fortune 500 payments and financial technology provider, needed to streamline and automate its IT incident management process to detect and fix issues earlier and more quickly. The incident management workflow was complex, primarily because mergers and acquisitions over the years had made Fiserv’s IT environment very heterogeneous. “The challenges we were facing were enormous,” IT Director Chris Kreps says.
When working with IoT (internet of things) devices one of the key issues is to keep track of the health of all installations. Most of the time, especially with smaller devices, the applications (firmwares) are flashed for a single time during setup and stay untouched at their location of action for a long while.
Last week I went camping with some friends. One of them did the shopping for all of us, so I sent him my share using a payment app. It took me less than 2 minutes to complete the transaction. A few years ago, a similar transaction would have me going to the bank to complete the task, or at a minimum, calling a bank teller and having him do it. Try to imagine a bank asking its customers to do any of these things today. It would probably lose all its customers in no time.
