Skip to content

Analyze Logs

Scan a folder of MetaMiner logs from MMA and get an HTML report of errors, warnings and collection freshness, without sending anything off the machine.

Before you begin

  • MMA is running. The server does not need to be running.
  • You have a logs folder: the live server\logs\, a copy of it, or an unzipped log bundle from another server.

Steps

  1. In MMA, choose File > Analyze Logs....
  2. In Select a logs folder to analyze, choose the folder. It opens on server\logs\ by default.
  3. Wait while MMA shows "Analyzing logs...". Large folders can take a few minutes.
  4. Your browser opens the MetaMiner Log Analysis report.

The report is a local HTML file in your Windows temp folder (mm-log-analysis-*.html). Nothing is uploaded.

Image of the MetaMiner Log Analysis report in a browser, showing the Global summary cards and the Substrate freshness and pull status table with a Power BI row

../../images/admin/log-analysis-report.png

What the report shows

Section Content
Header Host, analysis time, time window covered by the logs
Global summary Counts of log entries, errors and warnings
Substrate freshness & pull status Per environment: Platform, Environment, Cycle, Last success, Last-known-good, State (for example FRESH, STALE, IN_PROGRESS, NEVER, FAIL)
Errors, Warnings One card per issue type with counts and sample lines
Notable Informational findings worth a look
System Server facts found in the logs, such as garbage collection and restarts

The scanner recognizes the MetaMiner log types (server.log, admin.log, slc.log, gc-*.log and others) and also reads rotated .log.zip files in the folder.

Year approximate

Some log lines carry no year. If the report cannot determine it with confidence, the header shows "year approximate".

Use the report

  • Start with Errors and the State column of the freshness table. A STALE or FAIL Power BI environment has not completed a snapshot cycle recently.
  • Use the sample lines to search server.log around the same time; check statereport.log for the collector involved. See Collection Status.
  • Attach the report to a support ticket together with a log bundle.

Next steps