Page MenuHomePhabricator

API Gateway needs a dual logging solution
Open, Needs TriagePublic

Description

As a result of fixing T295717, the API Gateway currently ships no useful logs. This isn't a huge change given that the logs we previously shipped to logstash were uselessly verbose and split across multiple lines. We need to replicate the JSON formatted logs that we currently send to eventgate on stdout. This could be by

  • implementing a second access_log entry in config if this is permitted
  • by relaying the log info we currently stream to stdout while shipping it
  • if it is no longer needed, removing the shipping of logs to eventgate - is this functionality still a requirement? I am not certain as to whether this feature is still a priority or if anyone uses it (@Pchelolo might have more insight on this)

Event Timeline

I don't think access logging in logstash would be very useful. It would be useful to send regular envoy logs to logstash, but filter on error level.

if it is no longer needed, removing the shipping of logs to eventgate - is this functionality still a requirement? I am not certain as to whether this feature is still a priority or if anyone uses it (@Pchelolo might have more insight on this)

I don't know if anyone uses it right now, but it's one of the features that brings the gateway on par with action API. Once the gateway is used more I think this feature would get more importance.