Changes between Version 9 and Version 10 of OperationalMonitoring/Overview


Ignore:
Timestamp:
03/17/14 14:34:04 (9 years ago)
Author:
rirwin@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • OperationalMonitoring/Overview

    v9 v10  
    1212<table border="0" style="float:center">
    1313  <tr>
    14        <td> <img src="http://groups.geni.net/geni/attachment/wiki/OperationalMonitoring/Overview/aggregator_local_datastore_overview.png?format=raw" width="500" height="317"> </td>
     14       <td> <img src="http://groups.geni.net/geni/attachment/wiki/OperationalMonitoring/Overview/local_datastore_collector.png?format=raw" width="500" height="317"> </td>
    1515  </tr>
    16   <caption align="bottom"> <b> Architectural Highlight of an collector and a Local Datastore </b></caption>
     16  <caption align="bottom"> <b> Architectural Highlight of a Collector and a Local Datastore </b></caption>
    1717</table>
    1818}}}
    19 An collector can poll a variety of datastores and any subset of data within each datastore.  A monitoring application relies on an collectors for its data queries, so collectors poll whatever data is necessary to have sufficient data to support the attached monitoring applications (i.e., alerting, reporting, historical analysis, visualization). 
     19A collector can poll a variety of datastores and any subset of data within each datastore.  A monitoring application relies on a collector for its data queries, so collectors poll whatever data is necessary to have sufficient data to support the attached monitoring applications (i.e., alerting, reporting, historical analysis, visualization). 
    2020
    2121{{{
     
    3838Use case description: Track node compute utilization, interface, and health statistics for shared rack nodes, and allow operators to get notifications when they are out of bounds
    3939
    40 Use case implementation story: Node statistics are time-series data, and are either collected on the node and pushed to the compute aggregate, or polled from each node by the compute aggregate (doesn't matter for our purposes). Statistics end up in a local database on each rack. Any group of operators that wants to send notifications on these statistics runs an collector, which polls all racks of interest to that group. The collector shares current values with an alerting service, which sends alerts.
     40Use case implementation story: Node statistics are time-series data, and are either collected on the node and pushed to the compute aggregate, or polled from each node by the compute aggregate (doesn't matter for our purposes). Statistics end up in a local database on each rack. Any group of operators that wants to send notifications on these statistics runs a collector, which polls all racks of interest to that group. The collector shares current values with an alerting service, which sends alerts.
    4141
    4242{{{
     
    5555Use case description: Find out what slivers will be affected by a maintenance or outage of some resource, and get contact information for the owners of those slivers so targeted notifications can be sent
    5656
    57 Use case implementation story: Aggregates collect up-to-date information about what slivers exist and what resources they have reserved (including sliver details such as expiration time), and make this information available via a local datastore. GENI trust authorities (e.g. clearinghouses) collect up-to-date information about experimenters and their contact information, and make this information available via a local datastore. Operators who want to be able to get this information run an collector which can query the relevant datastores (since this is an on-demand real-time query, the collector doesn't need to be active all the time, though it may be). The collector data is used to run a report listing affected experimenters and their contact info.
     57Use case implementation story: Aggregates collect up-to-date information about what slivers exist and what resources they have reserved (including sliver details such as expiration time), and make this information available via a local datastore. GENI trust authorities (e.g. clearinghouses) collect up-to-date information about experimenters and their contact information, and make this information available via a local datastore. Operators who want to be able to get this information run a collector which can query the relevant datastores (since this is an on-demand real-time query, the collector doesn't need to be active all the time, though it may be). The collector data is used to run a report listing affected experimenters and their contact info.
    5858{{{
    5959#!html