Difference: WebDocumentation (1 vs. 19)

Revision 192009-06-15 - DanieleCesini

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Overview

WMSMonitor is a monitoring tool collecting information from a cluster of distributed WMS instances about service status and Job Flow. Collected information is aggregated and presented exploiting two main keys: single WMS instance information and Virtual Organization (VO) information.
These two information aggregation keys lead to two parallel branches of metrics presentation in the GUI:
Line: 21 to 21
 
  • DB ANALYZER: a python daemon that checks the latest status of the cluster and sends notification to a nagios server providing mail and/or sms alert notifications.

  • DB RE-FILLER: I can happen for various reasons (i.e. high dg20 file queue on the wms) that data for some jobs are not available on the LB database when the sensors are triggered on the LB servers, resulting in a loss of data in the wmsmonitor server db. The data collector does its best trying to fix the situation, but if data does not reach the lb server in a reasonable time (about ten hours by default, a configurable timeout) the collector gives up and a manual reconstruction is needed. This utility perform such a reconstruction.
Added:
>
>
wmsmon-arch.png
 

Changed:
<
<
wmsmon_arch_1.4.png
>
>
 

Line: 31 to 33
 

Working On

  • Implementation of estimates of job latency
  • ICE sensors 
Changed:
<
<
  • WMS Load Balancing system 
>
>
  • Apache ActiveMQ communication system
  • DB redesigna
  • Performance improvement
 
Changed:
<
<
META FILEATTACHMENT attachment="wmsmon_arch_1.4.png" attr="" comment="" date="1234532180" name="wmsmon_arch_1.4.png" path="wmsmon_arch_1.4.png" size="40297" stream="wmsmon_arch_1.4.png" user="Main.DanieleCesini" version="1"
>
>
META FILEATTACHMENT attr="" autoattached="1" comment="" date="1245057364" name="wmsmon-arch.png" path="wmsmon-arch.png" size="50269" user="Main.DanieleCesini" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="" date="1234532181" name="wmsmon_arch_1.4.png" path="wmsmon_arch_1.4.png" size="40297" user="Main.DanieleCesini" version="1"

Revision 182009-02-13 - DanieleCesini

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Overview

WMSMonitor is a monitoring tool collecting information from a cluster of distributed WMS instances about service status and Job Flow. Collected information is aggregated and presented exploiting two main keys: single WMS instance information and Virtual Organization (VO) information.
These two information aggregation keys lead to two parallel branches of metrics presentation in the GUI:
Line: 10 to 10
 
  • You need the certificate and flash installed on your browser
  • Basic Knowledge of WMSLB architecture
Changed:
<
<

Tool Architecture Overview

>
>

Tool Architecture

 WMSMonitor is composed by the following main components:
  • WMSMonitor SERVER: WMSMonitor runs on a dedicated server machine with a Mysql database to store data, Php, Apache and Python on it.
Added:
>
>
 
  • WMSLB INSTANCES: A cron on the WMSMonitor server collects data from each WMS/LB instance executing sensors on them. These sensors send data to the WMSMonitor server using snmp. Job flow rates are calculated using direct queries to the LB database.
Added:
>
>
 
  • WEB PUBLISHING: Exploiting php based functions, data are retrieved from a local Mysql DB, aggregated and published on a graphical user interface through a (secure) http protocol. Charts are implemented exploiting "Open Flash Chart", an open source flash based set of libraries.
Added:
>
>
 
  • DB ANALYZER: a python daemon that checks the latest status of the cluster and sends notification to a nagios server providing mail and/or sms alert notifications.
Added:
>
>
 
  • DB RE-FILLER: I can happen for various reasons (i.e. high dg20 file queue on the wms) that data for some jobs are not available on the LB database when the sensors are triggered on the LB servers, resulting in a loss of data in the wmsmonitor server db. The data collector does its best trying to fix the situation, but if data does not reach the lb server in a reasonable time (about ten hours by default, a configurable timeout) the collector gives up and a manual reconstruction is needed. This utility perform such a reconstruction.

Revision 172009-02-13 - DanieleCesini

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Overview

WMSMonitor is a monitoring tool collecting information from a cluster of distributed WMS instances about service status and Job Flow. Collected information is aggregated and presented exploiting two main keys: single WMS instance information and Virtual Organization (VO) information.
These two information aggregation keys lead to two parallel branches of metrics presentation in the GUI:
Changed:
<
<
  1. WMS view focusing on WMS cluster status and performance monitoring. In the first branch we find a main page WMSMonitor main reporting an overview of most important status variables for all WMS instances monitored through which we can access a Specific WMSLB Instance Detailed data page with detailed data for each monitored WMS instance including Job flow rates between internal components other than system status indicator measuremnts.
  2. VOView providing Job flow statistics using the VOs as aggregation criterion. VOView and VO Stats Page
>
>
  1. WMS view focusing on WMS cluster status and performance monitoring. In the first branch we find a main page WMSMonitor main reporting an overview of most important status variables for all WMS instances monitored through which we can access a Specific WMSLB Instance Detailed data page with detailed data for each monitored WMS instance including Job flow rates between internal components other than system status indicator measuremnts.
  2. VOView providing Job flow statistics using the VOs as aggregation criterion. VOView and VO Stats Page
 Starting from WMSMonitor version 2.0, clicking on "WMS view" or "VO View" tabs, a window menu let you navigate through all available WMSmonitor web pages for each WMS instance or VO respectively.
Deleted:
<
<
 

User Requirements

  • You need the certificate and flash installed on your browser
  • Basic Knowledge of WMSLB architecture
Line: 12 to 11
 
  • Basic Knowledge of WMSLB architecture

Tool Architecture Overview

Added:
>
>
WMSMonitor is composed by the following main components:
 
  • WMSMonitor SERVER: WMSMonitor runs on a dedicated server machine with a Mysql database to store data, Php, Apache and Python on it.
Changed:
<
<
  • WMSLB INSTANCES: A cron on the WMSMonitor server collects data from each WMS/LB instance executing python compiled functions on them. This python executable on each WMS/LB instance implements sensors and send data to the WMSMonitor server using snmp. Job flow rates are calculated using direct queries to the LB database.
  • WEB PUBLISHING: Exploiting php based functions, data are retrieved from a local Mysql DB, aggregated and published on a graphical user interface through a secure https protocol. Charts are implemented exploiting "Open Flash Chart", an open source flash based set of libraries.
>
>
  • WMSLB INSTANCES: A cron on the WMSMonitor server collects data from each WMS/LB instance executing sensors on them. These sensors send data to the WMSMonitor server using snmp. Job flow rates are calculated using direct queries to the LB database.
  • WEB PUBLISHING: Exploiting php based functions, data are retrieved from a local Mysql DB, aggregated and published on a graphical user interface through a (secure) http protocol. Charts are implemented exploiting "Open Flash Chart", an open source flash based set of libraries.
 
  • DB ANALYZER: a python daemon that checks the latest status of the cluster and sends notification to a nagios server providing mail and/or sms alert notifications.
Changed:
<
<
  • DB RE-FILLER: I can happen for various reasons (i.e. high dg20 file queue on the wms) that data for some jobs are not available on the LB database when the sensors are triggered on the LB servers, resulting in a loss of data in the wmsmonitor server db. The data collector does its best trying to fix the situation, but if data does not reach the lb server in a reasonable time (about ten hours by default, a configurable timeout) the collector gives up and a manual reconstruction is needed. This utility perform such a reconstruction.
>
>
  • DB RE-FILLER: I can happen for various reasons (i.e. high dg20 file queue on the wms) that data for some jobs are not available on the LB database when the sensors are triggered on the LB servers, resulting in a loss of data in the wmsmonitor server db. The data collector does its best trying to fix the situation, but if data does not reach the lb server in a reasonable time (about ten hours by default, a configurable timeout) the collector gives up and a manual reconstruction is needed. This utility perform such a reconstruction.

wmsmon_arch_1.4.png

 
Changed:
<
<

Working On

>
>

Working On

 
  • Implementation of estimates of job latency
Deleted:
<
<
  • ICE sensors
  • WMS Load Balancing system
 \ No newline at end of file
Added:
>
>
  • ICE sensors 
  • WMS Load Balancing system 

META FILEATTACHMENT attachment="wmsmon_arch_1.4.png" attr="" comment="" date="1234532180" name="wmsmon_arch_1.4.png" path="wmsmon_arch_1.4.png" size="40297" stream="wmsmon_arch_1.4.png" user="Main.DanieleCesini" version="1"

Revision 162009-02-13 - DanieleCesini

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Overview

Changed:
<
<
WMSMonitor is a monitoring tool collecting information from a cluster of distributed WMS instances about service status and Job Flow. Collected information is aggregated and presented exploiting two main keys: single WMS instance information and Virtual Organization (VO) Job Flow information.
These two information aggregation keys lead to two parallel branches of metrics presentation in the GUI:
>
>
WMSMonitor is a monitoring tool collecting information from a cluster of distributed WMS instances about service status and Job Flow. Collected information is aggregated and presented exploiting two main keys: single WMS instance information and Virtual Organization (VO) information.
These two information aggregation keys lead to two parallel branches of metrics presentation in the GUI:
 
  1. WMS view focusing on WMS cluster status and performance monitoring. In the first branch we find a main page WMSMonitor main reporting an overview of most important status variables for all WMS instances monitored through which we can access a Specific WMSLB Instance Detailed data page with detailed data for each monitored WMS instance including Job flow rates between internal components other than system status indicator measuremnts.
  2. VOView providing Job flow statistics using the VOs as aggregation criterion. VOView and VO Stats Page
Starting from WMSMonitor version 2.0, clicking on "WMS view" or "VO View" tabs, a window menu let you navigate through all available WMSmonitor web pages for each WMS instance or VO respectively.

Revision 152009-01-30 - DaniloDongiovanni

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Overview

WMSMonitor is a monitoring tool collecting information from a cluster of distributed WMS instances about service status and Job Flow. Collected information is aggregated and presented exploiting two main keys: single WMS instance information and Virtual Organization (VO) Job Flow information.
These two information aggregation keys lead to two parallel branches of metrics presentation in the GUI:
Line: 15 to 15
 
  • WMSMonitor SERVER: WMSMonitor runs on a dedicated server machine with a Mysql database to store data, Php, Apache and Python on it.
  • WMSLB INSTANCES: A cron on the WMSMonitor server collects data from each WMS/LB instance executing python compiled functions on them. This python executable on each WMS/LB instance implements sensors and send data to the WMSMonitor server using snmp. Job flow rates are calculated using direct queries to the LB database.
  • WEB PUBLISHING: Exploiting php based functions, data are retrieved from a local Mysql DB, aggregated and published on a graphical user interface through a secure https protocol. Charts are implemented exploiting "Open Flash Chart", an open source flash based set of libraries.
Changed:
<
<
  • DB ANALYZER: a python daemon that check the latest status of the cluster and send notification to a nagios server providing mail and/or sms allert notofications.
  • DB RE-FILLER: I can happen for various reasons (i.e. high dg20 file queue on the wms) that data for some jobs are not available on the LB database when the sensors are triggered on the LB servers, resulting in a loss of data in teh wmsmonitor sevrver db. The data collector does its best trying to fix the situation, but if data does not reach the lb server in a reasonable time (about ten hours by default, a configurable timeout) the collector gives up and a manula recostruction is need. This utility perform such a reconstruction.
>
>
  • DB ANALYZER: a python daemon that checks the latest status of the cluster and sends notification to a nagios server providing mail and/or sms alert notifications.
  • DB RE-FILLER: I can happen for various reasons (i.e. high dg20 file queue on the wms) that data for some jobs are not available on the LB database when the sensors are triggered on the LB servers, resulting in a loss of data in the wmsmonitor server db. The data collector does its best trying to fix the situation, but if data does not reach the lb server in a reasonable time (about ten hours by default, a configurable timeout) the collector gives up and a manual reconstruction is needed. This utility perform such a reconstruction.
 

Working On

  • Implementation of estimates of job latency
  • ICE sensors
Added:
>
>
  • WMS Load Balancing system
 \ No newline at end of file

Revision 142009-01-29 - DaniloDongiovanni

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Overview

WMSMonitor is a monitoring tool collecting information from a cluster of distributed WMS instances about service status and Job Flow. Collected information is aggregated and presented exploiting two main keys: single WMS instance information and Virtual Organization (VO) Job Flow information.
These two information aggregation keys lead to two parallel branches of metrics presentation in the GUI:
  1. WMS view focusing on WMS cluster status and performance monitoring. In the first branch we find a main page WMSMonitor main reporting an overview of most important status variables for all WMS instances monitored through which we can access a Specific WMSLB Instance Detailed data page with detailed data for each monitored WMS instance including Job flow rates between internal components other than system status indicator measuremnts.
Changed:
<
<
  1. VOView providing Job flow statistics using the VOs as aggregation criterion. VOView and VO Stats Page
>
>
  1. VOView providing Job flow statistics using the VOs as aggregation criterion. VOView and VO Stats Page
Starting from WMSMonitor version 2.0, clicking on "WMS view" or "VO View" tabs, a window menu let you navigate through all available WMSmonitor web pages for each WMS instance or VO respectively.
 

User Requirements

  • You need the certificate and flash installed on your browser
Line: 18 to 20
 

Working On

  • Implementation of estimates of job latency
Deleted:
<
<
  • DB restructuring
  • Job flow rate measurements using wms data only in case of hgh dg20 queues, in order to avoid data loss in LB queries
 
  • ICE sensors

Revision 132009-01-29 - DaniloDongiovanni

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Overview

Changed:
<
<
WMSMonitor is composed by a main page reporting an overview of most important status variables for all WMS instances monitored
and a page with detailed data for each specific instance.
Deatails for a wms instance includes Job flow rates between internal components other than system status indicator measuremnts. 
A VOView is also provided to obtain usage statistics by the VOs.
Follow the following links for further details on what is provided by the monitor.

>
>
WMSMonitor is a monitoring tool collecting information from a cluster of distributed WMS instances about service status and Job Flow. Collected information is aggregated and presented exploiting two main keys: single WMS instance information and Virtual Organization (VO) Job Flow information.
These two information aggregation keys lead to two parallel branches of metrics presentation in the GUI:
  1. WMS view focusing on WMS cluster status and performance monitoring. In the first branch we find a main page WMSMonitor main reporting an overview of most important status variables for all WMS instances monitored through which we can access a Specific WMSLB Instance Detailed data page with detailed data for each monitored WMS instance including Job flow rates between internal components other than system status indicator measuremnts.
  2. VOView providing Job flow statistics using the VOs as aggregation criterion. VOView and VO Stats Page
 

User Requirements

  • You need the certificate and flash installed on your browser
Line: 15 to 13
 
  • WMSMonitor SERVER: WMSMonitor runs on a dedicated server machine with a Mysql database to store data, Php, Apache and Python on it.
  • WMSLB INSTANCES: A cron on the WMSMonitor server collects data from each WMS/LB instance executing python compiled functions on them. This python executable on each WMS/LB instance implements sensors and send data to the WMSMonitor server using snmp. Job flow rates are calculated using direct queries to the LB database.
  • WEB PUBLISHING: Exploiting php based functions, data are retrieved from a local Mysql DB, aggregated and published on a graphical user interface through a secure https protocol. Charts are implemented exploiting "Open Flash Chart", an open source flash based set of libraries.
Changed:
<
<
  • DB ANALYZER: a python daemon that check the latest status of the cluster and send notification  to a nagios server providing mail and/or sms allert notofications.
  • DB RE-FILLER: I can happen for various reasons (i.e. high dg20 file queue on the wms) that data for some jobs are not available on the LB database when the sensors are triggered on the LB servers, resulting in a loss of data in teh wmsmonitor sevrver db.  The data collector does its best trying to fix the situation, but if data does not reach the lb server in a reasonable time (about ten hours by default, a configurable timeout)  the collector gives up and a manula recostruction is need. This utility perform such a reconstruction.
>
>
  • DB ANALYZER: a python daemon that check the latest status of the cluster and send notification to a nagios server providing mail and/or sms allert notofications.
  • DB RE-FILLER: I can happen for various reasons (i.e. high dg20 file queue on the wms) that data for some jobs are not available on the LB database when the sensors are triggered on the LB servers, resulting in a loss of data in teh wmsmonitor sevrver db. The data collector does its best trying to fix the situation, but if data does not reach the lb server in a reasonable time (about ten hours by default, a configurable timeout) the collector gives up and a manula recostruction is need. This utility perform such a reconstruction.
 

Working On

  • Implementation of estimates of job latency
Changed:
<
<
  • Old lcg-rb monitoring (probably will not be done because of the decommissioning of lcg-rb )
  • DB restructoring
>
>
  • DB restructuring
 
  • Job flow rate measurements using wms data only in case of hgh dg20 queues, in order to avoid data loss in LB queries
  • ICE sensors
Deleted:
<
<
  • JOBdir sensor
  • Geographically distrubuted WMS/LB cluster monitoring
 \ No newline at end of file

Revision 122008-09-16 - DanieleCesini

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Overview

WMSMonitor is composed by a main page reporting an overview of most important status variables for all WMS instances monitored
and a page with detailed data for each specific instance.
Deatails for a wms instance includes Job flow rates between internal components other than system status indicator measuremnts. 
A VOView is also provided to obtain usage statistics by the VOs.
Follow the following links for further details on what is provided by the monitor.

Changed:
<
<
>
>
 

User Requirements

  • You need the certificate and flash installed on your browser

Revision 112008-09-16 - DanieleCesini

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Overview

Changed:
<
<
WMSMonitor is composed by a main page reporting an overview of main status variables for all WMS instances monitored
and a page with detailed data for each specific instance.
>
>
WMSMonitor is composed by a main page reporting an overview of most important status variables for all WMS instances monitored
and a page with detailed data for each specific instance.
Deatails for a wms instance includes Job flow rates between internal components other than system status indicator measuremnts. 
A VOView is also provided to obtain usage statistics by the VOs.
Follow the following links for further details on what is provided by the monitor.
 
Changed:
<
<
>
>
 

User Requirements

  • You need the certificate and flash installed on your browser
Line: 13 to 13
 

Tool Architecture Overview

  • WMSMonitor SERVER: WMSMonitor runs on a dedicated server machine with a Mysql database to store data, Php, Apache and Python on it.
Changed:
<
<
  • WMSLB INSTANCES: A cron on the WMSMonitor server collects data from each WMS/LB instance executing on it a python compiled function on them. This python executable on each WMSLB instance implements sensors and send data to the WMSMonitor server using snmp.
  • WEB PUBLISHING: Exploiting php based functions, data are retrieved from a local Mysql DB, aggregated and published on a graphical user interface through a secure https protocol. Charts are implemented exploiting "Open Flash Chart", an open source flash based set of libraries.
  • CUMULATIVE STATS: plot reporting on all wms in use by a specific VO
>
>
  • WMSLB INSTANCES: A cron on the WMSMonitor server collects data from each WMS/LB instance executing python compiled functions on them. This python executable on each WMS/LB instance implements sensors and send data to the WMSMonitor server using snmp. Job flow rates are calculated using direct queries to the LB database.
  • WEB PUBLISHING: Exploiting php based functions, data are retrieved from a local Mysql DB, aggregated and published on a graphical user interface through a secure https protocol. Charts are implemented exploiting "Open Flash Chart", an open source flash based set of libraries.
  • DB ANALYZER: a python daemon that check the latest status of the cluster and send notification  to a nagios server providing mail and/or sms allert notofications.
  • DB RE-FILLER: I can happen for various reasons (i.e. high dg20 file queue on the wms) that data for some jobs are not available on the LB database when the sensors are triggered on the LB servers, resulting in a loss of data in teh wmsmonitor sevrver db.  The data collector does its best trying to fix the situation, but if data does not reach the lb server in a reasonable time (about ten hours by default, a configurable timeout)  the collector gives up and a manula recostruction is need. This utility perform such a reconstruction.
 

Working On

Deleted:
<
<
  • Packaging for current release deployment
 
  • Implementation of estimates of job latency
  • Old lcg-rb monitoring (probably will not be done because of the decommissioning of lcg-rb )
Changed:
<
<
  • Mail notifications system implementation
>
>
  • DB restructoring
  • Job flow rate measurements using wms data only in case of hgh dg20 queues, in order to avoid data loss in LB queries
  • ICE sensors
  • JOBdir sensor
  • Geographically distrubuted WMS/LB cluster monitoring

Revision 102008-06-25 - DanieleCesini

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Overview

WMSMonitor is composed by a main page reporting an overview of main status variables for all WMS instances monitored
and a page with detailed data for each specific instance.

Changed:
<
<
>
>
 

User Requirements

Line: 13 to 13
 

Tool Architecture Overview

  • WMSMonitor SERVER: WMSMonitor runs on a dedicated server machine with a Mysql database to store data, Php, Apache and Python on it.
Changed:
<
<
  • WMSLB INSTANCES: A cron on the WMSMonitor server collects data from each WMS/LB instance executing on it a python compiled function on them. This python executable on each WMSLB instance implements sensors and send data to the WMSMonitor server using a soap module.
  • WEB PUBLISHING: Exploiting php based functions, data are retrieved from a local Mysql DB, aggregated and published on a graphycal user interface through a secure https protocol. Charts are implemented exploiting "Open Flash Chart", an open source flash based set of libraries.
>
>
  • WMSLB INSTANCES: A cron on the WMSMonitor server collects data from each WMS/LB instance executing on it a python compiled function on them. This python executable on each WMSLB instance implements sensors and send data to the WMSMonitor server using snmp.
  • WEB PUBLISHING: Exploiting php based functions, data are retrieved from a local Mysql DB, aggregated and published on a graphical user interface through a secure https protocol. Charts are implemented exploiting "Open Flash Chart", an open source flash based set of libraries.
  • CUMULATIVE STATS: plot reporting on all wms in use by a specific VO
 

Working On

  • Packaging for current release deployment
  • Implementation of estimates of job latency
Changed:
<
<
  • Cumulative stats plot reporting on all wms in use by a specific VO
  • Old lcg-rb monitoring
>
>
  • Old lcg-rb monitoring (probably will not be done because of the decommissioning of lcg-rb )
 
  • Mail notifications system implementation

Revision 92008-03-04 - DaniloDongiovanni

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Overview

WMSMonitor is composed by a main page reporting an overview of main status variables for all WMS instances monitored
and a page with detailed data for each specific instance.

Changed:
<
<
>
>
 

User Requirements

Revision 82008-03-04 - DaniloDongiovanni

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Overview

WMSMonitor is composed by a main page reporting an overview of main status variables for all WMS instances monitored
and a page with detailed data for each specific instance.

Changed:
<
<
Aggregated data page
>
>
 

User Requirements

Revision 72008-03-04 - DaniloDongiovanni

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Overview

WMSMonitor is composed by a main page reporting an overview of main status variables for all WMS instances monitored
and a page with detailed data for each specific instance.
Changed:
<
<
>
>
 

User Requirements

Revision 62008-02-29 - DaniloDongiovanni

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Overview

WMSMonitor is composed by a main page reporting an overview of main status variables for all WMS instances monitored
and a page with detailed data for each specific instance.
Line: 15 to 15
 
  • WMSLB INSTANCES: A cron on the WMSMonitor server collects data from each WMS/LB instance executing on it a python compiled function on them. This python executable on each WMSLB instance implements sensors and send data to the WMSMonitor server using a soap module.
  • WEB PUBLISHING: Exploiting php based functions, data are retrieved from a local Mysql DB, aggregated and published on a graphycal user interface through a secure https protocol. Charts are implemented exploiting "Open Flash Chart", an open source flash based set of libraries.
Deleted:
<
<

Installation

WORK IN PROGRESS

 

Working On

  • Packaging for current release deployment
  • Implementation of estimates of job latency

Revision 52008-02-12 - DaniloDongiovanni

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Overview

WMSMonitor is composed by a main page reporting an overview of main status variables for all WMS instances monitored
and a page with detailed data for each specific instance.
Line: 16 to 16
 
  • WEB PUBLISHING: Exploiting php based functions, data are retrieved from a local Mysql DB, aggregated and published on a graphycal user interface through a secure https protocol. Charts are implemented exploiting "Open Flash Chart", an open source flash based set of libraries.

Changed:
<
<

Installation

WORK IN PROGRESS
>
>

Installation

WORK IN PROGRESS
 

Revision 42008-02-08 - DaniloDongiovanni

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Overview

WMSMonitor is composed by a main page reporting an overview of main status variables for all WMS instances monitored
and a page with detailed data for each specific instance.
Changed:
<
<
>
>
 
Deleted:
<
<

Installation

  • Requirements
    WORK IN PROGRESS
 

User Requirements

  • You need the certificate and flash installed on your browser
  • Basic Knowledge of WMSLB architecture

Tool Architecture Overview

Changed:
<
<
  • WMSmonitor runs on a dedicated server machine with a Mysql database to store data, Php, Apache and Python on it.
  • On each WMS/LB instance data are collected by sensors and sent to the server using a pyhton soap module.
>
>
  • WMSMonitor SERVER: WMSMonitor runs on a dedicated server machine with a Mysql database to store data, Php, Apache and Python on it.
  • WMSLB INSTANCES: A cron on the WMSMonitor server collects data from each WMS/LB instance executing on it a python compiled function on them. This python executable on each WMSLB instance implements sensors and send data to the WMSMonitor server using a soap module.
  • WEB PUBLISHING: Exploiting php based functions, data are retrieved from a local Mysql DB, aggregated and published on a graphycal user interface through a secure https protocol. Charts are implemented exploiting "Open Flash Chart", an open source flash based set of libraries.

Installation

WORK IN PROGRESS

 

Working On

  • Packaging for current release deployment

Revision 32008-02-07 - DaniloDongiovanni

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Overview

WMSMonitor is composed by a main page reporting an overview of main status variables for all WMS instances monitored
and a page with detailed data for each specific instance.
Line: 25 to 25
 
  • Cumulative stats plot reporting on all wms in use by a specific VO
  • Old lcg-rb monitoring
  • Mail notifications system implementation
Deleted:
<
<
-- DaniloDongiovanni - 31 Jan 2008
 \ No newline at end of file

Revision 22008-02-07 - DaniloDongiovanni

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Overview

WMSMonitor is composed by a main page reporting an overview of main status variables for all WMS instances monitored
and a page with detailed data for each specific instance.
Line: 8 to 8
 

Installation

Changed:
<
<
  • Requirements
>
>
  • Requirements
    WORK IN PROGRESS
 

User Requirements

  • You need the certificate and flash installed on your browser

Revision 12008-01-31 - DaniloDongiovanni

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="WebHome"

Overview

WMSMonitor is composed by a main page reporting an overview of main status variables for all WMS instances monitored
and a page with detailed data for each specific instance.

Installation

  • Requirements

User Requirements

  • You need the certificate and flash installed on your browser
  • Basic Knowledge of WMSLB architecture

Tool Architecture Overview

  • WMSmonitor runs on a dedicated server machine with a Mysql database to store data, Php, Apache and Python on it.
  • On each WMS/LB instance data are collected by sensors and sent to the server using a pyhton soap module.

Working On

  • Packaging for current release deployment
  • Implementation of estimates of job latency
  • Cumulative stats plot reporting on all wms in use by a specific VO
  • Old lcg-rb monitoring
  • Mail notifications system implementation

-- DaniloDongiovanni - 31 Jan 2008

 
TWIKI.NET
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