Fix Magento logging

[adamlavery]

Preconditions (*)

1. Install any version of Magento 2

Steps to reproduce (*)

1. Set mode to Developer
2. Enable Debug

Expected result (*)

1. Debug log will contain debug logs only
2. Cron log will contain cron logs only
3. System log will contain system logs only

Actual result (*)

1. Debug log contains everything that is also logged to cron,log and system.log
2. System log contains everything that is also logged to cron.log
3. Cron log only contains cron logs - got that one right!

---

• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

Please address the mishandling of logs so that logs contain just what is necessary and desired.

• Debug log should contain just logs identified as "debug"
• System log should not duplicate everything written to cron.log

As a further request, please address the issue of "broken references" that fill the system (and debug logs!). There should be a switch to disable these logs. In the main they are not useful and cannot/will not be addressed. "Broken references" are always going to happen when using extensions/themes from multiple sources. Very few will be interested in these - the majority of us are not so these are pointless and just make reviewing logs more difficult.

[m2-assistant]

Hi @adamlavery. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!

[dverkade]

Issues waiting for confirmation should not be closed automatically.

[rosemariepopescu]

Waiting for an answer here as well! Issue is pretty straight forward, clearly explained and it bothers us all developers!!

[fredden]

@sidolov please can you re-open this so it can be triaged. It looks like it was closed by the stale robot by mistake.

[m2-assistant]

Hi @engcom-Lima. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Lima]

✔️ Issue confirmed

Issue got reproduced in 2.4-develop branch.

Description: Magento logs are not coming properly.

Pre-requisite:

• Fresh magento 2.4-develop should be installed.

Steps to reproduce:

1. Set mode to Developer
2. Enable Debug
3. Check logs in var/log/

Expected result:

1. Debug log will contain debug logs only
2. Cron log will contain cron logs only
3. System log will contain system logs only

Actual result:

1. Debug log contains everything that is also logged to cron,log and system.log
2. System log contains everything that is also logged to cron.log
3. Cron log only contains cron logs.

Screenshots:
Debug logs:

System log :

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.adobe.com/browse/AC-6767 is successfully created for this GitHub issue.

[m2-assistant]

✅ Confirmed by @engcom-Lima. Thank you for verifying the issue.
Issue Available: @engcom-Lima, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[engcom-Bravo]

Hi @adamlavery,

Thanks for your reporting and collaboration.

We have tried to reproduce the issue in Latest 2.4-develop instance and we are not able to reproduce the issue.Kindly refer the screenshots.

1. Debug log will contain debug logs only
2. Cron log will contain cron logs only
3. System log will contain system logs only

Hence we are closing this issue.

Thanks.

[adamlavery]

Ok, great. What release is this fix going in or has gone in? We can't see Jira tickets. Shouldn't there be a "Fixed in X.Y.Z" label?