This article supports informed decision-making based on tracked activities:
Introduction
The Logs page provides a centralized view of system-generated messages that track activity and events within FORGE Content Manager. This section is essential for administrators, developers, and content managers who need visibility into actions such as content updates, publishing events, user activity, system warnings, and errors.
Accessing the Logs page
To access logs in the CMS, start by logging into FORGE Content Manager with the appropriate permissions. Once logged in, in the top-left corner, select the hamburger menu icon:
In the hamburger menu, select Logs:
This opens the Logs overview page. You can see the log messages by severity and application:
Reading logs
You can filter logs per
-
Severity level: It indicates the importance or urgency of the event that was recorded. The possible values are:
- Error only: Error messages.
- Warning (or more critical): Warning, and error messages.
- Debug (or more critical): Debug, warning, and error messages.
- Info (or more critical): Info, debug, warning, and error messages.
-
Application: Name of the FORGE's component that is the source of the log entry. The possible values are:
-
FrontEnd
-
BackOffice
-
ApplicationService
-
DistributionApi
-
DistributionService
-
DependencyService
-
NotificationDispatcher
-
BackOfficeMobile
-
Extensions
-
DivaDashboardHost
-
DivaWorker
-
DivaConnectorWebhook
-
DivaConnectorUnfolder
-
ExternalSearchService
-
- Correlation ID: Identifier that links many log entries.
- Date from/Date to: Date and time of the log entries.
When selecting a log entry, you access the following details:
- Message: The description of the tracked event.
- Correlation ids (if any): List of identifiers that link the tracked event to others.
- Properties (JSON): Structured information that describes the tracked event.
For example, this is an error log detail: