This table is not available for ADQL queries and through the TAP endpoint.
Resource Description:
For a list of all services and tables belonging to this table's resource, see Information on resource 'logs/logs'
To cite the table as such, we suggest the following BibTeX entry:
@MISC{vo:weblogs_accesses, year=2008, title={Untitled Resource}, author={{GAVO} Data Center}, url={https://dc.zah.uni-heidelberg.de/tableinfo/weblogs.accesses}, howpublished={{VO} resource provided by the {GAVO} Data Center} }
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.
Sorted by DB column index. [Sort alphabetically]
Name | Table Head | Description | Unit | UCD |
---|---|---|---|---|
service | Service | Service used (only set for selected renderers). | N/A | N/A |
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 |
acc_time | Time | Local time of the access. | N/A | N/A |
handle | Handle | Identifier for the IP the access came from. This is a hash of the IP plus monthly changing random data | N/A | N/A |
uri | URI | The URI accessed | N/A | N/A |
status | Status | The server status returned | N/A | N/A |
resplen | #Bytes | Response length. | N/A | N/A |
agent | Agent | User agent used. This is only available starting Mar 2009. | N/A | N/A |
method | Method | HTTP method of the access. | N/A | N/A |
Columns that are parts of indices are marked like this.
The following services may use the data contained in this table:
VO nerds may sometimes need VOResource XML for this table.