Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "EGI Core activities:2013-bidding Monitoring central services"

From EGIWiki
Jump to navigation Jump to search
Line 39: Line 39:


= Service level targets =
= Service level targets =
*Minimum availability/reliability: 99%/100%
*Minimum availability/reliability: 99%/99%
*Response to incident records in GGUS within support hours: [[FAQ_GGUS-PT-QoS-Levels#Medium_service| Medium]] (see https://wiki.egi.eu/wiki/FAQ_GGUS-PT-QoS-Levels#Medium_service)
*Response to incident records in GGUS within support hours: [[FAQ_GGUS-PT-QoS-Levels#Medium_service| Medium]] (see https://wiki.egi.eu/wiki/FAQ_GGUS-PT-QoS-Levels#Medium_service)

Revision as of 17:54, 3 July 2013


Go back to the activity list.

  • Service name: Central Monitoring Services
  • Service category: Operations
  • Service type: Coordination, operation

Central Monitoring Services is part of the EGI Core Infrastructure Platform, which supports the daily operations of EGI.

Introduction

Infrastructure operations requires in some cases monitoring activities to be conduced centrally to support specific activities, like monitoring of UserDN publishing in accounting records, GLUE information validation, and of software versions of deployed middleware.

Technical description

This service includes the following services:

Monitoring of EGI.eu technical services

A centralised SAM installation is currently running in production to monitor the performance of EGI.eu operations tools (Accounting Portal, central Accounting Repository, Operations Portal, GOCDB, GStat, Metrics Portal, the message broker network and SAM) and user community support tools (GGUS, Application Database and CRM).

Central Nagios service

A central Nagios service is provided to support specific operations activities like User DN publishing in accounting records, GLUE information validation and monitoring of deployed software versions. New specific monitoring needs emerge depending on the operations technical activities. The Nagios infrastructure needs to be scaled accordingly.

Development of Nagios probes

  • Maintenance of existing operations probes
  • Development of new probes as required to support operations activities
  • Requirements gathering

Coordination

This activity is responsible of the coordination of the system operation and upgrade activities with those partners that are in charge of operating other systems that depend on it

Support

Support through the EGI helpdesk about the functionality of the service and the monitoring data gathered.

Support about ... is out of scope and is part of activity 2nd level support (core platform).

Support hours: eight hours a day (9-17 CE(S)T), Monday to Friday – excluding public holidays of the hosting organization.

Operation

  • Daily running of the system
  • High availability configuration

Service level targets