GENI Monitoring

This page captures information and procedures related to the monitoring functions found in the GENI Monitoring system which is based on the architecture described in the Operational Monitoring wiki.

Operator and experimenter accounts are available to access this system. To get an account see the instructions in the Getting an Account page. If you already have an account and would like an overview of how to use the system, see the GENI Monitoring Overview page.

To see an example on how to monitoring experiment resources see the GENI Monitoring Resources Check page. Also available is a GENI Monitoring Tips page, which highlighting features for operators.

Monitoring Features

The GENI Monitoring system make the following types of information available:

  • Aggregates - Monitored GENI Aggregates data is available that includes details such as allocated nodes, links and slivers at that GENI Aggregate.
  • Users - Users information known to the GENI Clearinghouse (
  • Slices - All active slices, that may or may not have resources.
  • Slivers - All active reservations that compute and/or network resources actively allocated.
  • VLANs - All VLANs in use in GENI Environment, includes both sites and AL2S VLANs.
  • Nodes - Allocated GENI nodes, including VM and bare metal for all monitored aggregates.
  • Interfaces - All nodes defined for all aggregates being monitored. Note, ExoGENI keeps historical list of interfaces, while other aggregates only list active interfaces.
  • Links - Active GENI network connections which map VLANs between endpoints.
  • Check Stores - External Check that are run by GPO and by IMinds that capture status for specific type of information, such as up/down status or stitching support.
  • Authorities - GENI Clearinghouse ( provides valid user and slice information.
  • Aggregate Status - Site availability, available raw-pc and VM server statistics information. Also allows selecting aggregates by criteria like aggregate type or stitching. See Aggregate Status help page for more details.

GENI Monitoring API

The GENI Monitoring API system allows for access to collected data via RESTful calls to the collector. See the GENI Monitoring API page for instructions on example calls as well as available data types.


The GENI Monitoring system includes an Alerts system that generates notification based on monitoring criteria selected by the user. Currently Alerts can only be defined for GENI Monitoring Metrics. See the GENI Alerts page for instructions on defining alerts.

Also included is a Reporting system that generates reports based on monitoring data selected by the user. See the GENI Reporting page for instructions on defining and reports.

Note: Make sure to define "user" by specifying if a function is for Administrator, Operator and/or Experimenter roles.

Getting help

Account or Password Help

To get help on a monitoring issue, to get a new monitoring system account, or help with a forgotten password, please contact

Reporting a Problem

Is you are experiencing a problem with the monitoring system, please report the problem to the Global Meta Operations Center (GMOC) at See the GMOC Support page for instructions on reporting a problem or current calendar of outages. >>

Known Monitoring issues can be seen at the:

Scheduled and Unscheduled Outages

Monitoring outages can be seen at the GMOC locations:

Help pages

There are various areas in the monitoring system for which additional Help pages are available:

Email for GENI support or email me with feedback on this page!
Last modified 5 years ago Last modified on 05/31/17 11:23:23