You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
and inside LogRecord->with there is missing formatted key to be copied over, so if any previous processor set any information inside LogRecord->formatted it will be lost.
Seems like same issue with toArray
The text was updated successfully, but these errors were encountered:
@Seldaek Yes, since we use custom logic to format all records.
Basically logic was as follows:
Create new structure to formatted property
Every processor adds it's own information to this formatted to the place where it needs to be
Formatter converts log record to JSON or Plain text log, but keeps structure from formatted. Means formatters only responsible for final output, but not structure of log itself
With this approach formatters does not care about structure, just how format LogRecord to string. Processors are responsible for it's own parts of LogRecord->formatted processing.
E.g. Adding information about current user can come from 3 different processors and it merges under key LogRecord->formatted->user
Right, exactly my thinking @stof - sounds to me like these processors should all record stuff in extra as they are meant to, and then the final formatter can use the info in context/extra to generate the final formatted record.
Monolog version 3.2.0
When
PsrLogMessageProcessor
processes message, it returns new instance ofLogRecord
using codeand inside
LogRecord->with
there is missingformatted
key to be copied over, so if any previous processor set any information insideLogRecord->formatted
it will be lost.Seems like same issue with
toArray
The text was updated successfully, but these errors were encountered: