Skip to content

[Issue] Use Logger implementation based on deployment configuration #29600

Closed
@m2-assistant

Description

@m2-assistant

This issue is automatically created based on existing pull request: #27379: Use Logger implementation based on deployment configuration


Summary (*)

Magento 2.4-develop
Use Logger implementation based on deployment configuration

Examples (*)

  • Configure Magento to run in production mode
  • Add 'log' => [ 'type' => \Monolog\Logger::class, 'args' => ['name' => 'test']], line to app/etc/env.php file
  • Delete var/log folder
  • Run bin/magento s:s:d
  • Test that errors is logged to StdError stream
  • Test that var/log folder is not exists/empty

Proposed solution

Metadata

Metadata

Assignees

No one assigned

    Labels

    Component: LoggerFixed in 2.4.xThe issue has been fixed in 2.4-develop branchIssue: ConfirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedPriority: P3May be fixed according to the position in the backlog.Progress: doneReported on 2.4.0Indicates original Magento version for the Issue report.Reproduced on 2.4.xThe issue has been reproduced on latest 2.4-develop branchSeverity: S3Affects non-critical data or functionality and does not force users to employ a workaround.

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions