Statserver / CCPulse

[PFCCWA]

Hello,

Due to some network issues we keep losing real time stats on ccpulse, so occasionally the figures are reset to 0.  Usuallly the application gets stuck in at the point the server is affected without adding to the numbers.

Which log files can I use to determine what caused this and when?
Im assuming it is the statserver which was either restarted or reset.

If I run a historical report through cca there is a gap between two 15 minute blocks which gives us an idea of when it was affected.

Thanks,
W

[tony]

I [i]think [/i] I know what you mean.... and for this, there is a Persistant Stats Table which maintains a "running total" at StatServer level, relevant for each Client (CCPulse+, in this instance)... This Table is maintained for a time period that you can also define...

Check the following 3 Options for your StatServer:

auto-backup-interval
backup-file-name
old-stats-remove-interval

- full details are in the StatServer Deployment Guide...

Be aware that, using these options the stats will continue to be collated for all Clients - and only as long as the StatServer is up and running, irrespective of the availability of the Client (CCPulse+).  The local settings for CCPulse+ (where you may have set a Time Period or Time Profile) remains unaffected by this and, if you have set your stats to reset on the Client at a specific time or time intervals, this will still occur, irrespective of the settings on the StatServer.

I hope this helps?

TT

[Fra]

[quote author=PFCCWA link=topic=5633.msg24633#msg24633 date=1276602687]
Hello,

Due to some network issues we keep losing real time stats on ccpulse, so occasionally the figures are reset to 0.  Usuallly the application gets stuck in at the point the server is affected without adding to the numbers.

Which log files can I use to determine what caused this and when?
Im assuming it is the statserver which was either restarted or reset.

[/quote]
CCPulse does not have log files.
You said "due to some network issues", and then "Im assuming it is the statserver which was either restarted or reset" - either of two you can easily check whether statserver was restarted checking its log files.

Fra