Upload server logs

The XML export tells FM Fathom what your solution *is*. Server logs tell it what your solution *does*: what actually runs, how often, how slowly, and what breaks. Uploading them unlocks four areas of the portal (Performance, Schedules, Incidents, and Server Logs) plus production evidence throughout.

What you need

• Access to your FileMaker Server's Logs folder
• The Upload logs capability on your account (ask your admin if uploads are rejected)

Get the whole set, not one file

Two habits that make everything downstream better:

• Use "Download All Logs". In the FileMaker Server Admin Console, don't save a single log; the Download All Logs button hands you the complete set in one zip, which is exactly what FM Fathom wants.
• Turn on Top Call Stats. It's off by default in the Admin Console. With it on, the server records which operations cost the most, and FM Fathom gets a real sense of which tables, fields, and scripts are expensive in production. Highly recommended.

Upload

1. On the server, grab the complete log set (see above) as a zip. That's the natural unit: don't pick through it, just take it all.
2. In Workspace, on the client's card, drop the .zip onto the Server logs target. A single .log file works too.
3. Wait for Parsing logs to finish. Large bundles are normal (hundreds of megabytes, millions of lines) and interrupted uploads can resume.

FM Fathom recognizes the standard FileMaker Server log families: Event, Access, TopCallStats, ClientStats, Stats, ScriptEvent, the Data API and OData logs, and more. Anything it doesn't recognize is skipped and counted in the upload summary, never an error. Overlapping date ranges from log rotation are handled; uploading the same bundle twice doesn't double anything.

One server, many databases

FileMaker Server logs are server-wide: one bundle carries every hosted database. Each file in FM Fathom keeps a list of the database names that belong to it, and log ingest keeps only the matching lines (dropped lines are counted in the summary).

You usually don't set this up by hand. If the bundle contains only one database, FM Fathom discovers the name automatically. If it contains several, the upload pauses and asks you which names belong to this file. You can review the mapping anytime under File Options, in the Server logs card. The same solution can go by different names on different servers; list them all.

What logs unlock

• Server Logs: observed production activity, what actually runs and what breaks.
• Performance: server health and where server time actually goes.
• Schedules: how your server schedules really behave, on a zoomable timeline.
• Incidents: reconstruct what was happening around a moment in time.
• Production evidence elsewhere: observed-usage panels on entity pages, a production-activity split in Unused elements, and the log-backed AI tools.

Every log-based number in FM Fathom states its coverage window ("based on logs covering March 3 to June 12"), so an absence of evidence is never dressed up as evidence of absence.

Related

• Production insight: a tour of the four areas logs unlock
• Quick start if you haven't uploaded XML yet