glog considered bad practice - rip it out and use something more standard

[Godley]

reasons from twitter

Using glog on operator - we should move toward something better, and more generally, make sure we're now using one, good logging library across all components (whatever gateway is using is probably right?)

[rusenask]

Gateway is using logrus https://github.com/sirupsen/logrus which is quite easy to use and is very flexible (we can later on add some hooks, like errors to sentry if we want to).

Another good option is https://github.com/uber-go/zap. I use zap too, but it's a bit more hassle and you basically have to pass it through the structs which is fine. But it is a hassle: )

Pros of logrus:

• Easy to use, just import and do log.WithFields, or log.Error

Pros of zap:

• Very few allocations. I guess it makes most sense to use it in high load systems such as load balancers or something similar. I don't believe we will ever have enough load to worry about allocations though.