Further access options are discussed below
For a list of all services and tables belonging to this service's resource, see Information on resource 'logs/logs'
According to our privacy policy , we log accesses to our services. For data protection, no IPs are stored. Instead, we have user handles which are IPs shrouded with a monthly changing random key. Thus, counts for distinct hosts and the like are not possible across months.
The acc_month column in the database reflects the shrouding key used. At the end of a month, some requests will be counted towards the next month. Since the statistics are somewhat bogus anyway, we will not change this behaviour.
To filter out maintenance and robot accesses as well as let users opt out of logging, the following measures are taken:
The identification of the service used currently is somewhat crude. If the request is for one of the renderers in {form, custom, siap.xml, scs.xml, soap}, the service is taken to be the first element in the URI.
Similarly, it is not trivial to tell accesses actually retrieving data from those that merely retrieve a form. A good measure for retrieving queries is the number of accesses using the POST method. However, within the DC retrieving queries may be posted using GET as well, and only a close inspection of the query itself and knowledge of the service queried could identify them as retrieving queries. This is not done here.
You can access this service using:
This resource is not (directly) published. This can mean that it was deemed too unimportant, for internal use only, or is just a helper for a published service. Equally likely, however, it is under development, abandoned in development or otherwise unfinished. Exercise some caution.
Other services provided on the underlying data include:
The following fields are available to provide input to the service (with some renderers, some of these fields may be unavailable):
Name | Table Head | Description | Unit | UCD |
---|---|---|---|---|
acc_month | Month | Month the access is logged for (handles for different months cannot be compared) | N/A | N/A |
acc_year | Year | Year the access is logged for. | N/A | N/A |
method | Method | HTTP method of the access. | N/A | N/A |
service | Service | Service used (only set for selected renderers). | N/A | N/A |
uri | URI | The URI accessed | N/A | N/A |
The following fields are contained in the output by default. More fields may be available for selection; these would be given below in the VOTable output fields.
Name | Table Head | Description | Unit | UCD |
---|---|---|---|---|
accesses | #Accesses | Total number of service accesses in the month. | N/A | N/A |
hosts | #Hosts | Number of distinct hosts in the month. | N/A | N/A |
monspec | Start | Characteristic date as fractional year | yr | N/A |
The following fields are available in VOTable output. The verbosity level is a number intended to represent the relative importance of the field on a scale of 1 to 30. The services take a VERB argument. A field is included in the output if their verbosity level is less or equal VERB*10.
Name | Table Head | Description | Unit | UCD | Verb. Level |
---|---|---|---|---|---|
monspec | Start | Characteristic date as fractional year | yr | N/A | 1 |
hosts | #Hosts | Number of distinct hosts in the month. | N/A | N/A | 1 |
accesses | #Accesses | Total number of service accesses in the month. | N/A | N/A | 1 |
VOResource XML (that's something exclusively for VO nerds)