We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I noticed when I was working with the ECS NodeJS loggers that Metadata fields weren't name spaced.
I can see one of three scenario's:
labels
tags
Here's an example configuration:
const logger = winston.createLogger({ format: ecsFormat(), level: "debug", defaultMeta: { defaultMeta: { 'environment': 'dev' } }, transports: [ new winston.transports.Console() ] })
and a resulting output:
{ "@timestamp": "2021-08-20T15:43:32.147Z", "log.level": "debug", "message": "Example with the default Meta Data fields.", "ecs": { "version": "1.6.0" }, "environment": "dev" }
The text was updated successfully, but these errors were encountered:
Yes, agreed. Would you mind moving to #68 -- which I believe is the same general issue?
Sorry, something went wrong.
@trentm Moved my comment over there so feel free to close this.
Thanks.
No branches or pull requests
I noticed when I was working with the ECS NodeJS loggers that Metadata fields weren't name spaced.
I can see one of three scenario's:
labels
per [https://www.elastic.co/guide/en/ecs/current/ecs-base.html](Base Fields)tags
per [https://www.elastic.co/guide/en/ecs/current/ecs-base.html](Base Fields)Here's an example configuration:
and a resulting output:
The text was updated successfully, but these errors were encountered: