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 @


From EGIWiki
Jump to navigation Jump to search
Main operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security

Documentation menu: Home Manuals Procedures Training Other Contact For: VO managers Administrators

How to add URL service endpoint information into GOC-DB

For monitoring purposes, each service endpoints registered into GOC-DB with the flags production and monitored should include the endpoint URL information in order to be contacted by the relative nagios probe.

Important: currently these steps are required only for the sites under certification. For sites in production, EGI Monitoring is retrieving from the Top-BDII these information

The information needed for service type are:

  • CREAM-CE: the queue URL where the ops VO is enabled. This is the value of the attribute GlueCEUniqueID published in the BDII (e.g.
  • SRM: the value of the attribute GlueServiceEndpoint published in the BDII (e.g. httpg://
  • Other service types: the value of the attribute GlueServiceEndpoint published in the BDII

It is also possible registering additional endpoints for each service: by setting also the "Monitored" flag, ARGO will monitor them.

For having more information about managing the Service endpoints in GOC-DB, please consult the relative documentation.

Get the information

For retrieving the queue URL from the BDII, you can simply use the command lcg-infosites executed from an UI. Be sure to query a production Top-BDII: you can either set the one provided by your Operations Centre or choose one from

For example:

$ export

$ lcg-infosites --vo ops ce | grep nikhef
  5680      15          0            0       0
  5680      17          1            1       0
  5680      15          0            0       0
  5680      15          0            0       0
  5680      16          0            0       0

For getting the GlueServiceEndpoint URL of your SRM service, you can launch a ldap query to your site-bdii (or also directly to the SRM service):

$ ldapsearch -x -LLL -H ldap:// -b "mds-vo-name=NCG-INGRID-PT,o=grid" '(&(objectClass=GlueService)(GlueServiceType=SRM))' GlueServiceEndpoint

dn: GlueServiceUniqueID=httpg://,Mds-Vo-name=NCG-INGRID-PT,o=grid
GlueServiceEndpoint: httpg://

In a similar way, by just changing the value of GlueServiceType, you can get the endpoint URLs of other services.

An alternative way for retrieving the GlueServiceEndpoint URL is using the GLUE2 information browser provided by VAPOR ( select your NGI, then your site and hence the Storage service; click on the endpoint details button for finding the URL associated to the SRM interface.

Fill in the information

URLs information are completely missing

  • URLs information are completely missing: you need to edit the services information
this is the home page regarding your site. You need to fill in the URL information. Click on a service for displaying its page (e.g. the CREAM-CE) Picture01.png
click on the EDIT button on the top-right corner Picture02.png
fill in the Service URL field with the queue URL; Picture03.png
Now the CREAM-CE service endpoint contains the required queue information. Proceed in a similar way for the other CREAM-CE and SRM services. Picture04.png

Additional endpoints information

In case you need to register an additional endpoint for a service, go on the service summary page and add the proper information. In the example below it is shown the case of a computing element.

this is the service summary page. You need to click on the Add endpoint button for registering additional endpoint URLs. Picture05.png
Fill in the proper information and don't forget to select the "Monitored" flag for making nagios to detect the new endpoint. Picture06.png
The summary page of the endpoint just added should look like this one. Picture07.png
And this is the summary page of the service reporting the information about all its endpoints registered: the first one in the Grid Information section and the additional ones in the Service Endpoints section. Picture08.png



In order to properly monitor your webdav endpoint: