Accessing the Metric Insights Log files

Metric Insights has a number of different pieces to the application.  The log files generated by each of these programs help us to diagnose any issues you may be having with your installation of Metric Insights.  Below you'll find a list of the log files we use and where they are located.

1. Easiest way to access error Log files - via the Status Monitor

Easiest way to access error Log files - via the Status Monitor
  1. There is a Get error logs button on the Status Monitor > Application Errors tab page.
  2. From the pop-up, you can download the logs (zipped) to your local machine, send them to our support team for assistance, or both.

2. Manually access Log Files

Logs can exist in different locations depending on the Operating System:

  • Debian
  • CentOS/RHEL

2.1. Debian log files

1.  Apache error log

  • /var/log/apache2/error.log
  • /var/log/apache2/pyinsight-error.log
  • /var/log/apache2/ssl_access.log

2,   Report Generator Log – most recent file matching:

  • /var/log/mi.debug

3.  Data Fetch Request Broker Log: most recent file matching:

  • /opt/mi/iv/data/temp/broker/*.log

4.  Data Collector Logs:

  • /opt/mi/datacollector/logs/insight.log
  • /opt/mi/datacollector/logs/query.log

5.   Mysql:

  • /var/log/syslog

2.2. CentOS / RHEL log files

1.  Apache error log

  • /var/log/httpd/error_log
  • /var/log/httpd/pyinsight-error.log
  • /var/log/httpd/ssl_access.log

2.  Report Generator Log – most recent file matching:

  • /var/log/mi.debug

3.  Data Fetch Request Broker Log: most recent file matching:

  • /opt/mi/iv/data/temp/broker/*.log

4.  Data Collector Logs:

  • /opt/mi/datacollector/logs/insight.log
  • /opt/mi/datacollector/logs/query.log

5.  Mysql:

  • /var/lib/mysql/hostname.err  [where hostname is the name of the server.]