Page History
...
Property: | solr-statistics.server | |||
Example Values: | solr-statistics.server = http://127.0.0.1/solr/statistics | |||
Informational Note: | Is used by the SolrLogger Client class to connect to the Solr server over http and perform updates and queries. In most cases, this can (and should) be set to localhost (or 127.0.0.1).
Assuming you get an HTTP 200 OK response, then you should set | |||
Property: | solr-statistics.query.filter.bundles | |||
Example | solr-statistics.query.filter.bundles=ORIGINAL | |||
Informational | A comma seperated list that contains the bundles for which the file statistics will be displayed. | |||
Property: | solr-statistics.query.filter.spiderIp | |||
Example Value: | solr-statistics.query.filter.spiderIp = false | |||
Informational Note: | If true, statistics queries will filter out spider IPs -- use with caution, as this often results in extremely long query strings. | |||
Property: | solr-statistics.query.filter.isBot | |||
Example Value: | solr-statistics.query.filter.isBot = true | |||
Informational Note: | If true, statistics queries will filter out events flagged with the "isBot" field. This is the recommended method of filtering spiders from statistics. | |||
Property: | solr-statistics. | spiderips.urlsautoCommit | ||
Example Value: | solr-statistics. | spiderips.urlsautoCommit = true | ||
Informational Note: | If true (default), then all view statistics will be committed to Solr whenever the next autoCommit is triggered. This is recommended behavior. If false, then view statistics will be committed to Solr immediately (i.e. via an explicit commit call). This setting is untested in Production scenarios, and is primarily used by automated integration tests (to verify that the statistics engine is working properly). | |||
Property: | solr-statistics.spiderips.urls | |||
Example Value: | solr-statistics.spiderips.urls =
| |||
Informational Note: | List of URLs to download spiders files into [dspace]/config/spiders. These files contain lists of known spider IPs and are utilized by the SolrLogger to flag usage events with an "isBot" field, or ignore them entirely.
from your [dspace]/bin directory |
...
Property: | usage-statistics.dbfile |
Example Value: | usage-statistics.dbfile = ${dspace.dir}/config/GeoLiteCityGeoLite2-City.datmmdb |
Informational Note: | The following referes to the GeoLiteCity database file References the location of the installed GeoLite or DB-IP City "mmdb" database file. This file is utilized by the LocationUtils to calculate the location of client requests based on IP address. During the Ant build process (both fresh_install and update) this file will be downloaded from http://www.maxmind.com/app/geolitecity if a new version has been published or it is absent from your [dspace]/config directory |
Property: | usage-statistics.resolver.timeout |
Example Value: | usage-statistics.resolver.timeout = 200 |
Informational Note: | Timeout in milliseconds for DNS resolution of origin hosts/IPs. Setting this value too high may result in solr exhausting your connection pool. |
Property: | useProxies (Set in dspace.cfg) |
Example Value: | useProxies = true |
Informational Note: | Will cause Statistics logging to look for X-Forward URI to detect clients IP that have accessed it through a Proxy service (e.g. the Apache mod_proxy). Allows detection of client IP when accessing DSpace. [Note: This setting is found in the DSpace Logging section of dspace.cfg] |
Property: | usage-statistics.authorization.admin.usage |
Example Value: | usage-statistics.authorization.admin.usage = true |
Informational Note: | When set to true, only general administrators, collection and community administrators are able to access the pageview and download statistics from the web user interface. As a result, the links to access statistics are hidden for non logged-in admin users. Setting this property to "false" will display the links to access statistics to anyone, making them publicly available. |
Property: | usage-statistics.authorization.admin.search |
Example Value: | usage-statistics.authorization.admin.search = true |
Informational Note: | When set to true, only system, collection or community administrators are able to access statistics on search queries. |
Property: | usage-statistics.authorization.admin.workflow |
Example Value: | usage-statistics.authorization.admin.workflow = true |
Informational Note: | When set to true, only system, collection or community administrators are able to access statistics on workflow events. |
Property: | usage-statistics.logBots |
Example Value: | usage-statistics.logBots = true |
Informational Note: | When this property is set to false, and IP is detected as a spider, the event is not logged. |
Property: | usage-statistics.shardedByYear |
Example Value: | usage-statistics.shardedByYear = false |
Informational Note: | When set to "true", the DSpace statistics engine will look for additional Solr Shards (per year) when compiling all usage statistics. Therefore, if you are regularly running "stats-utils -s" (as documented in the "Solr Sharding By Year" section of the "SOLR Statistics Maintenance" page), then you should set this to "true". By default, it is "false", which tells the statistics engine to only compile usage statistics based on what is found in the current Solr core. |
Pre-1.6 Statistics settings
...