I hear it all the time when talking to future BigPanda customers; “I’m not sure BigPanda can really help me correlate all these alerts together because our CMDB is very immature.” Or sometimes, they don’t even have a CMDB, and incorrectly assume this disqualifies them from meaningful noise reduction and alert correlation. I’m happy to tell you the same thing I tell the folks who are looking at BigPanda for the first time. “No CMDB? No problem!”.

There used to be a distinct, technical separation between terms such as AI and machine learning (ML) – but only while these technologies remained largely theoretical. As soon as they became practical in the real world, and then commodifiable into products, the marketers stepped in. Widespread overuse of the terms AI/ML in marketing have managed to thoroughly confuse the meanings of these words.

Last year at PagerDuty Summit 2018, we officially launched PagerDuty University (PDU), a training program that provides hands-on classroom training to current and prospective customers so they can get the most out of the PagerDuty platform. Since its debut, PDU has taught hundreds of learners how they can optimize their instances to minimize downtime and improve responders’ quality of on-call life, in addition to providing thought leadership best practices to customers around the globe.

Software vendors and analysts love to rattle off scary numbers about how many thousands of dollars per minute or hour an infrastructure outage will cost the typical company. Those numbers can be scary indeed; for example, Gartner quotes $5,400 per minute as the cost borne by a medium to large-sized retailer. Your company, however, is most likely not identical to the “typical” company on which the numbers are based.

In the IT world, support teams race to resolve incidents, ensuring that clients and stakeholders remain satisfied. Yet, many teams struggle to meet time-to-response goals due to ineffective alerting processes, human errors and sluggish procedures.

July 2019 Update introduces the option to opt-out for certain categories as well as some enhancements in the Web portal. You can now opt-in/out of certain categories under Settings -> Services & Systems. This works on a per-user basis and is useful when you do not want to receive certain alerts but your team members still need to get them. Another scenario is to listen in, meaning you see what is going on but all notifications can be muted.

No matter how you design your architecture or what technologies you implement, critical incidents will happen. When things go wrong, it is easy to get carried away and forget about the bigger picture. But your work isn’t done after you fix the immediate problem; now is the time to take a look at how the incident actually happened so that you can learn from it.

In a simpler world, incident response notifications would be a one-size-fits-all type of item. You could deliver the same notification to everyone with equally successful results. But in the real world, incident response messages must be nuanced. Unlike baseball hats or wristwatches, the messages you send to different stakeholders when an incident occurs need to be tailored to each category of recipient.

Auto-alert suppression management in OpsRamp delivers first-response actions to reduce redundant and noisy alerts. Learning-based first-response policies ensure that IT teams no longer have to create static rules for a target set of resources by configuring alarm thresholds, defining filter criteria, and specifying time intervals.