You are browsing the documentation for version 4.2 of OroCommerce, OroCRM and OroPlatform, which is no longer maintained. Security Support ends in January 2024. Read version 5.0 (the latest LTS version) of the Oro documentation to get the updated information.
See our Release Process documentation for more information on the currently supported and upcoming releases.
OroLoggerBundle extends the MonologBundle functionality and provides:
- Error logs email notifications
- Ability to temporarily decrease log level
- Console commands logging
Error Logs Email Notifications
To enable error logs email notification, run the
oro:logger:email-notification command with semicolons separating the recipients, for example:
php bin/console oro:logger:email-notification --recipients="email@example.com;firstname.lastname@example.org"
To disable the notifications, run the command with the
--recipients option can be used to update the list of the recipients that will receive email notifications about the logged errors:
php bin/console oro:logger:email-notification --recipients=<recipients>
php bin/console oro:logger:email-notification --email@example.com;firstname.lastname@example.org;emailN@example.com'
Or you can configure recipients list using web interface from System > Configuration > System Configuration > General Setup > Application Settings > Error Logs Notifications section.
To change log level for email notifications , update the
monolog.handlers.swift.level parameter in
Temporarily Decrease Log Level
The default log level in the production environment is specified by the
oro_logger.detailed_logs_default_level container parameter
and equals to
error, you can update it in the application configuration.
To find problems, you can change this value for a specific time for a specific user by running the following command:
php bin/console oro:logger:level debug "1 hour" --email@example.com
debug is the log level and
1 hour is the time interval when the level is used instead of the default, the
--user option contains the email address of the user whose log will be affected.
You can also decrease the log level system-wide by skipping the
Logging Console Commands
All console commands are logged automatically on ConsoleEvents::COMMAND and ConsoleEvents::EXCEPTION. See ConsoleCommandSubscriber for more information.