Structured logging hides contents of interface objects

[uablrek]

Describe the bug

Some (quite many) go objects in Meridio are really interfaces. When used for output in structured logging the contents is empty {}. Example;

Meridio/pkg/loadbalancer/stream/loadbalancer.go

Line 190 in c19b1d2

lb.logger.Info("AddTarget", "target", target)

To Reproduce

Check the load-balancer logs:

# kubectl logs -n red -c stateless-lb meridio-load-balancer-7549d49c9f-f28xz | jq
...
{
  "severity": "info",
  "timestamp": "2023-02-06T09:29:37.965+00:00",
  "service_id": "Meridio-LB",
  "message": "AddTarget",
  "version": "1.0.0",
  "extra_data": {
    "class": "LoadBalancer",
    "instance": "stream1",
    "target": {}
  }
}

Expected behavior

Useful logging

[uablrek]

Interface classes may be needed, but they should not be over-used since they basically trashes structured logging.

An overhaul is needed to log specific getters in interface objects rather than the objects themselves. This goes somewhat against the idea of structured logging.