Edit - Magento Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Isn't the info level written to the system.log in production as well? This would not really solve the problem.

fritzmg
– fritzmg

2019-11-13 14:44:01 +00:00
Commented Nov 13, 2019 at 14:44
It depends what your log level is. If you are only logging errors on production, then this would stop it from being logged. The point is this isn't an error. By downgrading this to an info output, it stops it being identified as an error that needs attention

Adam
– Adam

2019-11-13 20:57:11 +00:00
Commented Nov 13, 2019 at 20:57
Magento also logs info by default in production mode. It doesn't log debug.

fritzmg
– fritzmg

2019-11-14 07:19:00 +00:00
Commented Nov 14, 2019 at 7:19

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »