Re: Allow gorouter to log random headers.
Simon Johansson <simon@...>
WAKAWAKA is just an exampletoggle quoted message Show quoted text
But the difference is that WAKAWAKA is not platform specific whereas
X-Cf-Requestid is. If we want to move our app to Heroku, or a VM, or
whatewher we have platform specific implementation details in our
app(namely we rely on a header that is not there anymore). But that is not
the point of this thread.
The point is,
say we have an app that is fronted by a CDN, and the CDN sets the
X-Im-a-shark header with some value that we are interested to see in our
logs. The easiest way to achivie this without having to implement it into
our own apps is just to tell the Gorouter that it should append the value
of that header into the string that it logs so the event that flow via
Doppler and ultimately into cf logs/ELK will contain that value.
The reason why this would be such a valuable feature for us is that we dont
have to do anything. CF already provide the out of the box facility to give
us routing logs, so if we can piggy back on that for what we are interested
in we dont have to add libraries to our apps to log interesting headers on
On Wed, Jul 22, 2015 at 12:45 AM, Shannon Coen <scoen(a)pivotal.io> wrote:
I don't see the difference between WAKAWAKA and X-Cf-Requestid. Gorouter