Difference between revisions of "2016-bidding/monitoring"
Line 6: | Line 6: | ||
= Introduction = | = Introduction = | ||
Monitoring services archive and provide access to the infrastructure monitoring results of the services. These data are accessible at many levels (Resource Centres, Operations Centres and EGI.EU), and it is used for the generation of service level reports, and for the central monitoring of EGI.eu operational tools and other central monitoring needs. | |||
Infrastructure operations require in some cases monitoring activities created ad-hoc to support specific operational activities, for example UserDN publishing in accounting records and of software versions of deployed middleware. | |||
= Technical description = | = Technical description = |
Revision as of 17:50, 19 October 2016
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
EGI Core services menu: | Services PHASE I • | Services PHASE II • | Services PHASE III • | Bids • | Payments • | Travel procedure • | Performance |
Go back to the EGI Core Activities Bidding page.
- Service name: Monitoring (GGUS)
Introduction
Monitoring services archive and provide access to the infrastructure monitoring results of the services. These data are accessible at many levels (Resource Centres, Operations Centres and EGI.EU), and it is used for the generation of service level reports, and for the central monitoring of EGI.eu operational tools and other central monitoring needs. Infrastructure operations require in some cases monitoring activities created ad-hoc to support specific operational activities, for example UserDN publishing in accounting records and of software versions of deployed middleware.
Technical description
Monitoring (SAM) is a centralized system supporting EGI/NGI operations. It provides remote monitoring of services, computation of the monitoring data, visualization of the service status, dashboard interfacing, notification system and generation of availability and reliability reports. The monitoring services ensure the aggregation of all EGI metric results and the access to the data at a EGI-wide scope through the central ARGO user interface. These results are exposed through the central ARGO web service and its programmatic interface (XML & JSON supported). On top of that, the ARGO Reporting System generates monthly availability reports about sites and operational tools for use of the service owners. In addition to the central services described above, the activity provides also: Monitoring probes submission engines: a distributed, high available centralised installation is required to submit and run the monitoring probes for the availability computation profiles and for the other profiles required by the EGI operations.The deployment must support the size of the infrastructure. Development of nagios probes: Maintenance of existing operations probes Development of new probes as required to support operations activities Requirements gathering