Correlation Id Token about laabr

[felixheck]

Released as v2.2.3

Thanks for your issue!
BTW: I handled the mergeHapiLogData in this release as well.

[felixheck]

Hey Andrew (@stout01), thanks for your request.

First of all options.hapiPino.mergeHapiLogData does not work currently. It's disabled internally because the token :message needs the data nested in the message property of the logged message. If that's an additionally need, just push another issue or in best case a PR :)

Next: is it possible that I take a look on your project?
I'm really wondering because all those scenarios are captured with unit tests.
Additionally I added temporarily the line laabr.format('response', '>> :cid <<'); to examples/correlator.js:

Works for me.

[stout01]

I created a quick example app where I am still having the issue.

https://github.com/stout01/HapiLoggingExample

[felixheck]

What's your npm/node version? And what's your OS?

[stout01]

Windows 7
node: v8.1.1
npm: v5.3.0

[felixheck]

Installed node v8.1.1 & npm v5.3.0: works on macOS like a charm.
do you work w/ windows?

[stout01]

My work machine is windows 7...

Maybe I'm missing something, but your screen shot only shows the header once. The way I have the format line setup, it should show the x-request-id header twice in the log statement.

[felixheck]

Nope, it shows the correlation id stored in the continuation-local-storage.
The dash in the middle is the request header field x-request-id. This is just truthy if you send a respective header:

But yeah, you are right. There something wrong when using curl.
When using cocoa it works o.O It's necessary to send an additional accept-encoding header with the value/s gzip and/or deflate. Don't know why, gonna investigate.

@stout01 I asked some of the hapi core devs for help...I'm not really familiar with the compression logic in hapi. If there's no reply until tomorrow, I'll publish a hotfix.

[felixheck]

There's a release branch (https://github.com/felixheck/laabr/tree/release/2.2.3) containing the hotfix. would be nice if you could test it again in your environment but it should work :)

I'll release it just after I get the feedback.

[stout01]

Perfect. Its working as expected now. Thanks for being so on top of it!