Matteo Collina

I think we should extend `formatters.bindings` so that it forward `this` to the current logger. https://github.com/pinojs/pino/blob/185dc159166d8d31471a31532fede220d5a8d588/lib/tools.js#L157 Could you send a PR?

I think you could do something like: ```js const pino = require('pino')() exports.handler = function(event, context, callback) { console.log('remaining time =', context.getRemainingTimeInMillis()); console.log('functionName =', context.functionName); console.log('AWSrequestID =', context.awsRequestId); const logger...

> @mcollina Can you explain why the snippet would work? It's not super obvious to me. `pino.child()` is going to add a property `awsRequestId` to your newline delimited JSON lines....

I’m +1. However we need a bit more API parity between the two. Il giorno sab 14 set 2019 alle 21:02 James Sumners ha scritto: > I'm not opposed. >...

@delvedor given this is really about ElasticSearch and ECS, could you please check this out?

I tried ```bash node bug.js > out.json jq . < out.json ``` and it does not exhibit the problem. However, it looks like `node bug.js | cat - | jq...

What do you mean? It's totally possible that a char is lost somewhere in the process. I find it weird that it works through different destinations. Would you like to...

I'm with @jsumners

@YouriT https://github.com/pinojs/pino/pull/896 should solve this.

the msg text should be fixed to ease processing/searching. Add those as a property. log.info({ hello: “world” }, “some log line”) I don’t recall if we did this for some...