, view all tags
The CEMon service is responsible for providing information coming from the Computing Element (CE).

The "type" of information managed by CEMon is defined by plugins (also known as sensors) that can be plugged into the CEMon core engine.

For each plugin, one or more dialects (representing how the relevant information is rendered) are available.

Existing CEMon sensors are:


By implementing specific sensors, the CEMon service can also be configured to collect and provide other information types.

It is possible to interact with the CEMon service in a synchronous way (i.e. the client queries the CEMon service to get the required info) or asynchronously (i.e. the client can subscribe to get asynchronous notifications coming from theCEMon service). Moreover the CEMon administrator can configure predefined subscriptions, so the specified clients are automatically notified with asynchronous events, without the need of an explicit subscription.

Other existing CEMon sensors that can be plugged into CEMon include the one publishing GridICE information, the one publishing CREAM job status information, the one publishing CE information according the needs of the ReSS OSG project.

Specific policies and specific actions can be set on CEMon subscriptions. For example if is possible to define a subscriptions so that the client is notified only when certain conditions are satisfied (e.g. when the CE queue is empty or the number of enqueued jobs is less than a certain value).

-- MassimoSgaravatto - 2011-04-20

Edit | Attach | PDF | History: r2 < r1 | Backlinks | Raw View | More topic actions...
Topic revision: r1 - 2011-04-20 - MassimoSgaravatto
  • Edit
  • Attach
This site is powered by the TWiki collaboration platformCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback