Requirements for online monitoring software

(User Interface requirements)
  1. A viewer for collections of data up to the level of a subdetector should be provided.
  2. This viewer should run on special displays all the time for fast overall check of subdetector operations.
  3. An event display, specifically adapted for online monitoring should be available to check that everything is ok and especially to cross-check data in different subdetectors.
  4. This event display should have an "accumulate events" option to make a fast check for hot spots and holes in the subdetectors.
  5. The user interface software should be completely independent from implementations details on how to get monitoring data.Ideally every request of monitoring data or collections of monitoring data should be done with a unique URI to a server .
This last request may seem "strange", for this reason I will explain here in detail where it comes from.
I am implementing 1,2,3,4 for Tracker by building a tracker map . This can represent data like: This information is represented for the whole tracker in real time. But here is the problem: how can I represent this data if some of them are on a oracle database, other on a mysql database, other data come from daq, other must be computed on tier1, other must come somewhere from the grid... For this reason I am in favour of a standard interface between producer and consumer of monitoring information. The simplest standard interface to me seems to be by defining a Web address for each piece or collection of information that can be requested.For example ,if I need some module histogram computed at some time, I should be able to build a Web adress from these informations, send this to a Gateway and obtain the histogram from the Gateway. The Gateway will decide how to get the histogram:it can came from a database or be computed on the spot.