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:

• Certain IPs of machines used for development and maintenance are excluded.
• Accesses with certain known robot signatures are not logged (starting Feb 2008; we did not have access to user-agent information before).
• IPs that access robots.txt are ignored after that access.
• Certain known spider subnets are excluded.

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.

Please report errors and problems to the site operators. Thanks.