Where Are All Those Log Files?

Metric Insights is a dockerized application. All logs from Docker containers are stored in one directory /opt/mi/log

All logs are redirected to the rsyslog service that will store them in files. Alternatively, Splunk logging service can be used.

Table of contents:

Log Files and Their Description

Metric Insights' logs follow the ISO-8601 standard of date and time representation.

  • Example: 2025-01-23 10:35:00

v7

Simple Installation

Types of Logs Description
console.log Log of the console container.
da-index-update.log Log of the index-update service in the data-analyzer container.
da-main.log Log of the data-analyzer service.
data-analyzer.log Log of the data-analyzer container.
dataprocessor.log Log of the dataprocessor container.
image-generator.log Log of the image-generator container.
logger-debug.log Detailed log of the logcollector service, which is responsible for generating patcher.log.
logger.log Log of the logcollector service, which is responsible for generating patcher.log.
mi.log Log of the PHP application (migration-tool).
mysql.log Log of the MySQL container (optional).
patcher.log List of applied patches.
patcher.debug Detailed log of the patcher service, explaining the processing of applying patches.
redis.log Log of the Redis container.
web.log Log of the web container.

Orchestrated Environments

Containers logs Logs are managed by the orchestration service and can be accessed using the respective commands:

  • Kubernetes (K8s): Use kubectl logs -n <namespace> <pod id>.
  • ECS: All logs are available in AWS CloudWatch.
  • Docker Swarm: Use the default Docker command: docker logs.

The table below describes log files available for all orchestrated environments.

Types of Logs Description
console.log Log of the console application.
da-index-update.log Log of the index-update service in the data-analyzer module.
da-main.log Log of the data-analyzer service.
logger-debug.log Detailed log of the logcollector service, which is responsible for generating patcher.log.
logger.log Log of the logcollector service, which is responsible for generating patcher.log.
mi.log Log of the PHP application (migration-tool).
patcher.log List of applied patches.
patcher.debug Detailed log of the patcher service, explaining the processing of applying patches.

v6

Simple Installation

Types of Logs Description
mi.log, mi.debug, mi.error General logs from the UI and generator (migration utility scripts)
dataprocessor.log Logs from the Data Processor service
seed.log Logs from the Data Processor Seed Node service
mysql.log mysql.log
web.log Logs from the Web Service

Orchestrated Environments

Types of Logs Description
mi.log, mi.debug, mi.error General logs from the UI and generator (migration utility scripts)
mi.system Sytem logs
network.log Network logs
patcher.log Logs from the Patcher
tomcat-access.log, application.log, insight.log Logs from the Dataprocessor

Additional Logging Options

Logging can be configured using System Variables that are available from the UI.

  1. To access, go to Admin > System > System Config
  2. Click the Edit (Gear) icon to see the Variable's description