When you contact QuerySurge Support, in many cases you will be asked to provide logs to Support in order to help diagnose an issue. Each QuerySurge component has its own logs, and you may be requested to send logs for one or more components.
Note: It will help QuerySurge Support identify your issue more quickly if you send logs for the specific date and time where the issue occurred.
QuerySurge App Server Logs
Windows: <QuerySurge Install Dir>\QuerySurge\tomcat\logs\querysurgetomcat-stderr-<date>.log
Linux: <QuerySurge Install Dir>/opt/QuerySurge/tomcat/logs/catalina.<date>.log
QuerySurge Agent Logs
Windows: <QuerySurge Install Dir>\QuerySurge\agent\logs\querysurgeagent-stderr.<date>.log
Linux: <QuerySurge Install Dir>/QuerySurge/agent/qsagent-err.log
QuerySurge Statsmon Logs
Windows: <QuerySurge Install Dir>\QuerySurge\statsmon\logs\querysurgestatsmon-stderr.<date>.log
Linux: <QuerySurge Install Dir>/QuerySurge/agent/qsstatsmon-err.log
QuerySurge MySQL Logs
Windows: <QuerySurge Install Dir>\QuerySurge\mysql\data\<machinename>.err
Linux: <QuerySurge Install Dir>/QuerySurge/mysql/data/mysql.log
Note: MySQL has a number of specialty logging options. If you are using one of these (typically at the request of QuerySurge Support), you may need to locate a different log file to send to Support.
Important Note: Any QuerySurge logs may contain sensitive data. Please review any logs before sending them to QuerySurge Support, and determine that the log contents may be shared externally. Agent logs are of special concern, and are likelier to have sensitive data if you have used Debug Level 1 or 2 (see this article for information about the Agent Debug mode). This is especially true for Debug Level 2. Because of this, Agent logs should be carefully examined before sending to Support.