Trader Information
Back to topOverview
Back to topLogs Manager Pro is a self-contained, on-site logging and monitoring toolset for the store admin. It is a standalone extension — it does not connect to, depend on, or transmit data to any external company or third-party service. Every feature runs locally inside your own store: log files, request and email records never leave your server.
The extension gives the admin a complete toolset for working with log files. Out of the box there is no admin tooling for logs — they grow without bound, become hard to open, and turn analysis into a tedious process. Logs Manager Pro rotates oversize log and report files into compressed archives, keeps a configurable number of recent copies, and adds admin grids for Monolog records, REST and GraphQL traffic and outgoing emails — with filters, full-text search, secret masking and per-feature retention. Once installed it is fully usable from the admin with no extra setup or sign-up.
Account & Pricing
No separate account is required to use this extension. There is no external service or company to connect to, so nothing is created during or after installation and there is no sign-up step. Because no third-party service is involved, no additional service fees of any kind apply — the extension price is all you pay.
Features
- Automatic rotation of var/log/ and var/report/ files into ZIP archives when they exceed a configurable size threshold.
- Configurable retention — keep the N most recent rotated copies, prune the rest.
- Compression ratio of 70 to 90 percent on real log files. A 10 MB file typically rotates to 0.5–1 MB.
- Admin grid for Monolog-formatted system.log records with pagination, sorting and full message popup.
- Filtering by date and time range, channel, file name, log level and full-text description.
- WebAPI request and response log for every REST call, with full headers and body capture.
- GraphQL request and response log with an option to log mutations only and to skip selected operation names.
- Outgoing email log with HTML and plain text body preview, delivery status and the transport error message on failure.
- Secret masking — sensitive headers and JSON keys are masked or removed before storage. Configurable word list.
- Per-feature retention windows for the database-backed logs. Daily cleanup cron.
- Granular ACL — separate resources for View, Download, Clear All on each grid.
File rotation
A cron job sweeps var/log/ every four hours and, when enabled, also var/report/. For each file larger than the configured threshold the module creates a timestamped ZIP archive next to the original, truncates the source file to zero bytes and then prunes older archives so that at most the configured number of rotated copies remains. The active log file stays in place — the admin grid keeps reading it.
Defaults: 20 MB threshold, 5 archive copies kept. Both values are configurable in the admin.
Logs grid
The Logs grid parses Monolog records from system.log into a paginated, filterable table. Each row carries the date, time, channel, level, source file and a trimmed description. Click the description to open the full message in a popup with Prev and Next navigation through the current filter result.
Available filters:
- Date range and time range.
- Monolog channel (main, third-party module channels).
- Source file name substring.
- Description substring (full-text search inside the message).
- Log level multiselect (DEBUG, INFO, WARNING, ERROR, CRITICAL).
A Columns dropdown toggles individual columns and a Default View dropdown saves filter and column combinations as named views.
WebAPI logs
When enabled, every REST request that hits the WebAPI front controller is captured into a dedicated database table with the HTTP method, URL, headers, body, response code, response headers, response body, client IP, end-to-end duration and timestamp. A per-row drill-in shows the full payload on both sides.
Filtering controls:
- Log Request Methods — multiselect over GET, POST, PUT, DELETE, PATCH. Empty means log all methods.
- Endpoint Filter Mode — All Endpoints, or Only Specific Endpoints from the registered REST routes multiselect.
- Excluded Paths — substrings, one per line. Requests whose URL contains any of these are dropped before write.
A retention window (in hours, default 720 — 30 days) ages out old rows nightly. A value of zero disables cleanup.
GraphQL logs
GraphQL traffic is captured into the same table as REST. The GraphQL section adds two GraphQL-specific knobs: Log Only Mutations to skip query operations and log only data-changing ones, and Excluded Operations for an explicit operation-name blocklist (for example IntrospectionQuery). Retention is shared with the WebAPI cleanup cron.
Email logs
When enabled, every outgoing email handed to the mail transport is captured with the From, To, CC, BCC, Subject, HTML body, plain text body, delivery status (success or failed) and the transport error message on failure. The body preview is a copy of what the transport actually saw — useful when a notification looks fine in admin but renders wrong in the recipient inbox.
An independent retention window (default 720 hours) ages out old rows nightly. A Clear All bulk action gated by its own ACL resource truncates the table on demand.
Security
Secret masking is built into the WebAPI and GraphQL capture path:
- Off — no masking; raw values are stored as captured.
- Mask Values (default) — values for keys whose name contains any configured secret word are replaced with a fixed mask before storage.
- Remove Keys — matching keys are dropped from the serialized representation entirely.
The default Secret Words list covers password, token, secret, authorization, api_key and credit_card. Extend the list to match the headers and JSON keys used by your integrations. The Email log captures only what the transport saw — sensitive content in transactional templates is the merchant's responsibility.
ACL
Each grid is a separate ACL resource. Read-only operators can be granted the View resources without any Clear All resource. Each Clear All bulk action is its own resource so that destructive operations can be reserved for senior admins.
Demo
To get a demo version of the extension, please contact our technical support. In the letter, indicate your name and surname, name of the extension, email address, and website URL. The demo is valid for 14 days. After 14 days, you agree to remove the extension demo from your site and from wherever it was installed.
Technical Specifications
Back to topSeller profile
Seller contact
Current Version
2.2.0
Adobe Commerce platform compatibility
Adobe Commerce (cloud): 2.4 (current)
Adobe Commerce (on-prem): 2.4 (current)
Magento Open Source: 2.4 (current)
Type
Stable Build
Updated
03 July, 2026
Categories
Extensions, Site Optimization, Hosting, Site Monitoring, Performance
Documentation
License Type
Policy
Quality Report
Back to topAll tests were conducted on the latest versions of Adobe Commerce that existed for the compatible release lines at the moment of the extension submission. Latest versions of all other software were used, as applicable.
Release Notes
Back to top2.2.0:
- Compatible with Adobe Commerce (cloud) : 2.4
- Compatible with Adobe Commerce (on-prem) : 2.4
- Compatible with Magento Open Source : 2.4
- Stability: Stable Build
-
Description:
LogsCore: Switched admin log templates to the Escaper service instead of block escape helpers.
2.1.9:
- Compatible with Adobe Commerce (cloud) : 2.4
- Compatible with Adobe Commerce (on-prem) : 2.4
- Compatible with Magento Open Source : 2.4
- Stability: Stable Build
-
Description:
LogsCore: Add email and webapi log management features. Added support Magento 2.4.8-p4 and Adobe Commerce 2.4.8-p4
2.1.8:
- Compatible with Adobe Commerce (on-prem) : 2.4
- Compatible with Magento Open Source : 2.4
- Stability: Stable Build
-
Description:
Added support Magento 2.4.8-p4 and Adobe Commerce 2.4.8-p4
2.1.7:
- Compatible with Adobe Commerce (on-prem) : 2.4
- Compatible with Magento Open Source : 2.4
- Stability: Stable Build
-
Description:
Refactored code.
2.1.6:
- Compatible with Adobe Commerce (on-prem) : 2.4
- Compatible with Magento Open Source : 2.4
- Stability: Stable Build
-
Description:
The functionality for uploading logs to cloud storages, such as Dropbox, Google Drive, and MS OneDrive, has been removed. This is now handled by the Backup Pro module.
2.1.5:
- Compatible with Adobe Commerce (on-prem) : 2.4
- Compatible with Magento Open Source : 2.4
- Stability: Stable Build
-
Description:
Added support Magento 2.4.8-p3 and Adobe Commerce 2.4.8-p3
2.1.4:
- Compatible with Adobe Commerce (on-prem) : 2.4
- Compatible with Magento Open Source : 2.4
- Stability: Stable Build
-
Description:
Added support Magento 2.4.8-p2 and Adobe Commerce 2.4.8-p2
2.1.3:
- Compatible with Adobe Commerce (on-prem) : 2.4
- Compatible with Magento Open Source : 2.4
- Stability: Stable Build
-
Description:
Added support Magento 2.4.8-p1 and Adobe Commerce 2.4.8-p1
2.1.2:
- Compatible with Adobe Commerce (on-prem) : 2.4
- Compatible with Magento Open Source : 2.4
- Stability: Stable Build
-
Description:
Added support Magento 2.4.8 and Adobe Commerce 2.4.8
2.1.1:
- Compatible with Adobe Commerce (on-prem) : 2.4
- Compatible with Magento Open Source : 2.4
- Stability: Stable Build
-
Description:
Added support Magento 2.4.7-p5 and Adobe Commerce 2.4.7-p5
2.1.0:
- Compatible with Adobe Commerce (on-prem) : 2.4
- Compatible with Magento Open Source : 2.4
- Stability: Stable Build
-
Description:
Added support Magento 2.4.7-p4 and Adobe Commerce 2.4.7-p4
2.0.9:
- Compatible with Adobe Commerce (on-prem) : 2.4
- Compatible with Magento Open Source : 2.4
- Stability: Stable Build
-
Description:
Added support Magento 2.4.7-p3 and Adobe Commerce 2.4.7-p3
2.0.8:
- Compatible with Adobe Commerce (on-prem) : 2.4
- Compatible with Magento Open Source : 2.4
- Stability: Stable Build
-
Description:
Added support Magento 2.4.7-p2 and Adobe Commerce 2.4.7-p2
2.0.7:
- Compatible with Adobe Commerce (on-prem) : 2.4
- Compatible with Magento Open Source : 2.4
- Stability: Stable Build
-
Description:
Added support Magento 2.4.7-p1 and Adobe Commerce 2.4.7-p1
2.0.6:
- Compatible with Adobe Commerce (on-prem) : 2.4
- Compatible with Magento Open Source : 2.4
- Stability: Stable Build
-
Description:
Fixed names of Google API classes. There were changing underscores to namespaces.
2.0.5:
- Compatible with Adobe Commerce (on-prem) : 2.4
- Compatible with Magento Open Source : 2.4
- Stability: Stable Build
-
Description:
Fixed Google Drive connection
2.0.4:
- Compatible with Adobe Commerce (on-prem) : 2.4
- Compatible with Magento Open Source : 2.4
- Stability: Stable Build
-
Description:
Added support Magento 2.4.7 and Adobe Commerce 2.4.7
2.0.3:
- Compatible with Adobe Commerce (on-prem) : 2.4
- Compatible with Magento Open Source : 2.4
- Stability: Stable Build
-
Description:
Added support Magento 2.4.6-p4 and Adobe Commerce 2.4.6-p4
2.0.2:
- Compatible with Adobe Commerce (on-prem) : 2.4
- Compatible with Magento Open Source : 2.4
- Stability: Stable Build
-
Description:
Added support Magento 2.4.6-p3 and Adobe Commerce 2.4.6-p3
2.0.1:
- Compatible with Adobe Commerce (on-prem) : 2.4
- Compatible with Magento Open Source : 2.4
- Stability: Stable Build
-
Description:
Fixed a bug with the Google Drive connection
2.0.0:
- Compatible with Adobe Commerce (on-prem) : 2.4
- Compatible with Magento Open Source : 2.4
- Stability: Stable Build
-
Description:
To check the correct connection to Cloud Storages, Test Connection buttons for Microsoft OneDrive, Google Drive, and Dropbox were added.
1.6.1:
- Compatible with Adobe Commerce (on-prem) : 2.4
- Compatible with Magento Open Source : 2.4
- Stability: Stable Build
-
Description:
Added support Magento 2.4.6-p2 and Adobe Commerce 2.4.6-p2
1.6.0:
- Compatible with Adobe Commerce (on-prem) : 2.4
- Compatible with Magento Open Source : 2.4
- Stability: Stable Build
-
Description:
Added support Adobe Commerce 2.4.6-p1
1.5.9:
- Compatible with Adobe Commerce (on-prem) : 2.4
- Compatible with Magento Open Source : 2.4
- Stability: Stable Build
-
Description:
Support Adobe Commerce (Magento) 2.4.6
Support PHP 8.1 and PHP 8.2
Support
Back to topThe best place to start if you need help with a specific extension is to contact the developer. All Adobe Commerce developers have both a contact email and a support email listed.
Contact Vendor