Hi,

I think what you are doing is just a refresh of the statistics page? I
think you are using the same userAgent and the same session perhaps, that
is why it is not being
counted as a hit (visits).
You can see that the solr statistics are being accumulated if you (for
example) download the file, then you will see a +1 in the download counter.
Try using different browser, or even another machine and I am sure that you
will see the count number increase.

I hope this helps.


On Mon, Sep 21, 2015 at 4:23 PM, christian criollo <[email protected]>
wrote:

> Hi mohamed
>
> *when I say that the visits are not accumulating I refer  that the counter
> dont increase for example*
>
>
> *I visit a item five times,, the visits counter of september for example
> has one hunderd visits for the moment, the next day I look the statistics
> and these have increased the new value is one hundred and five this should
> be the normal behavior, the statististics increase depending of the number
> of visits a item, colection, comunity *
>
> El lunes, 21 de septiembre de 2015, 14:23:38 (UTC-5), mohamed battou
> escribió:
>>
>> What is the determinant that you have used to know that the visits are
>> not accumulating?
>> It seems to make sense to me when I look at it.
>>
>> Can you provide more information?
>>
>>
>> On Mon, Sep 21, 2015 at 12:41 PM, christian criollo <[email protected]>
>> wrote:
>>
>>>
>>>
>>> El lunes, 21 de septiembre de 2015, 11:37:57 (UTC-5), christian criollo
>>> escribió:
>>>>
>>>>  Hi ottawad
>>>>
>>>> *the solr is running, the problem basicly consist in that the
>>>> statistics not increase after visit a item, colection, comunity etc the
>>>> counter visits remains the same here a printscreen of the page of
>>>> statistics of our repository where in the month of september the visits
>>>> counter not change*
>>>>
>>>>
>>>>
>>>> El viernes, 18 de septiembre de 2015, 9:19:20 (UTC-5), christian
>>>> criollo escribió:
>>>>>
>>>>> > Hi all
>>>>>
>>>>> >
>>>>>
>>>>> > In our institution we have problems with statistics Dspace, when  I
>>>>>
>>>>> > visited a colection, comunity, item the counter of visits not
>>>>> working
>>>>>
>>>>> > the log is the following
>>>>>
>>>>> >
>>>>>
>>>>> > 2015-03-25 03:43:11,122 INFO  org.dspace.browse.BrowseEngine @
>>>>> anonymous:session_id=B0EE0C89BDD4174B9D7EA1C5005E058B:ip_addr=157.55.39.201:
>>>>> browse_by_item:
>>>>>
>>>>> > 2015-03-25 03:43:11,827 INFO
>>>>>
>>>>> > org.dspace.app.webui.servlet.RetrieveServlet @
>>>>>
>>>>> >
>>>>> anonymous:session_id=30ADC4C506D79A8CA10B643BF9D5DFE0:ip_addr=66.249.7
>>>>>
>>>>> > 9.159:view_bitstream:bitstream_id=131758
>>>>>
>>>>> > 2015-03-25 03:43:11,827 INFO
>>>>>
>>>>> > org.dspace.usage.LoggerUsageEventListener @
>>>>>
>>>>> >
>>>>> anonymous:session_id=30ADC4C506D79A8CA10B643BF9D5DFE0:ip_addr=66.249.7
>>>>>
>>>>> > 9.159:view_bitstream:bitstream_id=131758
>>>>>
>>>>> > 2015-03-25 03:43:12,142 INFO
>>>>>
>>>>> > org.dspace.app.webui.discovery.DiscoverUtility @ facets for scope,
>>>>>
>>>>> > null: 3
>>>>>
>>>>> > 2015-03-25 03:43:12,288 INFO
>>>>>
>>>>> > org.dspace.app.webui.discovery.DiscoverySearchRequestProcessor @
>>>>>
>>>>> >
>>>>> anonymous:session_id=DF9068AADCFF2D6660FC9F871DE946D0:ip_addr=66.249.7
>>>>>
>>>>> > 9.151:search:scope=null,query="null",results=(0,0,5)
>>>>>
>>>>> > 2015-03-25 03:43:12,955 INFO
>>>>>
>>>>> > org.dspace.app.webui.servlet.RetrieveServlet @
>>>>>
>>>>> >
>>>>> anonymous:session_id=B0E9B9B9CE44198BEE97ADEA94DE6050:ip_addr=66.249.7
>>>>>
>>>>> > 9.151:view_bitstream:bitstream_id=246549
>>>>>
>>>>> > 2015-03-25 03:43:12,956 INFO
>>>>>
>>>>> > org.dspace.usage.LoggerUsageEventListener @
>>>>>
>>>>> >
>>>>> anonymous:session_id=B0E9B9B9CE44198BEE97ADEA94DE6050:ip_addr=66.249.7
>>>>>
>>>>> > 9.151:view_bitstream:bitstream_id=246549
>>>>>
>>>>> > 2015-03-25 03:43:17,738 INFO
>>>>>
>>>>> > org.dspace.app.webui.servlet.BitstreamServlet @
>>>>>
>>>>> >
>>>>> anonymous:session_id=CF232C60E5499D86B678CF43CA82F0EF:ip_addr=186.116.
>>>>>
>>>>> > 13.53:view_bitstream:bitstream_id=71731
>>>>>
>>>>> > 2015-03-25 03:43:17,738 INFO
>>>>>
>>>>> > org.dspace.usage.LoggerUsageEventListener @
>>>>>
>>>>> >
>>>>> anonymous:session_id=CF232C60E5499D86B678CF43CA82F0EF:ip_addr=186.116.
>>>>>
>>>>> > 13.53:view_bitstream:bitstream_id=71731
>>>>>
>>>>> > 2015-03-25 03:43:17,739 *ERROR *
>>>>>
>>>>> *> org.dspace.statistics.SolrLoggerUsageEventListener @*
>>>>>
>>>>> > 2015-03-25 03:43:17,826 INFO
>>>>>
>>>>> > org.dspace.app.webui.discovery.DiscoverUtility @ facets for scope,
>>>>>
>>>>> > null: 3
>>>>>
>>>>> > 2015-03-25 03:43:18,079 INFO
>>>>>
>>>>> > org.dspace.app.webui.discovery.DiscoverySearchRequestProcessor @
>>>>>
>>>>> >
>>>>>
>>>>> > I have posted in the comunity dspace with out answers, my question
>>>>> is
>>>>>
>>>>> > if this error has solution in a new release for example 5.3
>>>>>
>>>>> >
>>>>>
>>>>> > thanks for the help
>>>>>
>>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "DSpace Technical Support" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>> To post to this group, send email to [email protected].
>>> Visit this group at http://groups.google.com/group/dspace-tech.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/dspace-tech.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Reply via email to