<?xml version="1.0" encoding="ISO-8859-1"?>
<ns1:meme ns1:id="35" ns1:title="application monitoring" xmlns:ns1="http://www.memento.org"><ns1:author>Jaron Collis</ns1:author><ns1:memeContent><ns1:memenode><ns1:nodename>Core Concept</ns1:nodename><ns1:nodetext>To remotely monitor and forward system status information to a central operators centre.</ns1:nodetext><ns1:children><ns1:child>monitoring</ns1:child><ns1:child>aggregation</ns1:child></ns1:children></ns1:memenode><ns1:memenode><ns1:nodename>monitoring</ns1:nodename><ns1:nodetext>Achieved by adding sensors to each application component of interest, sensor data is aggregated by a collecting component &apos;MonitorBean&apos;</ns1:nodetext><ns1:children><ns1:child>concepts</ns1:child><ns1:child>visualisation</ns1:child></ns1:children></ns1:memenode><ns1:memenode><ns1:nodename>aggregation</ns1:nodename><ns1:nodetext>The refining of collected observations into a small set of service states reflecting current state of the system. This abstraction process is handled by a dedicated aggregator component configured by rules.</ns1:nodetext><ns1:children><ns1:child>service mapping</ns1:child><ns1:child>update model</ns1:child><ns1:child>communication channel</ns1:child></ns1:children></ns1:memenode><ns1:memenode><ns1:nodename>concepts</ns1:nodename><ns1:nodetext>Activities abstracted into concepts and organised into a hierarchy of visits, events &amp; tasks. By structuring at collect-time related activities appear together - rather than in separate text logs requiring post-processing.</ns1:nodetext><ns1:children><ns1:child>visits</ns1:child><ns1:child>events</ns1:child><ns1:child>tasks</ns1:child></ns1:children></ns1:memenode><ns1:memenode><ns1:nodename>visits</ns1:nodename><ns1:nodetext>All interactions by a particular user</ns1:nodetext></ns1:memenode><ns1:memenode><ns1:nodename>events</ns1:nodename><ns1:nodetext>Individual interactions, e.g. page requests, received datagrams</ns1:nodetext></ns1:memenode><ns1:memenode><ns1:nodename>tasks</ns1:nodename><ns1:nodetext>Operations performed by application in response to an event - each has a status code (OK, WARNING, CRITICAL)</ns1:nodetext></ns1:memenode><ns1:memenode><ns1:nodename>visualisation</ns1:nodename><ns1:nodetext>Collected information can be visualised in real-time through web interface</ns1:nodetext></ns1:memenode><ns1:memenode><ns1:nodename>service mapping</ns1:nodename><ns1:nodetext>Rules describe mapping between incoming information source and a particular service state</ns1:nodetext></ns1:memenode><ns1:memenode><ns1:nodename>update model</ns1:nodename><ns1:nodetext>Incoming monitored events (errors) may change the aggregator component&apos;s model, the service state moving from OK to an error state. </ns1:nodetext></ns1:memenode><ns1:memenode><ns1:nodename>communication channel</ns1:nodename><ns1:nodetext>Service states are written to a database which is asynchronously polled by a system daemon (e.g. Nagios) that sends the results to a network operations centre.</ns1:nodetext></ns1:memenode></ns1:memeContent><ns1:access>false</ns1:access><ns1:category>software</ns1:category><ns1:repository>1</ns1:repository><ns1:creationDate>2003-08-05T17:33:51.855+01:00</ns1:creationDate><ns1:lastModified>2003-10-08T15:42:14.746+01:00</ns1:lastModified><ns1:relatedMemes/><ns1:relatedLinks><ns1:link><ns1:label>Nagios</ns1:label><ns1:location>http://www.nagios.org</ns1:location></ns1:link></ns1:relatedLinks></ns1:meme>