Difference between revisions of "Adding Custom Service to Availability Monitoring"
Line 27: | Line 27: | ||
= Process = | = Process = | ||
{| class="wikitable" | {| class="wikitable" |
Revision as of 16:15, 13 March 2013
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.
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).
The Service Availability Monitoring (SAM) [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. It includes the following components:
- test execution framework based on the open source monitoring framework Nagios and the Nagios Configuration Generator (NCG)
- database components which contain topology (gathered from GOCDB and other sources), profiles (mapping between service types and tests), test results and availability and reliability of sites and services
- visualization portal MyEGI which enables users to access current status, history and availability of monitored sites and services
- programmatic interface which enables other tools (e.g. Operations Portal, VO dashboards) to access test results and availability and reliability of sites and services
- probes used to test monitored services. These probes are provided by middleware developers and third parties (e.g. NGIs, Nagios community).
Process
Service provider | Operations |
---|---|
1. Register your service endpoint instance in GOCDB. |
|
2. Validates the service endpoint registration. | |
3. Find the suitable service type in GOCDB. 3.1 If your service does not match any of the existing service types at GOCDB, please request a new service type . | |
4. If an existing service type was chosen, subsequent operations are automatic. 4.1 If a new service type was requested, it will be reviewed by OMB and OTAG. | |
5. If an existing GOCDB service type was suitable, please set option "Monitoring" to start receiving probes.
5.1 If a new service type was requested, choose from the set of currently available probes for your service from the list. | |
6. Subsequent operations are automatic. 6.1 If a new service type was requested and existing probes in SAM framework were chosen, they have to be enabled in a profile of local NGI based on service location |