Open alkalinecoffee opened 4 years ago
Do we just have to add the new params here?
( I am completely new here and if you know of another c++ project that would be easier for me to start with, I would go there before trying to contribute here)
The code to edit is in here: https://github.com/envoyproxy/envoy/blob/master/source/common/formatter/substitution_formatter.h. And related users.
Hi @yozaam! Have you already started to work on this? I also got an interest in this feature request, so if you haven't, I would like to take it. (never mind if you have:+1:)
Hi @yozaam! Have you already started to work on this? I also got an interest in this feature request, so if you haven't, I would like to take it. (never mind if you have👍)
Hey @musaprg go ahead :D
/assign @Shikugawa
Adding a request to support environment variables in our log formatting, perhaps using the
ENV
key (similar toREQ
,RESP
, etc).HOSTNAME
is an already supported keyword pulled from the environment--this feature would expand on that.Some values are known ahead of time and can be baked into the log format. However, the use case would be for logging runtime values (host IP, AZ, etc) that are only known when the container is deployed. Our current solution is to parse the config file, injecting selected envvars, etc before booting the service.