Forum Moderators: DixonJones
We have now moved to a .NET application and I have asked my server providor to install awstats, for my purposes. But after nearly 8 weeks it's become obvious to me that he has difficulties extracting and installing historical data and configuring awstats for .NET
How straight forward should the full instalation and migration of data be from a linux server to .NET?
Are there support groups that can guide him through?
The problem part is however to get it running. AwStats is written in the Perl language. To make the statistics package work, you first have to install the Perl interpreter on the .NET server, which might be very difficult to nearly impossible depending on the setup.
If it is no problem for you, I would advice you to just send periodically the logfiles of the .NET server to one of your linux boxes and use an AwStats implementation under Linux to interpreted the logs.
I would advice you to just send periodically the logfiles of the .NET server to one of your linux boxes and use an AwStats implementation under Linux to interpreted the logs
We're not wanting to retain any of the linux boxes. So if this is the case what's the best option?
Should we just start with a new system [ for my elementary purposes ] that's cheap and compatible to .NET and extract the historical data that we have to the new stats package?
[edited by: Whitey at 5:52 am (utc) on Feb. 10, 2008]
If it is no problem for you, I would advice you to just send periodically the logfiles of the .NET server to one of your linux boxes and use an awstats implementation under Linux to interpreted the logs.
Finally the server admin got awstats working a couple of weeks ago.
Does anyone know if it's possible to use the "live update" button to refresh the stats directly from the .NET server , like it does on a Linux server?
btw - I wouldn't bother with all of this, except with 12 sites I need something quick and simple to provide a one page comprehensive summary solution which i've found awstats to be good at.