Thank you for the clarification. This is helpful for me.
I will re-enable the info messages to restore statistics capture.
Regarding my second issue, here is the type of noise that I am seeing in my
"All Actions Performed" report.
Action Number of times
expected hex character and not 170,177
1, Size 103
http 24
attempted to re-assign handle '10822/550858' to an incoming harvested item
'oai 9
restore_auth_sys_state 8
Items Archived 0
Community Views 0
Licence Rejections 0
OAI Requests 0
Searches Performed 0
Bitstream Views 0
Collection Views 0
User Logins 0
Item Views 0
Terry
On Tue, Jun 11, 2013 at 6:03 PM, helix84 <[email protected]> wrote:
> Hi Terry,
>
> this topic is a bit complicated due to the fact that new statistics
> engines have been added and the old ones still kept.
>
> Your definition of content and usage statistics is not correct.
> Usage statistics is statistics on events caused by visitors, i.e. page
> views, downloads and searches.
> Content statistics is statistics on "static" contents of your
> repository - e.g. how many items you have, how many of a certain type.
> Newly in DSpace 3, there are also workflow statistics detailing
> operations on workflow steps by your users (e.g. approve, reject).
>
> There are 3 usage statistics "engines" in DSpace 3:
> 1) log files based - have been around since forever
> 2) Solr-based - since DSpace 1.6
> 3) Elastic Search based - since DSpace 3, disabled by default
>
> I don't know the menu items or the commands by heart, so just use the
> search feature of our official documentation (DSpace 3.x space), the
> commands will surely be there.
>
>
> Regarding your problems:
> 1) is almost certainly caused by disabling INFO lines, which are used
> by the log file based "engine". This is what those lines look like:
>
> 2013-05-15 16:33:27,671 INFO
> org.dspace.usage.LoggerUsageEventListener @
> anonymous:session_id=F55DB90438AFAE5C16855044111671A4:ip_addr=66.249.74.15:
> view_item:handle=123456789/647
>
> Solr-based statistics would not be affected by this, because they
> collect the events independently, not from log files (although import
> from log files is possible - meant for importing your legacy
> statistics).
>
> If you disabled logging, there's little hope of ever getting those
> back. You have a good chance of importing your log file-based
> statistics to Solr and continue using those exclusively. Unless you
> have bad luck, the missing period will be covered in Solr stats.
>
> The reverse - generating log files from Solr stats can't be done
> out-of-the-box. It might be possible to write a custom tool that would
> do this.
>
>
> 2) Sorry, can't help you much with this. There seems to be a problem
> also on demo.dspace.org. Is this what you mean? (example follows)
>
> ...
> 45.861] Performing deposit using location 1
> 36.741] Loaded ingester 1
> 52.774] Using package manifest format 1
> 18.794] Loaded ingester 1
> 16.629] Loaded package ingester 1
> 20.785] Total time for deposit processing 1
> ...
>
> Regards,
> ~~helix84
>
> Compulsory reading: DSpace Mailing List Etiquette
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>
--
Terry Brady
Applications Programmer Analyst
Lauinger Information Technology
202-687-7053
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
