-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please don't delete info.level #173
Comments
Winston's logform docs state that 'info' objects should always have 'level' and 'message' fields. Some downstream transforms and transports can rely on this. Instead the 'ecsStringify' will handle excluding the 'level' field from the stringification. Closes: #173
@doanthai Thanks for the issue! I have a fix started. |
Winston's logform docs state that 'info' objects should always have 'level' and 'message' fields. Some downstream transforms and transports can rely on this. Instead the 'ecsStringify' will handle excluding the 'level' field from the stringification. Closes: #173
Hi @trentm, I ran the basic branch: main input
output
|
Hi,
I just update version
@elastic/ecs-winston-format
from1.3.1
to1.5.0
and see an error about logging in console look likeIn old version,
undefined
is log level of message. When I check code, I see you deleteinfo.level
at bellow code:Though have
Symbol.for('level')
but some other transports still read level from info. So can you don't delete level in info object.The text was updated successfully, but these errors were encountered: