Products
- Muse^® Federated Search, today’s most powerful of its kind, is known as best of multiple target searching and content normalization to a single data model.
- Muse^® Proxy is a highly customizable multi-platform proxy server, easy to use and manage, acting as a gateway to authenticated content.
- Muse^® Harvest is based on different types of controlled extraction, such as search, date or feed based. it features a consistent delivery record format.
  - Overview
  - Features
- Muse^® Hybrid brings a powerful new approach to content discovery by combining real-time global federated searching with high performance central indexed searching.
  - Overview
  - Features
Services
Support
- FAQ
- Downloads
About
Contact

How do I send the Muse Proxy log files for statistical analysis?

Categories:
General
Muse Proxy

Statistics are offered as a service to Muse Proxy customers, no matter they are locally hosted or on cloud. The statistics are generated from content of the Muse Proxy log files:
– access log (access.log).
– statistics log (MuseProxyStatistics.log).
More details about the Muse Proxy log files in the Muse Proxy Advanced Configuration manual, chapter “2.9 Log Files“.
For the instances hosted by MuseGlobal, there is nothing to be done, we take care of everything.
For the locally hosted instances, the main requirement is to upload from your server on a daily basis the 2 log files – access.log and MuseProxyStatistics.log – corresponding to the previous day, onto our FTP repository – ftp.museglobal.com – from where we will further pick them up for processing into the statistics platform.
The log files upload is carried out by means of scripts driven by the system’s scheduler/cron, depending on the Operating System. We provide such scripts.
The main requirement for the upload scripts is to have a single log file per day and with the date stamp in their filenames, e.g. access-yyyyMMdd.log and MuseProxyStatistics-yyyyMMdd.log. Refer to this FAQ for making the required logging changes.

Download the patch containing the necessary scripts from here. Copy the downloaded archive into ${MUSE_HOME} and extract it. The content is deployed into the following location on disk: ${MUSE_HOME}/proxy/tools.

Windows OS

Make sure that the patch is already deployed.

Edit the MuseProxyLogsUpload.xml file and replace the PLACE_HERE_THE_FTP_USERNAME and PLACE_HERE_THE_PASSWORD placeholders with the actual values as provided by the MuseGlobal Support Team.
Open a CMD window, change directory to %MUSE_HOME%/proxy/tools/ and run the MuseProxyLogsUploadAnt.bat script. This is for test purposes to make sure the upload script works.
Create a scheduler job in Windows to run the %MUSE_HOME%/proxy/tools/MuseProxyLogsUploadAnt.bat script each day after midnight, for example at 1:00 AM. There are many online tutorials for setting up a basic task, like for example here.

Linux OS

Make sure that the patch is already deployed.

Edit the MuseProxyLogsUpload.xml file and replace the PLACE_HERE_THE_FTP_USERNAME and PLACE_HERE_THE_PASSWORD placeholders with the actual values as provided by the MuseGlobal Support Team.
Open a shell session on the server, change directory to ${MUSE_HOME}/proxy/tools/ and change the permissions of the MuseProxyLogsUploadAnt.sh file to allow execution. Make the same for the ${MUSE_HOME}/proxy/tools/apache-ant-1.10.13/bin/ant file.
Edit the MuseProxyLogsUploadAnt.sh and make sure the value for MUSE_HOME points to the correct location on disk of Muse Proxy.
Run the MuseProxyLogsUploadAnt.sh script. This is for test purposes to make sure the upload script works.
Create a cron job to run the ${MUSE_HOME}/proxy/tools/MuseProxyLogsUploadAnt.sh script each day after midnight, for example at 1:00 AM.