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.

Adding Custom Service to Availability Monitoring

From EGIWiki
Revision as of 16:01, 19 February 2013 by Ekarolis (talk | contribs) (→‎Process)
Jump to navigation Jump to search


Introduction

Operational tools such as the GOCDB management system and the SAM monitoring system are key software components for the reliable and stable operation/monitoring of the infrastructure.

GOCDB - Grid Configuration Database (GOCDB) contains general information about the sites participating to the production Grid. Accessed by all the project actors (end-users, sitemanagers, NGI mangers, support teams, VO managers), by other tools and by third party middleware in order to get Grid topology. The portal has a single central installation but a regional package will be developed and deployed on the interested NGIs.

Services registered in GOCDB are described with the following information:

  • Service Type: a unique name that identifies the type of software component deployed on a Grid.
  • Service Endpoint: is a deployed instance of a named service type
  • Endpoint Location: a Service Endpoint may optionally define an Endpoint Location which locates the service (URL).


SAM - The Service Availability Monitoring (SAM) system is used to monitor the resources within the production infrastructure. SAM monitoring data is used for calculation of availability and reliability of grid sites.

MS421 document (Reference)

Process

1. Register your custom service (hostname) at GOCDB.

Note: if your service does not much any of existing service types at GOCDB, please request new service type . (Service Types descriptions are meaningless to the not middleware related probes e.g. i want to monitor web service which is http)

2. Choose the set of currently available probes for your service from the list. (Probes descriptions are not available)

Note: if your service has one hostname and you would like to test multiple functionality e.g. http-check and db-check, please make sure that another custom service you will add in the future for the same created service type also provides same multitple functionality, because service types has associated with a set of probes.