automation of decision making for monitoring systems
DESCRIPTION
Automation of decision making for monitoring systems. Włodzimierz Funika, Filip Szura. Motivation. Main issue Automation of N etwork monitoring Rules Understandable Easy to create External Engine (Jboss Drools) Usage of external monitoring systems - PowerPoint PPT PresentationTRANSCRIPT
Włodzimierz Funika, Filip Szura
Automation of decision making for monitoring systems
MotivationMain issue
Automation of Network monitoringRules
Understandable Easy to createExternal Engine (Jboss Drools)
Usage of external monitoring systemsExtension of existing solutions (Zabbix)
Actions described as:Java codeUnix action scripts
System architectureSystem divided into
three components: Server
Decision component
Local-Monitor Data collector
GUI Presentation
Network 1, 2 – monitored networks
RMI (Remote Method Invocation) – standard communication between system components
System architecture
Saude-Net GUI Configuration provided
during work by the user
Web page generation, communication over RMI
Saude-Net Server Configuration stored in
XML Rules stored in DRL file Rules engine
Saude-Net Local-Monitor Dependent on external
monitoring system XML configuration Connection over RMI No actions provided for
user during work
System detailsSaude-Net(System for automation of decision
making for monitoring systems)Designed for small and medium size networksMultiple actions for resources under monitoringFully configurableRule and actions management is easy for
network administratorSystem choose the best action when event
occurred in the monitored networkCan manage multiple networks
Monitoring Tool (Zabbix)
Saude-Net Local-Monitor Data
From Monitoring Tools
Saude-Net Server
Knowledge Engine
Demo
List of available actions
Trigger the best action
GUI component
System detailsPreference tuning value (PTV)
Preference value (PV)
Ns - number of services which are currently modified
D - number of instances of any action
Iw - sum of instances of a specifed action as the best (+1) and other (-1)
PTV= NsD
x const xIwD
PV = oldPV + PTV
System featuresClassic monitoring systems
Network events are reported to network administrator
Our solutionSystem automatically react on reported
failuresReaction based on actual network snap-shot
and knowledgeIn effect, system is able to perform any
action when network event occurredAction described as Unix action scriptShort Java script located in rule
ImplementationServer component
Calculating preferences for actionsInvoke actionsStores actual view of network and actual knowledge baseValidation of rules
Local-Monitor component
Acquiring data from external monitoring systems (Zabbix)
Sending data to Saude-Net server
GUI component Create rules Simple validation Data representation Form generation
Presentation component
Extension of Local-Monitor Simple simulator of network
ImplementationUsed technologies:
Java – available for most operating systems, the same data representation in different systems
JSF – less code than in JSP Jboss Drools – easy to use, available for java XML – required by Spring Spring Framework – allows for Dependency Injection,
provides a connection to database
Component architectureSystem divided into separate components
Web-based GUISystem management by web pages
ConclusionsAchievements
Automatic actions on network failuresActions described by rulesEasy configuration of rules and actionsDistributed architecture
LimitationsAll components must be implemented in JavaConfiguration may not be changed during system workRules are created only by administrator, our system is
not allowed to create its own rules.Future work
System should learn automatically from actions taken by the administrator
Extensions of Saude-Net system securityRedundancy of Saude-Net server component
More details
Poster number: 6
Thank you for your attention!