MRS-PI: METRIC RESULTS STORE PROGRAMMATIC INTERFACE

INTRODUCTION

MRS programmatic interface provides several queries for retrieving information in various format(JSON,XML,YAML,PICKLE) from MRS(Metric Result Store), ATP(Aggregated Topology Provider) and MDDB(Metric Description Database) Databases. All the queries comply with the Grid Monitoring Data Exchange Standard defined by the WLCG Grid Monitoring Working Group. It has been developed using django-piston based REST APIs.

REPOSITORY

The SVN repository of the source code along with the spec file is located here: http://www.sysadmin.hep.ac.uk/svn/grid-monitoring/trunk/metric-store/mrs-web

COMPONENT

The MRS-PI has two two components.

DATABASE-COMPONENT

MRS-PI uses the Data from three different databases namely ATP, MDDB and MRS.

Navigate through these links to see the ERD Diagram of different databases used by MRS-PI

PI-COMPONENT

This component exposes the Data in various format via django-piston based RESTful APIs.

INSTALLATION AND CONFIGURATION

MRS-PI is available as rpm package. Just download and install them on the target system.

MRS-PI is developed using Django, a high level python framework and django-piston, a mini-framework for Django for creating RESTful APIs. The following softwares must be installed and configured on the target system before installing MRS-PI:

  1. python (2.4.3 or higher)
  2. Apache
  3. mod_wsgi
  4. Django 1.1
  5. Django-piston 0.2.2
  6. Python module for accessing Oracle database - cx_Oracle
  7. Python module for accessing MYSQL database - MySQLdb

After successful installation one needs to edit mrs.ini file under /etc/mrs_django for configuring the MRS-PI The most of the parameters in the mrs.ini file are self explanatory.It is recommend that all the settings in the debug section should be false in productive environment.

CONVENTIONS

  • All Dates displayed by MRS-PI are expressed in UTC/GMT and following the W3C Date and Time formats.
  • In particular, dates are represented in this format: YYYY-MM-DDThh:mm:ss, like for example: 2010-01-01T10:10:10
  • The parameter names are case-sensitive whereas the parameter values are case-insensitive
    • e.g. <site= CERN-PROD > and <site= cern-prod > doesn't make any difference
    • e.g. < SITE =CERN-PROD> and < site =cern-prod> are different and don't use like this otherwise you will get different results.
  • If feed is required in different format like xml,yaml,pickle then just append the format name(xml,yaml,pickle) to the query name followed by .
    • e.g
      http://grid-monitoring.cern.ch/mrs/api/site_name.xml
      this will generate the feed of all the site names defined in ATP in xml format.
    • e.g
      http://grid-monitoring.cern.ch/mrs/api/site_name.yaml
      this will generate the feed of all the site names defined in ATP in yaml format.

QUERIES

Description of all the queries implemented by MRS-PI with detailed information about the query parameters and there values along with sample output.

GROUP

Description:

This Query will return all the Site groupings defined by various vo's in ATP Database.

URL:

http://grid-monitoring.cern.ch/mrs/api/group

Parameter Description

  • vo : Possible values are: ops, lhcb , cms , atlas. This parameter is optional and can be present multiple times.

Sample URLs:

All Site groupings defined by all vo's :

http://grid-monitoring.cern.ch/mrs/api/group
All Site groupings defined by ops vo:
http://grid-monitoring.cern.ch/mrs/api/group?vo=ops
All Site groupings defined by ops and cms vo:
http://grid-monitoring.cern.ch/mrs/api/group?vo=ops&vo=cms

Sample Output:

{
 "cms": [
  "CMS-Services"
 ],
 "ops": [
  "Tier-2",
  "Tier-0",
  "Tier-1"
 ]
}

SITE GROUP

Description:

This Query will return all the sites present in a group defined by various vo's in ATP Database.

URL:

http://grid-monitoring.cern.ch/mrs/api/site_group

Parameter Description

  • vo : Possible values are: ops, lhcb, cms, atlas. This parameter is mandatory and should be present only once.
  • sitegroup : Possible values are Tier-0, Tier-1, etc for ops vo.This parameter is optional and can be present in the query multiple times.
Sample URLs:

All sites present in different Site groups defined by ops vo:

http://grid-monitoring.cern.ch/mrs/api/site_group?vo=ops
All sites present in tier-1 Site group defined by ops vo:
http://grid-monitoring.cern.ch/mrs/api/site_group?vo=ops&sitegroup=tier-1
All sites present in tier-0 and tier-1 Site groups defined by ops vo:
http://grid-monitoring.cern.ch/mrs/api/site_group?vo=ops&sitegroup=tier-0&sitegroup=tier-1

Sample Output:

{
 "GROUPS": {
  "Tier-0": {
   "CERN-PROD": {
    "TIER": "0",
    "INFRASTRUCTURE": "EGEE",
    "VIRTUAL_SITENAME": ""
   }
  }
 },
 "VO": "ops"
}

SERVICE GROUP

Description:

This Query will return all the service flavours present in a service group defined by various vo's in ATP Database.

URL:

http://grid-monitoring.cern.ch/mrs/api/service_group

Parameter Description

  • vo : Possible values are: ops, lhcb, cms, atlas. This parameter is mandatory and should be present only once in the query.
  • group : Possible values are CMS-Services,*etc* for cms vo.This parameter is optional and can be present in the query multiple times.
Sample URLs:

All service flavours present in all service groups defined by cms vo:

http://grid-monitoring.cern.ch/mrs/api/service_group?vo=cms
All service flavours present in service groups CMS-services defined by cms vo:
http://grid-monitoring.cern.ch/mrs/api/service_group?vo=cms&group=CMS-services

Sample Output:

{
 "GROUP": {
  "CMS-Services": {
   "CE": [
    "CE"
   ],
   "SRM": [
    "SRMv2"
   ]
  }
 },
 "vo": "cms"
}

METRIC NAME(TEST NAME)

Description:

This Query will return all the service metrics(test) present in different profiles defined by various vo's in MDDB Database.

URL:

http://grid-monitoring.cern.ch/mrs/api/metric_name

Parameter Description

  • vo : Possible values are: ops, lhcb, cms, atlas. This parameter is mandatory and should be present only once in the query.
  • profile : Profile defined by the vo's. Possible values are ROC, ROC_CRITICAL, GLEXEC, etc for ops vo.This parameter is optional and can be present in the query multiple times.
  • service : Possible values are CE, SRM,etc.This parameter is optional and can be present in the query multiple times.
  • flavour : Possible values are SRMv2, glite-CE,etc.This parameter is optional and can be present in the query multiple times.
  • testname : Possible values are hr.srce.GRAM-Auth, hr.srce.GRAM-Auth,etc.This parameter is optional and can be present in the query multiple times.
Sample URLs:

All service metrics present in all the profiles defined by ops vo:

http://grid-monitoring.cern.ch/mrs/api/metric_name?vo=ops
All service metrics present in profile ROC defined by ops vo:
http://grid-monitoring.cern.ch/mrs/api/metric_name?vo=ops&profile=ROC
All service metrics present in profile ROC for the service CE defined by ops vo:
http://grid-monitoring.cern.ch/mrs/api/metric_name?vo=ops&profile=ROC&service=CE
All service metrics present in profile ROC for the service CE and service flavour glite-CE defined by ops vo:
http://grid-monitoring.cern.ch/mrs/api/metric_name?vo=ops&profile=ROC&service=CE&flavour=glite-CE
This will give the Profile , Service , Service flavour of a Particular service metric defined by ops vo.Possible values are hr.srce.GRAM-Auth, org.gstat.SanityCheck,etc
http://grid-monitoring.cern.ch/mrs/api/metric_name?vo=ops&testname=hr.srce.GRAM-Auth

Sample Output:

{
 "GROUPS": {
  "ROC": {
   "CE": {
    "CE": [
     "hr.srce.GRAM-Auth",
     "hr.srce.GRAM-CertLifetime",
     "org.nagios.GridFTP-Check",
     "hr.srce.GridFTP-Transfer",
     "hr.srce.CAdist-Version",
     "org.sam.CE-JobSubmit",
     "org.sam.CE-JobState",
     "org.sam.WN-RepCr",
     "org.sam.WN-CAver",
     "org.sam.WN-RepISenv",
     "org.sam.WN-SoftVer",
     "org.sam.WN-Rep",
     "org.sam.WN-Bi",
     "org.sam.WN-RepGet",
     "org.sam.WN-RepDel",
     "org.sam.WN-RepFree",
     "org.sam.WN-Csh",
     "org.sam.WN-RepRep",
     "org.sam.WN-PyVer",
     "org.nmap.GRAM"
    ]
   }
  }
 },
 "VO": "ops"
}

HISTORY OF SERVICE METRICS(TEST)

Description:

This Query will return the history result of service metrics(tests) present in a profile and executed in a particular sitegroup by the vo from the MRS Database.

URL:

http://grid-monitoring.cern.ch/mrs/api/metric_result

Parameter Description

  • vo : Possible values are: ops, lhcb, cms, atlas. This parameter is mandatory and should be present only once in the query.
  • sitegroup : Grouping defined by the vo's. Possible values are Tier-1, Tier-0, Tier-2 for ops vo.This parameter is optional and can be present in the query multiple times.
  • profile : Profile defined by the vo's. Possible values are ROC, ROC_CRITICAL, GLEXEC, MPI for ops vo.This parameter is optional and can be present in the query multiple times.
  • flavour : Possible values are SRMv2, glite-CE,etc.This parameter is optional and can be present in the query multiple times.
  • host : Host on which the metrics is executed.Possible values are fts-t2-service.cern.ch,etc.This parameter is optional and can be present in the query multiple times.
  • stardate : Starting time (in W3C format) of history period. This parameter is optional and should be present only once.
  • endate : Ending time (in W3C format) of history period. This parameter is optional and should be present only once.
  • timerange : Timerange in hours.It uses last N hours.This parameter is optional and should be present only once.

NOTE:

  • Maximum value of timerange parameter can be upto 1000 Hrs.
  • The Time gap between startdate and enddate should be less than one month.
  • If startdate and enddate are not specified then it will give the last 7 days result.
  • If startdate ,*enddate* and timerange all are specified then timerange has precedence will giving the result.
  • If range between enddate and startdate is bigger than a month then it will give the last 7 days result.

Sample URLs:

Result of all service metrics(test) present in all profiles defined by ops vo and executed on all sites present in sitegroup Tier-0

http://grid-monitoring.cern.ch/mrs/api/metric_result?vo=ops&sitegroup=tier-0&startdate=2010-01-01T10:10:10&enddate=2010-01-03T01:11:11
Result of all service metrics(test) with service flavour CE defined in profile ROC and executed on all sites present in sitegroup Tier-0
http://grid-monitoring.cern.ch/mrs/api/metric_result?vo=ops&sitegroup=tier-0&flavour=ce&profile=roc&startdate=2010-01-01T10:10:10&enddate=2010-01-03T01:11:11
Result of all service metrics(test) in profile ROC defined by ops vo and executed on all sites present in sitegroup Tier-0 in last 100 Hours
http://grid-monitoring.cern.ch/mrs/api/metric_result?vo=ops&sitegroup=tier-0&profile=roc&timerange=100
Result of all service metrics(test) in profile ROC defined by ops vo and executed on host fts-t2-service.cern.ch in last 100 Hours
http://grid-monitoring.cern.ch/mrs/api/metric_result?vo=ops&profile=roc&timerange=100&host=fts-t2-service.cern.ch
Result of all service metrics(test) with service flavour FTS defined in profile ROC and executed on host fts-t2-service.cern.ch in last 100 Hours
http://grid-monitoring.cern.ch/mrs/api/metric_result?vo=ops&profile=roc&timerange=100&host=fts-t2-service.cern.ch&flavour=FTS
Sample Output:
[
 {
  "GROUPS": {
   "Tier-0": {
    "CERN-PROD": {
     "FTS": {
      "FTS": {
       "fts-t2-service.cern.ch": {
        "ch.cern.FTS-ChannelList": [
         {
          "STATUS": "OK",
          "CHECKTIME": "2010-04-02T13:50:45"
         },
         {
          "STATUS": "OK",
          "CHECKTIME": "2010-04-02T14:05:51"
         },
         {
          "STATUS": "OK",
          "CHECKTIME": "2010-04-02T14:20:51"
         }
        ]
       }
      }
     }
    }
   }
  },
  "VO": "ops"
 }
]

DETAIL RESULT OF SERVICE METRIC(TEST)

Description:

This Query will return the detail test result of the Service Metric(test) executed by the vo from MRS Database.

URL:

http://grid-monitoring.cern.ch/mrs/api/metric_detail

Parameter Description

  • vo : Possible values are: ops, lhcb, cms, atlas. This parameter is mandatory and should be present only once in the query.
  • hostname : Host on which the metric(test) is executed.Possible values are phys5.gridzone.ru,etc.This parameter is mandatory and should be present only once in the query.
  • metric : Possible values are org.sam.WN-Bi,etc.This parameter is mandatory and can be present only once in the query.
  • timestamp : TimeStamps at which the metric(test) is executed.This parameter is mandatory and should be present only once in the query.
Sample URLs:

This will give the detail test result of the Service Metric org.sam.WN-Bi executed on host phys5.gridzone.ru at timestamp 1252657145

http://grid-monitoring.cern.ch/mrs/api/metric_detail?vo=ops&hostname=phys5.gridzone.ru&metric=org.sam.WN-Bi&timestamp=1252657145
Sample Output:
{
 "LOG": "<h2>Checking if BrokerInfo works</h2>\\n<p>BrokerInfo file: /home/ops036/globus-tmp.phys14.31408.0/https_3a_2f_2fwmssamtest02.cern.ch_3a9000_2fUeL3J_5foACBVx1UiIYoKYGw/.BrokerInfo</p>\\n<pre>\\n+ ls -l /home/ops036/globus-tmp.phys14.31408.0/https_3a_2f_2fwmssamtest02.cern.ch_3a9000_2fUeL3J_5foACBVx1UiIYoKYGw/.BrokerInfo\\n-rw-r--r--  1 ops036 ops 2275 Sep 11 12:16 /home/ops036/globus-tmp.phys14.31408.0/https_3a_2f_2fwmssamtest02.cern.ch_3a9000_2fUeL3J_5foACBVx1UiIYoKYGw/.BrokerInfo\\n+ set +x\\n</pre>\\n<p>Check if we can get the name of CE using glite-brokerinfo command</p>\\n<pre>\\n+ glite-brokerinfo -v getCE\\nBrokerInfo::getBIFileName(): /home/ops036/globus-tmp.phys14.31408.0/https_3a_2f_2fwmssamtest02.cern.ch_3a9000_2fUeL3J_5foACBVx1UiIYoKYGw/.BrokerInfo\\nBrokerInfo::getCE(): \\n -> phys5.gridzone.ru:2119/jobmanager-lcgpbs-ops\\n -> BI_SUCCESS\\n+ result=0\\n+ set +x\\n</pre>\\n"
}

SERVICE-END-POINT PRESENT IN THE SITE

Description:

This Query will give the different service-end-point present in a site from ATP Database .

URL:

http://grid-monitoring.cern.ch/mrs/api/hostname

Parameter Description

  • vo : Possible values are: ops, lhcb, cms, atlas. This parameter is mandatory and should be present only once in the query.
  • sitegroup : Possible values are Tier-0, Tier-1, Tier-2 for ops vo.This parameter is optional and can be present in the query multiple times.
  • site : Possible values are CERN-PROD, FZK-LCG2,etc for ops vo.This parameter is optional and can be present in the query multiple times.
  • flavour : Possible values are SRMv2, glite-CE,etc.This parameter is optional and can be present in the query multiple times.
  • service : Possible values are CE, SRM,etc.This parameter is optional and can be present in the query multiple times.
Sample URLs:

This will give all the service-end-point for flavour SRMv2 in site CERN-PROD.

http://grid-monitoring.cern.ch/mrs/api/hostname?vo=ops&site=CERN-PROD&flavour=SRMv2
This will give all the service-end-point for flavour CE present in all sites of cms vo.
http://grid-monitoring.cern.ch/mrs/api/hostname?vo=cms&service=CE
This will give all the service-end-point for all flavours present in all sites in site group Tier-1 of ops vo.
http://grid-monitoring.cern.ch/mrs/api/hostname?vo=ops&sitegroup=Tier-1
Sample Output:
{
 "Tier-0": {
  "CERN-PROD": {
   "SRM": {
    "SRMv2": [
     "srm-alice.cern.ch",
     "srm-lhcb.cern.ch",
     "srm-atlas.cern.ch",
     "srm-dteam.cern.ch",
     "srm-cms.cern.ch",
     "srm-public.cern.ch"
    ]
   }
  }
 }
}

ADJACENT HOST OF GIVEN HOST

Description:

This Query will give the adjacent host for a given host present in a site from ATP Database .

URL:

http://grid-monitoring.cern.ch/mrs/api/adjacent_host

Parameter Description

  • vo : Possible values are: ops, lhcb, cms, atlas. This parameter is mandatory and should be present only once in the query.
  • site : Possible values are CERN-PROD, FZK-LCG2,etc for ops vo.This parameter is optional and can be present in the query multiple times.
  • flavour : Possible values are SRMv2, glite-CE,etc.This parameter is optional and can be present in the query multiple times.
  • host : Host for which the adjacent host is required.Possible values are ce104.cern.ch, ce105.cern.ch, etc.This parameter is optional and can be present in the query multiple times. NOTE: The hostname are sorted in the order starting from sitename,*flavour* and host.

Sample URLs:

This will give the adjacent host for all the hosts belonging to all the sites present in ops vo.

http://grid-monitoring.cern.ch/mrs/api/adjacent_host?vo=ops
This will give the adjacent host for all the hosts belonging to CERN-PROD site in ops vo.
http://grid-monitoring.cern.ch/mrs/api/adjacent_host?vo=ops&site=CERN-PROD
This will give the adjacent host for all the hosts for service flavour CE belonging to CERN-PROD site in ops vo.
http://grid-monitoring.cern.ch/mrs/api/adjacent_host?vo=ops&site=CERN-PROD&flavour=CE
This will give the adjacent host for host ce104.cern.ch present in ops vo.
http://grid-monitoring.cern.ch/mrs/api/adjacent_host?vo=ops&host=ce104.cern.ch

Sample Output:

[
 {
  "nexthost": "ce107.cern.ch",
  "prevhost": "ce105.cern.ch",
  "currenthost": "ce106.cern.ch"
 },
 {
  "nexthost": "ce108.cern.ch",
  "prevhost": "ce106.cern.ch",
  "currenthost": "ce107.cern.ch"
 }
]

SERVICE METRIC(TEST) STATUS

Description:

This query will returns all the possible status a service metric(Test) may have after execution from MRS Database.

URL:

http://grid-monitoring.cern.ch/mrs/api/servicemetric_status

Parameter Description

This query does not accept any parameter.

Sample Output:

{
 "METRIC_STATUS": [
  {
   "NAME": "OK",
   "DESCRIPTION": ""
  },
  {
   "NAME": "WARNING",
   "DESCRIPTION": ""
  },
  {
   "NAME": "CRITICAL",
   "DESCRIPTION": ""
  },
  {
   "NAME": "UNKNOWN",
   "DESCRIPTION": ""
  },
  {
   "NAME": "MISSING",
   "DESCRIPTION": "Automatically calculated by Metric Store"
  }
 ]

VO NAME

Description:

This query will return all the VO Names defined in ATP Database.

URL:

http://grid-monitoring.cern.ch/mrs/api/vo_name

Parameter Description:

This query does not accept any parameter.

Sample Output:

{
 "VO_LIST": [
  {
   "VO_NAME": "aegis"
  },
  {
   "VO_NAME": "alice"
  },
  {
   "VO_NAME": "ams"
  },
  {
   "VO_NAME": "ams02.cern.ch"
  },
  {
   "VO_NAME": "apesci"
  },
  {
   "VO_NAME": "argo"
  }
}

SITE NAME

Description:

This query will return all the site names present in ATP Database.

URL:

http://grid-monitoring.cern.ch/mrs/api/site_name

Parameter Description:

  • site_type : Possible values are: PPS, Production, SC and Test.This parameter is optional and can be present in the query multiple times.
  • site_status : Possible values are: true and false.It specifies whether the site is certified or not.This parameter is optional and should be present only once in the query.

Sample URLs:

This will give all the sites in Pre-Production state.

http://grid-monitoring.cern.ch/mrs/api/site_name?site_type=pps
This will give all the sites in Pre-Production or Production state.
http://grid-monitoring.cern.ch/mrs/api/site_name?site_type=pps&site_type=production
This will give all the sites in Production and Certified state:
http://grid-monitoring.cern.ch/mrs/api/site_name?site_type=Production&site_status=true

Sample Output:

[
 {
  "SITENAME": "AEGIS01-IPB-SCL",
  "SITE_STATUS": "Y",
  "SITE_TYPE": "Production"
 },
 {
  "SITENAME": "AEGIS07-IPB-ATLAS",
  "SITE_STATUS": "Y",
  "SITE_TYPE": "Production"
 },
 {
  "SITENAME": "AEGIS10-VINCA-CMS",
  "SITE_STATUS": "N",
  "SITE_TYPE": "Production"
 },
 {
  "SITENAME": "AGH-ICSR",
  "SITE_STATUS": "N",
  "SITE_TYPE": "Production"
 }
]

SERVICE TYPES

Description:

This query will return all the Service Types defined in ATP Database.

URL:

http://grid-monitoring.cern.ch/mrs/api/service_type

Parameter Description:

This query does not accept any parameter.

Sample Output:

[
 {
  "SERVICETYPE": "AMGA"
 },
 {
  "SERVICETYPE": "APEL"
 },
 {
  "SERVICETYPE": "BDII"
 },
 {
  "SERVICETYPE": "CE"
 },
 {
  "SERVICETYPE": "FTM"
 },
 {
  "SERVICETYPE": "FTS"
 },
 {
  "SERVICETYPE": "GUMS"
 }
]

SERVICE TYPE RUNNING IN SERVICE-END-POINT OR SITES

Description:

This query will return all the Service types defined in each service-endpoint or Sites from ATP Database.

URL:

http://grid-monitoring.cern.ch/mrs/api/servicetype_per_service_endpoint

Parameter Description:

  • serviceendpoint - The Service-endpoint were services are running. This parameter is optional and can be present in the query multiple times.
  • sitename - This parameter is optional and can be present in the query multiple times.

Sample URLs:

This will give all the Service types running in CERN-PROD and INFN-BOLOGNA-CMS site:

http://grid-monitoring.cern.ch/mrs/api/servicetype_per_service_endpoint?sitename=CERN-PROD&sitename=INFN-BOLOGNA-CMS

This will give the Service types running in the Service-endpoint agh1.atlas.unimelb.edu.au and cmsboce.bo.infn.it:

http://grid-monitoring.cern.ch/mrs/api/servicetype_per_service_endpoint?serviceendpoint=agh1.atlas.unimelb.edu.au&serviceendpoint=cmsboce.bo.infn.it

Sample Output:

{
 "INFN-BOLOGNA-CMS": {
  "cmsboce.bo.infn.it": "APEL"
 },
 "Australia-ATLAS": {
  "agh1.atlas.unimelb.edu.au": "Top-BDII"
 }
}

STATUS,TIMESTAMPS AND DETAILS OF SERVICE-ENDPOINT AND SERVICE METRICS EXECUTED BY A CERTAIN VO.

Description:

This query will return the latest timestamps(execution time) of all Service Metrics executed by certain VO in any Service-endpoint and Site from MRS database.

URLs:

http://grid-monitoring.cern.ch/mrs/api/service_endpoint_status

Parameter Description:

  • vo : This parameter is mandatory and should be present only once.
  • site : The Site name hosting the Service. This parameter is optional and can be present in the query multiple times.
  • flavour : The Service-Type-Flavour we are interested in. This parameter is optional and can be present in the query multiple times.
  • infrastructure : The infrastructure to which the site belongs.This parameter is mandatory and should be present only once.

Sample URLs:

This will give the last status and timestamps of all Service Metrics(test) for CE Service-Type-Flavour executed by ops vo in site CERN-PROD from EGEE infrastructure.

http://grid-monitoring.cern.ch/mrs/api/service_endpoint_status?vo=ops&site=CERN-PROD&infrastructure=EGEE&flavour=CE
This will give the last status and timestamps of all Service metrics(test) for all Service-Type-Flavour executed by ops vo in site CERN-PROD from EGEE infrastructure.
http://grid-monitoring.cern.ch/mrs/api/service_endpoint_status?vo=ops&site=CERN-PROD&infrastructure=EGEE
This will give the the last status and timestamps of all Service Metrics(test) for CE and SRMv2 Service-Type-Flavour executed by ops vo in site CERN-PROD from EGEE infrastructure.
http://grid-monitoring.cern.ch/mrs/api/service_endpoint_status?vo=ops&site=CERN-PROD&infrastructure=EGEE&flavour=CE&flavour=SRMv2
Sample Output:
{

      CERN-PROD: {
            ce127.cern.ch: {
                  CE: [
                        {
                            * status: "OK"
                            * timestamp: "08-07-2010 09:50:33"
                            * metric_name: "org.sam.CE-JobSubmit"
                        }
                        -
                        {
                            * status: "OK"
                            * timestamp: "08-07-2010 09:33:24"
                            * metric_name: "org.sam.WN-RepDel"
                        }
                        ]
                    }
              }
}

Topic attachments
I Attachment History Action Size Date Who Comment
Textini mrs.ini r1 manage 1.8 K 2010-04-03 - 17:49 MalikEhsanullah MRS-PI Configuration File
Edit | Attach | Watch | Print version | History: r9 < r8 < r7 < r6 < r5 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r9 - 2010-07-08 - AkshatKakkar
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LCG All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback