SCEPTOR

Sceptor is capable of providing a way to fine-tune the correlations between events from different systems. The analysis is based on the rate of events occurrences and pauses between them, number of the same-type events, their sequence and attributes, and defined timeframe.

During setup, both manual and automatic definition of events’ quarantine can be specified. Settings specify the sequence of operations execution to enable execution of diagnostic scenarios with saving their outputs within the event context.

The system uses horizontal scaling model for the event management, which enables load balancing and load distribution between several instances.

Unified registration and reporting database is also a universal report builder. It supports table and static representations of data, stored in the database. This tool allows to build charts and reports of any complexity, as well as to perform the detailed root cause analysis for the events received by the system.

Logging allows making immediate and detailed registration of actions, performed within the system. Processing of the received information allows getting consolidated figures, analyzing trends and making required checks. Activity separation enables instant search and access to the necessary information.

Permissions engine enables flexible, precise and detailed tuning of interactions with the system using the defined set of rules. In common, a setup can be performed for specific system objects and for system scenarios.

Advanced Correlation Engine

Features:

• Incident subscription mechanism supporting user-defined filters.
• Incident classification based on configurable reference table with hierarchical structure.
• Automated event priority definition.
• Expandable “floating” attribute model for the events.
• Notifications with escalation, based on escalation matrix, built in accordance to network-areas and severity of services fault.
• Notification transporting (e-mail, sms, call, push), based on the time of day, day of the week and date/time.
• SLA exceeding threshold indication.
• Storing files in an event context.
• Double-ended synchronization with Trouble.
• Ticket system.