wazigate-edge: too much logs

[cdupont]

wazigate-edge is emitting logs every seconds, so it's difficult to exploit it.
Example of log:

2020-12-04T14:16:26.029309859Z [HTTP ] 10.42.0.1:55284 200 GET "/apps/waziup.wazigate-system/internet" s:0
2020-12-04T14:16:26.727783364Z [APP  ] >> "waziup.wazigate-system" GET /docker/f8c6e3a59cf65a470066b15acacb64ec4a0300c708b51e575eba3cd56f578ca7/logs/50
2020-12-04T14:16:26.988601641Z [APP  ] << 200 200 OK (5809 B)
2020-12-04T14:16:26.988691986Z [HTTP ] 10.42.0.1:55284 200 GET "/apps/waziup.wazigate-system/docker/f8c6e3a59cf65a470066b15acacb64ec4a0300c708b51e575eba3cd56f578ca7/logs/50" s:0
2020-12-04T14:16:27.995793799Z [UP   ] (  0) Can not connect to server.
2020-12-04T14:16:27.995916215Z Post https://api.waziup.io/api/v2/auth/token: dial tcp: lookup api.waziup.io on 127.0.0.11:53: read udp 127.0.0.1:49902->127.0.0.11:53: i/o timeout
2020-12-04T14:16:28.727752412Z [APP  ] >> "waziup.wazigate-system" GET /docker/f8c6e3a59cf65a470066b15acacb64ec4a0300c708b51e575eba3cd56f578ca7/logs/50
2020-12-04T14:16:28.953639748Z [HTTP ] 10.42.0.1:55290 200 GET "/sys/uptime" s:0
2020-12-04T14:16:29.002021654Z [APP  ] << 200 200 OK (5809 B)
2020-12-04T14:16:29.002102740Z [HTTP ] 10.42.0.1:55284 200 GET "/apps/waziup.wazigate-system/docker/f8c6e3a59cf65a470066b15acacb64ec4a0300c708b51e575eba3cd56f578ca7/logs/50" s:0
2020-12-04T14:16:30.729709555Z [APP  ] >> "waziup.wazigate-system" GET /docker/f8c6e3a59cf65a470066b15acacb64ec4a0300c708b51e575eba3cd56f578ca7/logs/50
2020-12-04T14:16:30.975816046Z [APP  ] << 200 200 OK (5809 B)
2020-12-04T14:16:30.975907353Z [HTTP ] 10.42.0.1:55284 200 GET "/apps/waziup.wazigate-system/docker/f8c6e3a59cf65a470066b15acacb64ec4a0300c708b51e575eba3cd56f578ca7/logs/50" s:0
2020-12-04T14:16:30.995612453Z [MQTT ] "chirpstack-application-s" Message "gateway/0000000000000000/event/up" s:100 r:false q:0
2020-12-04T14:16:32.687744712Z [WWW  ] (127.0.0.1:42990) 200 GET "/"
2020-12-04T14:16:32.731683135Z [APP  ] >> "waziup.wazigate-system" GET /docker/f8c6e3a59cf65a470066b15acacb64ec4a0300c708b51e575eba3cd56f578ca7/logs/50
2020-12-04T14:16:32.876024849Z [HTTP ] 172.18.0.1:36912 200 GET "/sys/uptime" s:0
2020-12-04T14:16:32.957811050Z [APP  ] << 200 200 OK (5809 B)
2020-12-04T14:16:32.957893858Z [HTTP ] 10.42.0.1:55284 200 GET "/apps/waziup.wazigate-system/docker/f8c6e3a59cf65a470066b15acacb64ec4a0300c708b51e575eba3cd56f578ca7/logs/50" s:0
2020-12-04T14:16:34.731219350Z [APP  ] >> "waziup.wazigate-system" GET /docker/f8c6e3a59cf65a470066b15acacb64ec4a0300c708b51e575eba3cd56f578ca7/logs/50
2020-12-04T14:16:34.967335025Z [APP  ] << 200 200 OK (5809 B)
2020-12-04T14:16:34.967570339Z [HTTP ] 10.42.0.1:55284 200 GET "/apps/waziup.wazigate-system/docker/f8c6e3a59cf65a470066b15acacb64ec4a0300c708b51e575eba3cd56f578ca7/logs/50" s:0

It is actually polluted by requests made by the log window itself (GET docker/xxx/logs/50)