Skip to content

Log Files

Where MetaMiner writes its logs, what each file contains, and which file to open for a Power BI question.

Which log for which question

Question Open
Why did Test Connection or Apply fail? admin.log (validation runs in MMA)
Is a collector failing or throttled? statereport.log, then server.log around the same time
Did the server start? slc.log, server.start.log
Are the usage dashboards slow or empty? webapps.log, webapps.queries.log
Who changed the configuration? mma-audit.log

MetaMiner Server and MMA logs

Server and MMA logs are in the server\logs\ folder of the installation, for example C:\Program Files\Infolytik\MetaMiner\server\logs\. In MMA, use File > Open Log Folder.

File Content Rotation
server.log MetaMiner Server (MMS) runtime: collection, errors, warnings Daily and at 10 MB, kept 14 days
slc.log Service lifecycle: start, ready, stop Daily and at 10 MB, kept 14 days
server.start.log Service launcher output and startup properties Rewritten at each start
statereport.log Hourly server state report, including per-collector Power BI status Kept 14 days
admin.log MetaMiner Administrator (MMA) activity, including Power BI validation details At 5 MB
mma-audit.log Configuration changes made in MMA Daily and at 10 MB, kept 90 days
clients-activity.log MetaMiner Client (MMC) connections and actions Kept 90 days
webapps.log Web Apps service, including the Power BI usage dashboards Daily and at 50 MB, kept 30 days
webapps.queries.log Slow dashboard queries Daily and at 50 MB, kept 30 days
diagnostic.log Diagnostic notifications At 5 MB
threads.log Thread dumps taken automatically on slow actions At 5 MB
longquery.log Slow MMDB queries At 5 MB
query.log MetaQuery activity Kept 14 days
queryagent.log MetaQuery agent process At 5 MB
mmdb.log MMDB update activity Kept 10 days
postgres.log, influx.log Embedded database and metrics storage output Kept 3 days
gc-*.log Java garbage collection 40 files of 10 MB
orm-warnings\, parser-warnings\ Rows that could not be stored, SQL that could not be parsed -

Rotated files are zipped in the same folder, for example server-2026-10-24-1.log.zip. The embedded database writes its own logs to server\data\mmdb\logs\.

See Log Files in the reference section for the full list.

What logs contain

Logs can include tenant IDs and workspace, item and user names. Review your organisation's policy before you send logs.

Send logs to Infolytik Support

Use File > Create Log Bundle... in MMA; see Log Bundle for Support. It copies the logs while the server runs and creates one zip.

To review the logs yourself first, use File > Analyze Logs...; see Analyze Logs.

MetaMiner Client logs

  1. Start the MetaMiner Client.
  2. Choose File > Open MetaMiner Log Folder.
  3. Select all files, right-click and choose Send to > Compressed (zipped) folder.
  4. Send the zip to support@infolytik.com.

Image of the MetaMiner Client File menu with Open MetaMiner Log Folder highlighted

../../images/admin/mmc-open-log-folder.png

Restart the server with clean logs

Infolytik Support may ask you to restart with an empty log folder so the logs cover only the problem period.

  1. Create a log bundle first if you may need the old logs.
  2. In MMA, click Stop Server and wait until it stops.
  3. Choose File > Purge Logs, or delete the contents of server\logs\ in Windows Explorer.
  4. Click Start Server.

Stop before purging

Purge Logs deletes everything in the logs folder. Always stop the server first.