We wrote this article in response to a question asked in our Slack Community. Click here to join hundreds of technology leaders discussing best practices for incident response! ✨ We know a thing or two about incident response. As such, we're often asked to advise when companies are designing their incident response processes. A common question is "How do you design your incident severity levels?". It's a great question given how central they are to incident response!
Our brand new Google Analytics integration has just landed! Now you can benchmark your website performance on your real website analytics.
Great news for the SCOM community – SCOM 2022 is going to be released in the spring! SCOM isn’t going anywhere and it’s only getting better. We saw this proven in the Big SCOM Survey Results 2021 where more than half of respondents said they were going to increase their SCOM deployment to monitor more of their existing and new infrastructure.
Gone are the days where software development was slowed down by the top-down, water-fall approach for getting work done. The rigidity of this methodology made for a longer development lifecycle, and it affected the way software was created and deployed.
“I can’t get this website to load.” As common help requests go, this sort of ticket can cause any tech to roll their eyes in anticipation of wasting time on a wild goose chase. If example.com isn’t working for one of your users, it could be caused by any of a dozen or more points of failure—everything from the user making a simple typo to a major Internet outage.