Pino Redact does not work with Pino HTTP customAttributeKeys.

I currently am using pino-http to map to an ECS format. When doing so though my redactions are not taking place.

redact: {
    paths: ['http.request.headers.authorization'],
    censor: '***REDACTED***',
  },
  customAttributeKeys: {
    req: 'http.request',
  },

[baterson]

@sethtomy Your example doesn’t work because pino assumes that it should redact an object with the given structure:
{ http: { request: { headers: { authorization: "" }}}} But in your case it’s:
{ "http.request": { headers: { authorization: "" }}}

So to make it work, you just need to rewrite the path or use a key without dots in name:

redact: {
    paths: ['["http.request"].headers.authorization'],
    censor: '***REDACTED***',
},
customAttributeKeys: {
    req: 'http.request',
},

[sethtomy]

@RohitRox thank you for responding. Unfortunately that does not seem to work in combination with “customAttributeKeys”.

@baterson that works perfectly! If you don’t mind, for my curiosity, I’m interested in how that’s working. A took ~ an hour to look into the issue myself but Streams unfortunately are not my strong suit (I need to learn 😃) How is the dot notation for ‘http.request.headers.authorization’ structurally different from ‘[“http.request”].headers.authorization’. Is there something special around that first “http.request” key?