One of the many features of OSS is that they’re great at monitoring network performance and alerting operators of any threshold breaches. Initially these thresholds were static. For example if the CPU utilisation on a router goes above x% then an alert gets raised.
But this technique has flaws in that there might be recurring peaks (such as 9am on Monday morning when everyone is synching their field data / jobs) that are normal and predictable yet raise alerts to operators.
When recently performing a review of Opmantek they showed how they had rolled the work of Igor Trubin and his SEDS concept into their solution.
Please check out the link above to learn how this simple, yet elegant solution can reduce false anomaly notifications and the corresponding operator interruptions. I especially like how Figure 7 shows an example of a deteriorating system long before reaching failure state.
What do you think? Do you have any other great predictive / anomaly / trending algorithms to recommend?
Have you ever had an OSS or BSS project that’s impacted by poor data quality? The problem of data integrity gets raised on almost every
“One of my favorite things about designing software is designing the defaults. The defaults define the experience for everyone out of the box. And, therefore,
Have you ever been tasked with mapping out the processes for the telco you work for? Either as a way of documenting current state, or
In the last week alone, I’ve had two potent reminders that the world of OSS is simply (pun intended) too complex. This manifests in many
Here at Passionate About OSS, we are exactly that – Passionate About OSS (Operational Support Systems). We’re also passionate about BSS, NMS, or any other names you call the tools that help to operationalise your network.
