This can be done in 2 different ways. This first method described here is recommended as the easiest to implement if you are not too tech savvy.
Important: The logaholic.php file will connect back to the database server that contains your Logaholic information. So, make sure you use a fully qualified hostname (i.e not just 'localhost') as the database server name in your Logaholic database configuration settings (Check Global Settings to change this if necessary, or edit the logaholic.php file manually). Some database servers won't allow connections from a different machine. In that case, please read this work around.
2. Using FTP to Transfer Log Files
In your Logaholic, create a profile for each website you want to track. Next, you'll need to copy (ftp) the log files from your different servers to the server Logaholic is installed on. Simply configure your profiles to read the copied log files on the local machine. Of course, the catch is that you will need to copy the most recent log file data each time you want to update your statistics, so you will probably want to automate this in some way.
Alternatively, you can use Logaholic's built in FTP mode (use the FTP Download method on the Data Collection tab). This will automatically transfer the most recent log data and keep a local copy of the log file. However, Logaholic's FTP mode currently only accepts a single log file per profile, so if your web host automatically archives your log data into more than one file, you will get holes in your reporting if you don't update your stats in Logaholic on time. To avoid that from happening, make sure you automate Logaholic updates and let it run before your web host rotates/archives your log files.