/ /

Request Ops Manager Server Logs

You can collect Ops Manager application server logs from one or more Ops Manager servers through the Ops Manager Admin UI or the Public API. Ops Manager collects the logs in a background job, compresses and encrypts them, and stores the resulting archive in the Application Database. You can then download the archive as a single .tar.gz file.

Each request can collect any combination of the following log types:

Log Type	Description
Application	Ops Manager application operations logs (`mms0.log` and rotated files).
Migration	Ops Manager database migration logs (`mms-migration.log`).
HTTP Access	Ops Manager HTTP access logs (`mms0-access.log` and rotated files).

To request, monitor, and manage Ops Manager server log collection jobs through the Admin UI, you must have the Global Owner role.

Considerations

Before you request Ops Manager server logs, review the following limits.

Ops Manager considers a server active if it sent a heartbeat to the Application Database within the last 20 seconds. The server selection dropdown lists only active servers.
Ops Manager sets the default expiration of a job to 7 days from the job creation date. You can extend the expiration up to 28 days from that creation date. You cannot extend a job that has already expired.
You cannot delete a job that is still in progress.
You cannot download logs from a job in the EXPIRED or IN_PROGRESS state. You can download logs from a job whose status is SUCCESS or FAILURE. If a job partially failed, the archive includes only the log files that Ops Manager collected successfully.

Request Server Logs

Open the Logs page.

Click Admin, General, then the Logs tab.

Open the request form.

Click Request Ops Manager Logs. The Request Ops Manager Logs modal opens.

Choose which servers to include.

Use the multi-select dropdown to choose one or more Ops Manager servers. The dropdown lists only active servers. To collect logs from every active server, click the Select all link at the top of the dropdown list.

Choose which log types to collect.

By default, no log types are selected. Select the checkboxes for the log types you want to collect:

Checkbox	Collected logs
Application	Application operations logs (`mms0.log` and rotated files).
Migration	Database migration logs (`mms-migration.log` and related files).
HTTP Access	HTTP access logs (`mms0-access.log` and rotated files).

Apply a filter.

You can choose one of the following filter modes to limit the volume of logs collected:

Mode	Behavior
Filter by Size	Set the maximum uncompressed size, in bytes, per log type per server. Ops Manager reads from the most recent log file until it reaches the size limit.
Filter by Date Range	Set a time range. Ops Manager collects only the log lines whose timestamps fall in this range, with the size limit as a safety cap. The size limit defaults to the remaining configured size unless you set a specific value in Filter by Size. If the logs in your selected time range exceed the size limit, Ops Manager returns only the most recent logs up to that limit.

Submit the request.

Click Request Logs.

Ops Manager creates a background job, distributes one task per server and log type, and stores the resulting archive in the Application Database when the tasks complete. The page redirects to the Log Request History page.

Monitor and Download

The Log Request History page lists each request with these columns:

Column	Contents
Status	Current state of the job: `IN_PROGRESS`, `SUCCESS`, `FAILURE`, or `EXPIRED`.
Servers	Ops Manager servers included in the request.
Log Types	Log types included in the request.
Size	Total uncompressed size of the archive. You need this much free disk space to extract it.
Expiration	Date when Ops Manager automatically deletes the collected logs.
Actions	Available actions: Download, Extend, Delete, Retry, or Copy URL.

To download the archive of a successful or partially successful job, click the Download icon for that row. The archive uses the file name format om-logs_{timestamp}.tar.gz.

You cannot resume a download. If a download fails, restart it from the beginning.

The extracted archive uses the following layout:

<hostname>/
   application/
      mms0.log
      mms0.20260412.log
   http_access/
      mms0-access.log
      mms0-access.20260412.log
   migration/
      mms-migration.log

To download the archive programmatically, click Copy URL and pass the URL to the download endpoint.

Note

If you applied a date range and a size filter, and the logs in the range exceed the size limit, the row shows an info icon. Click the icon to see the specific server IDs and log types affected by truncation.

Extend Log Expiration

Ops Manager deletes collected logs 7 days after the job creation date. To keep the archive longer, extend the expiration. You can extend up to a total of 28 days from the original creation date. You cannot extend a job that has already expired.

Open the Log Request History page.

Click Admin, General, then the Logs tab. Click Log History.

Extend the job.

For the row you want to keep, click Extend. Ops Manager adds 7 days to the current expiration, up to the 28-day cap.

Retry a Failed Job

A job can fail in part or in full. When a job partially fails, Ops Manager keeps the archives that succeeded. You can still download the partial archive. To collect the missing log files, retry the job.

Open the Log Request History page.

Click Admin, General, then the Logs tab. Click Log History.

Inspect the failure.

For a failed row, click the info icon. The icon shows which server and log type combinations failed and the error message for each.

Retry the failed tasks.

Click Retry. Ops Manager reruns only the tasks that failed and preserves the tasks that succeeded.

Delete a Job

Warning

Deletion is immediate. Ops Manager removes the job, all task summaries, and every collected log file from the Application Database. You cannot delete a job that is still in progress.

Open the Log Request History page.

Click Admin, General, then the Logs tab. Click Log History.

Delete the job.

For the row you want to remove, click Delete. Ops Manager deletes the job and its archive immediately.

Use the API

To request, monitor, and manage Ops Manager server log collection jobs programmatically, see Ops Manager Server Log Collection Jobs.

Back

Manage Application Logs

Manually Update Manifest