Service Monitoring Task Force Requirements


Current proposal has Grid Web services (or the hosting middleware instance in general) publishing metrics (monitoring data) to the messaging layer and a management GUI (browser-based) get that data from the messaging layer.

Client types


Grid Web services publishing metrics, WAN distributed.


Web GUI consuming data, WAN distributed users.

Destination types

Not yet clear, could be:

  • one topic for each middleware instance containing all monitoring data, regardless of metric type
  • one topic for each metric type per middleware instance
  • one topic for each Grid service per middleware instance

For a give destination type:

  • instances number: not known
  • messages content: monitoring data structured according to a schema
  • messages size: unclear at the moment
  • format of the messages body: XML
  • messages lifetime: 1-3 minutes
  • maximum latency: not known
  • permanent vs occasional connections: permanent connected producers and occasionally connected consumers
  • security requirements: unclear at the moment, expect to have some level of security

For a given destination instance:

  • producers, consumers, message rate: not known

For a given destination type:

  • producers, consumers, message rate: not known

Programming Languages

Not known

Edit | Attach | Watch | Print version | History: r5 < r4 < r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r5 - 2011-04-01 - MassimoPaladin
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Main/MassimoPaladin All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback