Web Management Alert Risk Scoring for Availability Monitoring
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Administering web management software, particularly when implemented using a cloud platform, is challenging due to the high volume of alerts generated by various entities, which makes it difficult for administrative users to accurately determine the availability risk and severity of issues affecting the software.
Innovation Solution
Implementing an administrator system that assigns problem codes to alerts based on problem code conditions, determining a risk score for the web management software, and sending messages to administrative users when the availability risk exceeds a threshold.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If web management software is implemented using multiple executables and cloud platforms to provide comprehensive functionality, then the software's capability and versatility are improved, but the complexity of administering and monitoring the software increases
Solution Approach 1:
The patent segments the monitoring system into distinct functional components: alert generation modules distributed across multiple executables, a central alert aggregation service, and a separate risk assessment module. This segmentation allows each component to specialize in specific tasks, improving overall system capability while making administration more manageable through clear separation of concerns.
Solution Approach 2:
The patent introduces an intermediary alert aggregation service that sits between the distributed executables and administrative users. This intermediary consolidates alerts from multiple sources, applies risk scoring rules, and presents unified risk assessments to administrators, thereby reducing the complexity of monitoring a distributed system without sacrificing functional comprehensiveness.
2Measurement precision
If comprehensive monitoring of all software entities is performed to accurately determine availability risk, then the precision of risk assessment is improved, but the volume of alerts and processing requirements increase
Solution Approach 1:
The patent applies local quality by implementing risk scoring rules that are specific to different entity types and alert conditions. Instead of uniform monitoring, the system applies context-specific assessment criteria to different parts of the system (e.g., database entities versus web server entities), improving risk assessment accuracy while avoiding unnecessary processing of irrelevant alerts.
Solution Approach 2:
The patent changes parameters by transforming raw alert data into risk scores through configurable scoring rules. The system adjusts the state of alert information from unprocessed notifications to standardized risk assessments with numerical scores, enabling precise risk measurement while reducing the effective volume of alerts that administrators must evaluate by presenting only scored results.
3Measurement precision
If all alerts are processed and analyzed in detail to identify significant risks, then the precision of problem detection is improved, but the time required for analysis increases
Solution Approach 1:
The patent implements partial action by applying risk scoring rules selectively based on alert characteristics and configured thresholds. The system processes alerts in a prioritized manner, applying detailed analysis only to alerts that meet specific risk criteria, while applying faster assessment methods to lower-priority alerts. This approach maintains high detection precision for critical issues while reducing overall analysis time through selective processing intensity.
Data Source
AI summary
Various examples are directed to systems and methods for administering web management software. A system may access alert data describing a plurality of alerts generated by a cloud-implemented web management software and apply a set of problem code conditions to the alert data. Based on the applying of the set of problem code conditions to the alert data, the system may assign a first problem code to the first alert. The system may determine a risk score for the web management software based at least in part on a problem state for the web management software, where the problem state comprises at least the first problem code. The system may determine that the risk score for the web management software matches a threshold condition and send a problem message to a user computing device associated with a user, the problem message describing a problem state of the web management software.


