- Doc Structure
- A Globus Primer
- Installing GT
- Platform Notes
- Migrating from GT2
- Migrating from GT3
- PDF version
- Best Practices
- Coding Guidelines
- API docs
- Public Interfaces
- Resource Properties
- Performance Studies
Table of Contents
The WS MDS Trigger Service collects information about Grid resources and can be configured to execute a program if the collected data meets certain conditions.
End-users will typically interact with the Trigger Service indirectly, using some mechanism specific to the triggered executable program (for example, an executable program may send mail to an end-user or write a structured log file that will later be read by some other program).
The Trigger Service itself does not have any command-line clients for end users; instead, the trigger service is configured to run an executable program to take some action (for example, send mail to a set of users, or write a log entry to a file).
The mds-servicegroup-add(1) command in the Aggregator Framework is used to configure the Trigger Service to collect information from various sources.
There is no GUI specifically for the Trigger Service. The release contains WebMDS which can be used to display the status of resources registered to a Trigger Service in a normal web browser.
The Trigger Service does not have any end-user clients. General troubleshooting information can be found in Section 4, “Troubleshooting”.
The following WS MDS-specific usage statistics are sent in a UDP packet every 60 minutes, in addition to the standard header information described in the Usage Stats section.
- Service Name (service group)
- Total number of registrations i.e., successfully invoked service group add operations made against the resource during its lifetime
- Current number of registrants (service group entries)
- The resource creation time
The client (mds-servicegroup-add) does NOT send any data. It is the server components that send the usage statistics.
Also, please see our policy statement on the collection of usage statistics.