kirrg001

Furthermore. Look at https://github.com/TryGhost/Ghost/blob/1.22.5/core/server/config/index.js. And see whatelse needs to be defined in Ignition. Background. Ghost has added `nconf` before it was using Ghost-Ignition.

@sebgie has suggested to not generate a new request id if a specific header already exists. Example: `x-request-id` https://devcenter.heroku.com/articles/http-request-id http://stackoverflow.com/questions/25433258/what-is-the-x-request-id-http-header By this we can track a request through multiple stages.

Request ID header was directly added in Ghost for now (see https://github.com/TryGhost/Ghost/pull/9122). We can port this change over to here as soon as we source out the logging middleware.

FYI: Ignition doesn't do anything with database connections yet. Ignition is a centralised, generic tool for multiple repositories. Do you know where these endpoints would be used? e.g. a metric...

bunyan-loggly uses `request` as dependency...that's why the memory consumption is high.

Thanks @frantzypants! > I’m not sure what the best solution is, or if it’s worth changing, but for me personally I’d prefer to see each file that needs to be...

Thanks @frantzypants! Yeah agree, GScan shouldn't detect commented out code or show a warning instead.

> As far as I know, the only reason we're seeing this happen is because the output from gscan about changing instances of image tell them to do a straight...

Thanks for the investigation. We are also running into this problem. [This](586cd0a33fd9d7823edc0ba12fe2be73d8772651) has helped us as a workaround. Thank you so much!

Might be the same experience: https://github.com/Blizzard/node-rdkafka/issues/1128