Skip to content

Log Files

Every log file MetaMiner writes in a Power BI deployment, which process writes it, where it is, and how long it is kept.

Paths are relative to the installation folder, for example C:\Program Files\Infolytik\MetaMiner\. To send logs to Infolytik, create a log bundle instead of copying files by hand. For reading and analysing logs in the product, see Log Files and Analyze Logs.

Image of the MMA File menu with Open MetaMiner Service Log, Open Log Folder, Purge Logs and Create Log Bundle

../../images/help/mma-file-menu-logs.png

Which log for which problem

Problem Start with
Environment validation fails admin.log
Collection errors, throttling, missing data server.log, then statereport.log
Service does not start or stops server.start.log, slc.log
Dashboards do not load or are slow webapps.log, webapps.queries.log, webapps.start.log
MetaMiner Client problems client.log on the client machine
Memory problems gc-*.log, server.log, heap dumps

MetaMiner Server (service metaminer)

Folder: server\logs\. Rotated files are compressed to <name>-<date>-<n>.log.zip or <name>.<n>.log.zip.

File Content Rotation and retention
server.start.log Launcher output: Java options, property values and errors before logging starts Written by the service launcher
server.log Main log: collectors (by name, for example WORKSPACE_SCAN), processing, errors of all components Daily and at 10 MB, kept 14 days
slc.log Service lifecycle: start, ready, reload and stop events Daily and at 10 MB, kept 14 days
statereport.log Hourly state report, including the Power BI environments and their collectors Daily and at 25 MB, kept 14 days
clients-activity.log MetaMiner Client connections and sign-in attempts Daily and at 10 MB, kept 90 days
mmdb.log MetaMiner Database messages and schema updates Daily and at 5 MB, kept 10 days
postgres.log Embedded PostgreSQL start and stop as seen by the MMS Daily and at 2 MB, kept 3 days
longquery.log MetaMiner Database queries that ran longer than expected 5 MB per file, 10 files
diagnostic.log Diagnostic and notification activity 5 MB per file, 10 files
threads.log Thread dumps written when an action takes too long, or on request 5 MB per file, 10 files
gc-<timestamp>.log Java garbage collection 10 MB per file, 40 files
restarter.log Service restarter helper, when used 5 MB per file, 10 files

Other diagnostic output of the server:

Location Content
server\java_pid<nnnn>.hprof Heap dump written on an out-of-memory error. As large as the heap
server\health\incidents-<date>.jsonl Summary of detected problems, used by the MMA health indicator. Kept 90 days
mm-pbi-dumps\ in the Java temp folder Copies of workspace scan results MetaMiner could not read, for diagnosis. At most 4 GB, 10 files, 30 days
server\data\mmdb\logs\ PostgreSQL's own logs for the embedded MetaMiner Database

MetaMiner Administrator

Folder: server\logs\ (the MMA runs on the server).

File Content Rotation and retention
admin.log MMA activity, Power BI environment validation with the HTTP status of each Microsoft call, saves 5 MB per file, 10 files
admin.start.log MMA launcher output Written by the launcher
mma-audit.log Record of configuration changes made in the MMA Daily and at 10 MB, kept 90 days

MetaMiner Web Apps (service MetaMinerWebApps)

Folder: server\logs\.

File Content Rotation and retention
webapps.log Dashboard and web app requests and errors Daily and at 50 MB, kept 30 days
webapps.queries.log Dashboard queries slower than 5 seconds, and Meta Query web statements Daily and at 50 MB, kept 30 days
webapps.start.log Launcher output Written by the launcher

MetaQuery agent

Folder: server\logs\.

File Content Rotation and retention
queryagent.log Meta Query agent activity 5 MB per file, 10 files
queryagentquery.log Queries run by Meta Query 5 MB per file, 10 files
queryagentlongquery.log Meta Query queries that ran long 5 MB per file, 10 files
queryagent.start.log Launcher output Written by the launcher

MetaMiner Client

Folder: %APPDATA%\MetaMiner\logs\ for each Windows user. Open it from the MMC with File > Open MetaMiner Log Folder.

File Content Rotation and retention
client.log MMC activity and errors 5 MB per file, 5 files (client.<n>.log.zip)
client.start.log Launcher output Written by the launcher

Managing log files

  • The MMA File menu opens the most-used logs (Open MetaMiner Administrator Log, Open MetaMiner Service Log, Open Diagnostic Log, Open Threads Log) and the folder (Open Log Folder).
  • File > Purge Logs deletes the contents of server\logs\. Create a log bundle first if you may need support.
  • File > Analyze Logs... scans a logs folder and opens a summary report in your browser.

Logs contain tenant metadata

Server logs name workspaces, items and user principal names. Share them only with Infolytik Support, through the channel support gives you.