By type
2022/01/13 03:51:42.532500 beat.go:285: INFO Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs]
2022/01/13 03:51:42.532540 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/01/13 03:51:42.532591 logstash.go:90: INFO Max Retries set to: 3
2022/01/13 03:51:42.532636 outputs.go:108: INFO Activated logstash as output plugin.
2022/01/13 03:51:42.532757 metrics.go:23: INFO Metrics logging every 30s
2022/01/13 03:51:42.532754 publish.go:295: INFO Publisher name: onap-portal-sdk-856bc9b5d4-snk6h
2022/01/13 03:51:42.533150 async.go:63: INFO Flush Interval set to: 1s
2022/01/13 03:51:42.533186 async.go:64: INFO Max Bulk Size set to: 2048
2022/01/13 03:51:42.533996 beat.go:221: INFO filebeat start running.
2022/01/13 03:51:42.534036 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/01/13 03:51:42.911529 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/01/13 03:51:42.911662 registrar.go:123: INFO States Loaded from registrar: 0
2022/01/13 03:51:42.911832 crawler.go:38: INFO Loading Prospectors: 1
2022/01/13 03:51:42.911993 registrar.go:236: INFO Starting Registrar
2022/01/13 03:51:42.912202 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/01/13 03:51:42.912209 sync.go:41: INFO Start sending events to output
2022/01/13 03:51:42.912277 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/01/13 03:51:42.912491 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/01/13 03:51:42.912540 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/01/13 03:51:42.913976 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/01/13 03:51:42.914144 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/01/13 03:51:42.914572 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/01/13 03:51:42.914737 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/01/13 03:51:42.914845 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/01/13 03:51:47.926447 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:51:47.926508 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:51:48.932628 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:51:48.932672 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:51:50.936277 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:51:50.936312 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:51:54.945081 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:51:54.945123 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:52:02.955900 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:52:02.955947 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:52:12.533391 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=5 filebeat.harvester.running=5 filebeat.harvester.started=5 libbeat.publisher.published_events=356 registrar.writes=1
2022/01/13 03:52:18.967537 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:52:18.967586 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:52:42.533250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 03:52:50.980537 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:52:50.980566 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:53:12.533116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 03:53:42.533195 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 03:53:50.991030 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:53:50.991085 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:54:12.533240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 03:54:42.533246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 03:54:50.999976 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:54:51.000027 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:55:12.533320 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 03:55:42.533063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 03:55:51.009264 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:55:51.009295 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:56:12.533118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 03:56:42.533083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 03:56:47.927007 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/01/13 03:56:47.927015 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/01/13 03:56:47.927117 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/01/13 03:56:47.927433 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/01/13 03:56:47.931966 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/01/13 03:56:51.021114 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:56:51.021146 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:57:12.533247 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=5 filebeat.harvester.open_files=-5 filebeat.harvester.running=-5
2022/01/13 03:57:42.533162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 03:57:51.034870 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:57:51.034961 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:58:12.533211 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 03:58:42.533026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 03:58:51.046204 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:58:51.046237 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:59:12.533185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 03:59:42.533191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 03:59:51.056540 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:59:51.056737 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:00:12.533035 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:00:42.533027 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:00:51.066938 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:00:51.066966 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:01:12.533070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:01:42.533021 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:01:51.077445 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:01:51.077485 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:02:12.533186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:02:42.533224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:02:51.086931 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:02:51.086975 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:03:12.533140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:03:42.533056 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:03:51.097090 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:03:51.097180 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:04:12.533206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:04:42.533023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:04:51.104868 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:04:51.104913 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:05:12.533207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:05:42.533021 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:05:51.114368 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:05:51.114418 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:06:12.533126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:06:42.533199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:06:51.123449 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:06:51.123484 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:07:12.533176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:07:42.533071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:07:51.131870 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:07:51.131908 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:08:12.533029 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:08:42.533249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:08:51.140783 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:08:51.140817 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:09:12.533073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:09:42.533081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:09:51.150886 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:09:51.150984 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:10:12.533071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:10:42.533127 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:10:51.161764 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:10:51.161814 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:11:12.533071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:11:42.533149 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:11:51.170695 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:11:51.170727 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:12:12.533230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:12:42.533267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:12:51.180334 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:12:51.180386 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:13:12.533136 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:13:42.533089 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:13:51.189731 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:13:51.189780 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:14:12.533134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:14:42.533133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:14:51.198198 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:14:51.198230 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:15:12.533119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:15:42.533127 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:15:51.208472 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:15:51.208520 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:16:12.533066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:16:42.533435 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:16:51.218382 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:16:51.218431 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:17:12.533043 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:17:42.533076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:17:51.228712 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:17:51.228754 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:18:12.533079 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:18:42.533179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:18:51.237942 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:18:51.237986 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:19:12.533109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:19:42.533055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:19:51.249016 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:19:51.249052 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:20:12.533076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:20:42.533075 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:20:51.259272 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:20:51.259328 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:21:12.533040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:21:42.532984 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:21:51.270620 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:21:51.270701 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:22:12.533185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:22:42.533119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:22:51.279787 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:22:51.279840 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:23:12.533246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:23:42.533170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:23:51.288635 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:23:51.288679 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:24:12.533146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:24:42.533127 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:24:51.298076 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:24:51.298128 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:25:12.533109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:25:42.533041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:25:51.306222 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:25:51.306266 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:26:12.533191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:26:42.533199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:26:51.313642 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:26:51.313676 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:27:12.533129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:27:42.533139 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:27:51.327705 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:27:51.327738 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:28:12.533195 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:28:42.533138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:28:51.335635 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:28:51.335688 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:29:12.533142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:29:42.533118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:29:51.344767 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:29:51.344810 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:30:12.533180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:30:42.533054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:30:51.351639 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:30:51.351668 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:31:12.533068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:31:42.533180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:31:51.360469 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:31:51.360501 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:32:12.533147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:32:42.533100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:32:51.371056 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:32:51.371187 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:33:12.533202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:33:42.533146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:33:51.380858 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:33:51.380892 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:34:12.533048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:34:42.533317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:34:51.389682 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:34:51.389759 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:35:12.533093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:35:42.533200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:35:51.398685 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:35:51.398767 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:36:12.533237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:36:42.533169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:36:51.405231 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:36:51.405278 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:37:12.533314 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:37:42.533186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:37:51.412737 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:37:51.412778 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:38:12.533234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:38:42.533254 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:38:51.420966 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:38:51.420987 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:39:12.533070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:39:42.533042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:39:51.431184 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:39:51.431263 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:40:12.533121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:40:42.533075 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:40:51.438372 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:40:51.438422 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:41:12.533082 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:41:42.533030 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:41:51.447909 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:41:51.447942 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:42:12.533091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:42:42.533008 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:42:51.458247 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:42:51.458289 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:43:12.533323 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:43:42.533032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:43:51.466846 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:43:51.466893 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:44:12.533198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:44:42.533915 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:44:51.475187 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:44:51.475231 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:45:12.533186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:45:42.533145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:45:51.483022 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:45:51.483050 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:46:12.533080 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:46:42.533009 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:46:51.492633 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:46:51.492675 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:47:12.533053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:47:42.533200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:47:51.501611 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:47:51.501659 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:48:12.533199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:48:42.533140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:48:51.511370 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:48:51.511415 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:49:12.533124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:49:42.533052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:49:51.521599 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:49:51.521659 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:50:12.533216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:50:42.533005 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:50:51.533411 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:50:51.533456 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:51:12.533181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:51:42.533051 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:51:51.541417 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:51:51.541484 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:52:12.533293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:52:42.533113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:52:51.549673 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:52:51.549724 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:53:12.533104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:53:42.533108 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:53:51.560766 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:53:51.560826 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:54:12.533418 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:54:42.533049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:54:51.569479 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:54:51.569516 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:55:12.533086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:55:42.533063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:55:51.588572 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:55:51.588603 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:56:12.533449 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:56:42.533170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:56:51.596764 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:56:51.596825 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:57:12.533062 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:57:42.532999 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:57:51.649826 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:57:51.649869 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:58:12.533054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:58:42.533102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:58:51.660067 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:58:51.660109 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:59:12.533171 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:59:42.532983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:59:51.670613 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:59:51.670692 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:00:12.533064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:00:42.533069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:00:51.680532 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:00:51.680554 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:01:12.533202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:01:42.533142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:01:51.690359 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:01:51.690414 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:02:12.533312 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:02:42.533251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:02:51.700812 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:02:51.700858 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:03:12.533086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:03:42.533219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:03:51.709660 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:03:51.709704 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:04:12.533273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:04:42.533083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:04:51.717900 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:04:51.717948 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:05:12.533111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:05:42.533112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:05:51.727314 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:05:51.727341 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:06:12.533182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:06:42.533107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:06:51.739082 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:06:51.739142 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:07:12.533119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:07:42.533317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:07:51.748050 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:07:51.748107 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:08:12.533226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:08:42.533155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:08:51.757075 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:08:51.757124 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:09:12.533135 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:09:42.533079 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:09:51.765973 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:09:51.766028 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:10:12.533031 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:10:42.533181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:10:51.775846 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:10:51.775902 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:11:12.533072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:11:42.533174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:11:51.784673 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:11:51.784706 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:12:12.533170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:12:42.533168 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:12:51.793901 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:12:51.793945 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:13:12.533192 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:13:42.533010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:13:51.803471 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:13:51.803503 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:14:12.533056 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:14:42.533157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:14:51.812926 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:14:51.812962 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:15:12.533046 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:15:42.533108 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:15:51.823505 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:15:51.823549 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:16:12.533186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:16:42.533162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:16:51.833838 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:16:51.833885 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:17:12.533228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:17:42.533198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:17:51.843853 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:17:51.843897 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:18:12.533109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:18:42.533138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:18:51.854326 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:18:51.854476 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:19:12.533013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:19:42.533144 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:19:51.865902 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:19:51.865940 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:20:12.533195 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:20:42.533112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:20:51.875264 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:20:51.875291 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:21:12.533113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:21:42.533121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:21:51.884124 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:21:51.884167 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:22:12.533085 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:22:42.533145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:22:51.893724 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:22:51.893783 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:23:12.533172 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:23:42.533222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:23:51.904580 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:23:51.904628 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:24:12.533134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:24:42.533103 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:24:51.914574 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:24:51.914722 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:25:12.533104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:25:42.533162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:25:51.922369 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:25:51.922420 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:26:12.533081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:26:42.533055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:26:51.929796 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:26:51.929844 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:27:12.533222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:27:42.533208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:27:51.937533 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:27:51.937584 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:28:12.533067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:28:42.533097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:28:51.947188 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:28:51.947256 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:29:12.533160 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:29:42.532965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:29:51.956340 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:29:51.956386 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:30:12.533270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:30:42.533111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:30:51.962947 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:30:51.962975 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:31:12.533336 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:31:42.533142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:31:51.973180 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:31:51.973249 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:32:12.533026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:32:42.533174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:32:51.989651 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:32:51.989686 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:33:12.533119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:33:42.533107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:33:52.000669 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:33:52.000713 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:34:12.533114 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:34:42.533134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:34:52.009887 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:34:52.009933 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:35:12.533062 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:35:42.533034 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:35:52.019612 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:35:52.019677 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:36:12.533120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:36:42.533137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:36:52.029944 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:36:52.030011 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:37:12.533071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:37:42.533027 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:37:52.039918 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:37:52.039967 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:38:12.533156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:38:42.533142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:38:52.049608 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:38:52.049639 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:39:12.533207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:39:42.533146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:39:52.060136 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:39:52.060174 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:40:12.533097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:40:42.533136 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:40:52.069891 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:40:52.069930 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:41:12.533112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:41:42.533092 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:41:52.082971 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:41:52.083036 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:42:12.533212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:42:42.533145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:42:52.092480 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:42:52.092509 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:43:12.533216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:43:42.533429 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:43:52.103186 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:43:52.103363 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:44:12.533176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:44:42.533137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:44:52.112818 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:44:52.112877 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:45:12.533162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:45:42.533174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:45:52.121935 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:45:52.121996 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:46:12.533197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:46:42.533288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:46:52.133905 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:46:52.133978 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:47:12.533119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:47:42.533109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:47:52.143137 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:47:52.143212 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:48:12.533257 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:48:42.533205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:48:52.153593 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:48:52.153653 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:49:12.533216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:49:42.532990 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:49:52.160968 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:49:52.161003 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:50:12.533100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:50:42.533042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:50:52.169798 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:50:52.169841 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:51:12.532993 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:51:42.533149 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:51:52.179444 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:51:52.179496 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:52:12.533174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:52:42.533196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:52:52.188732 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:52:52.188781 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:53:12.533264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:53:42.533217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:53:52.198360 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:53:52.198452 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:54:12.533247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:54:42.533109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:54:52.206116 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:54:52.206149 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:55:12.533431 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:55:42.533114 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:55:52.217422 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:55:52.217467 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:56:12.533413 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:56:42.533104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:56:52.225988 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:56:52.226038 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:57:12.533408 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:57:42.533135 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:57:52.236218 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:57:52.236243 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:58:12.533293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:58:42.533171 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:58:52.245447 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:58:52.245507 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:59:12.533030 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:59:42.533066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:59:52.254497 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:59:52.254534 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:00:12.533088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:00:42.533037 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:00:52.266030 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:00:52.266078 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:01:12.533013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:01:42.533109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:01:52.275419 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:01:52.275482 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:02:12.533127 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:02:42.533147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:02:52.284919 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:02:52.284961 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:03:12.533134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:03:42.533009 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:03:52.294504 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:03:52.294554 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:04:12.533208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:04:42.533331 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:04:52.304471 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:04:52.304528 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:05:12.533342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:05:42.533297 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:05:52.313295 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:05:52.313382 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:06:12.533229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:06:42.533154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:06:52.322441 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:06:52.322542 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:07:12.533061 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:07:42.533114 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:07:52.332916 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:07:52.332963 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:08:12.533077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:08:42.533048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:08:52.341192 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:08:52.341440 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:09:12.533099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:09:42.533038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:09:52.351450 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:09:52.351497 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:10:12.533094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:10:42.533267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:10:52.368960 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:10:52.369021 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:11:12.533072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:11:42.533169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:11:52.385945 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:11:52.385976 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:12:12.533191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:12:42.533041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:12:52.393892 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:12:52.393918 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:13:12.533110 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:13:42.533173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:13:52.401782 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:13:52.401808 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:14:12.533207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:14:42.533154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:14:52.410226 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:14:52.410272 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:15:12.533100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:15:42.533071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:15:52.416803 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:15:52.416856 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:16:12.533154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:16:42.533213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:16:52.424288 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:16:52.424328 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:17:12.533242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:17:42.533129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:17:52.431873 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:17:52.431896 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:18:12.533243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:18:42.533098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:18:52.439510 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:18:52.439544 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:19:12.533144 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:19:42.533113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:19:52.447996 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:19:52.448038 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:20:12.533108 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:20:42.533112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:20:52.456647 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:20:52.456683 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:21:12.533098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:21:42.533091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:21:52.465742 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:21:52.465802 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:22:12.533196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:22:42.533272 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:22:52.473019 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:22:52.473046 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:23:12.533018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:23:42.533187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:23:52.482319 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:23:52.482369 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:24:12.533242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:24:42.533233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:24:52.491326 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:24:52.491390 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:25:12.533142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:25:42.533251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:25:52.500097 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:25:52.500148 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:26:12.533289 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:26:42.533199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:26:52.507309 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:26:52.507335 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:27:12.533133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:27:42.533055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:27:52.515912 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:27:52.515951 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:28:12.533159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:28:42.533031 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:28:52.524374 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:28:52.524411 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:29:12.533321 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:29:42.533235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:29:52.536107 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:29:52.536152 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:30:12.533182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:30:42.533060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:30:52.544950 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:30:52.544974 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:31:12.533298 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:31:42.533069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:31:52.553441 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:31:52.553489 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:32:12.533160 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:32:42.533046 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:32:52.560173 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:32:52.560205 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:33:12.533049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:33:42.533048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:33:52.568836 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:33:52.568867 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:34:12.533164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:34:42.533242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:34:52.578322 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:34:52.578369 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:35:12.533285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:35:42.533136 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:35:52.588671 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:35:52.588694 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:36:12.533213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:36:42.533123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:36:52.597815 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:36:52.597868 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:37:12.533217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:37:42.533178 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:37:52.605593 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:37:52.605641 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:38:12.533170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:38:42.533138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:38:52.615436 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:38:52.615498 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:39:12.533186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:39:42.533283 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:39:52.624332 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:39:52.624398 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:40:12.533026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:40:42.533121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:40:52.632950 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:40:52.632996 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:41:12.533230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:41:42.533185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:41:52.641675 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:41:52.641719 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:42:12.533116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:42:42.533174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:42:52.649326 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:42:52.649368 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:43:12.533137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:43:42.533101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:43:52.657163 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:43:52.657190 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:44:12.533150 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:44:42.533222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:44:52.663865 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:44:52.663914 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:45:12.533113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:45:42.533195 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:45:52.672405 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:45:52.672437 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:46:12.533206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:46:42.533055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:46:52.681345 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:46:52.681392 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:47:12.533016 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:47:42.533075 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:47:52.688953 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:47:52.688989 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:48:12.533529 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:48:42.533261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:48:52.696284 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:48:52.696309 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:49:12.533049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:49:42.533140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:49:52.705002 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:49:52.705047 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:50:12.533111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:50:42.533210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:50:52.715088 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:50:52.715108 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:51:12.533208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:51:42.533096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:51:52.723708 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:51:52.723745 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:52:12.533258 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:52:42.533040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:52:52.731972 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:52:52.732006 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:53:12.533169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:53:42.533078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:53:52.742142 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:53:52.742173 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:54:12.533015 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:54:42.533010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:54:52.751764 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:54:52.751805 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:55:12.533167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:55:42.533213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:55:52.761846 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:55:52.761896 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:56:12.533274 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:56:42.533096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:56:52.770197 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:56:52.770229 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:57:12.533127 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:57:42.533029 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:57:52.779066 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:57:52.779123 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:58:12.533215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:58:42.533174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:58:52.788852 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:58:52.788894 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:59:12.533276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:59:42.533321 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:59:52.795116 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:59:52.795147 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:00:12.533183 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:00:42.533183 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:00:52.802441 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:00:52.802475 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:01:12.533105 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:01:42.532983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:01:52.811533 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:01:52.811568 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:02:12.533205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:02:42.533016 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:02:52.820682 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:02:52.820710 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:03:12.533054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:03:42.533156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:03:52.827611 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:03:52.827637 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:04:12.533092 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:04:42.533208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:04:52.835206 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:04:52.835252 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:05:12.533034 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:05:42.533134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:05:52.844211 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:05:52.844255 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:06:12.533067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:06:42.533043 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:06:52.852998 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:06:52.853046 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:07:12.533177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:07:42.533146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:07:52.861971 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:07:52.862018 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:08:12.533237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:08:42.533254 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:08:52.874241 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:08:52.874280 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:09:12.533220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:09:42.533092 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:09:52.882510 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:09:52.882546 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:10:12.533135 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:10:42.533133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:10:52.892416 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:10:52.892461 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:11:12.533255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:11:42.533163 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:11:52.903138 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:11:52.903181 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:12:12.533017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:12:42.533180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:12:52.912837 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:12:52.912887 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:13:12.533125 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:13:42.533158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:13:52.921794 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:13:52.921835 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:14:12.533240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:14:42.533171 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:14:52.930739 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:14:52.930763 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:15:12.533177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:15:42.532994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:15:52.943132 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:15:52.943190 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:16:12.533072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:16:42.533213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:16:52.952534 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:16:52.952576 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:17:12.533157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:17:42.533245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:17:52.962776 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:17:52.962837 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:18:12.533179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:18:42.533096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:18:52.973201 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:18:52.973261 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:19:12.533101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:19:42.533136 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:19:52.982367 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:19:52.982420 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:20:12.533139 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:20:42.533165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:20:52.992596 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:20:52.992662 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:21:12.533101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:21:42.533206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:21:53.003459 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:21:53.003495 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:22:12.533245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:22:42.533239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:22:53.012811 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:22:53.012848 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:23:12.533433 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:23:42.533137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:23:53.021548 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:23:53.021609 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:24:12.533126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:24:42.533139 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:24:53.031439 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:24:53.031489 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:25:12.533055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:25:42.533126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:25:53.044783 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:25:53.044938 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:26:12.533195 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:26:42.533059 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:26:53.051990 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:26:53.052101 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:27:12.533088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:27:42.533137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:27:53.060635 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:27:53.060682 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:28:12.533101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:28:42.533449 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:28:53.069403 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:28:53.069460 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:29:12.533268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:29:42.533088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:29:53.076084 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:29:53.076135 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:30:12.533300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:30:42.533030 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:30:53.087493 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:30:53.087535 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:31:12.533266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:31:42.532988 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:31:53.095436 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:31:53.095475 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:32:12.533246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:32:42.533208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:32:53.103768 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:32:53.103826 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:33:12.533177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:33:42.533170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:33:53.112518 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:33:53.112551 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:34:12.533441 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:34:42.533048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:34:53.121022 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:34:53.121064 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:35:12.533106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:35:42.533065 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:35:53.130555 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:35:53.130663 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:36:12.533162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:36:42.533221 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:36:53.139661 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:36:53.139687 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:37:12.533234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:37:42.533077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:37:53.148528 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:37:53.148572 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:38:12.533097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:38:42.533045 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:38:53.155816 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:38:53.155856 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:39:12.533165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:39:42.533244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:39:53.162819 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:39:53.162844 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:40:12.533205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:40:42.532952 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:40:53.171399 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:40:53.171426 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:41:12.533066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:41:42.533143 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:41:53.180092 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:41:53.180137 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:42:12.533221 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:42:42.533276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:42:53.188054 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:42:53.188102 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:43:12.533129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:43:42.533058 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:43:53.238482 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:43:53.238513 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:44:12.533101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:44:42.533067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:44:53.246190 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:44:53.246241 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:45:12.533210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:45:42.533174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:45:53.256070 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:45:53.256114 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:46:12.533301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:46:42.533203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:46:53.263902 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:46:53.263952 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:47:12.533450 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:47:42.533291 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:47:53.271573 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:47:53.271601 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:48:12.533078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:48:42.533068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:48:53.278901 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:48:53.278936 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:49:12.533406 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:49:42.533198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:49:53.286967 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:49:53.287004 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:50:12.533159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:50:42.533170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:50:53.295153 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:50:53.295177 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:51:12.532999 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:51:42.533277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:51:53.303507 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:51:53.303545 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:52:12.533221 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:52:42.533051 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:52:53.311265 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:52:53.311309 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:53:12.533080 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:53:42.533154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:53:53.318341 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:53:53.318369 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:54:12.533284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:54:42.533141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:54:53.324110 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:54:53.324137 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:55:12.533074 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:55:42.533162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:55:53.331879 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:55:53.331925 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:56:12.533123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:56:42.533107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:56:53.344769 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:56:53.344831 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:57:12.533180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:57:42.533118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:57:53.353384 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:57:53.353425 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:58:12.533036 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:58:42.533137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:58:53.362019 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:58:53.362076 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:59:12.533130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:59:42.533056 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:59:53.372280 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:59:53.372315 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:00:12.533099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:00:42.533196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:00:53.382661 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:00:53.382714 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:01:12.533065 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:01:42.533089 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:01:53.392171 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:01:53.392302 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:02:12.533159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:02:42.533073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:02:53.402221 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:02:53.402413 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:03:12.533158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:03:42.533178 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:03:53.410954 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:03:53.410978 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:04:12.533120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:04:42.533118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:04:53.420508 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:04:53.420566 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:05:12.533580 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:05:42.533035 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:05:53.439808 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:05:53.439852 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:06:12.533139 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:06:42.533171 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:06:53.449987 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:06:53.450039 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:07:12.533283 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:07:42.533514 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:07:53.456603 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:07:53.456626 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:08:12.533158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:08:42.533197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:08:53.471829 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:08:53.471859 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:09:12.533007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:09:42.533036 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:09:53.480375 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:09:53.480420 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:10:12.533147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:10:42.533200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:10:53.490385 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:10:53.490430 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:11:12.533209 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:11:42.533064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:11:53.499714 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:11:53.499742 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:12:12.533204 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:12:42.533158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:12:53.508490 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:12:53.508558 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:13:12.533170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:13:42.533320 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:13:53.518824 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:13:53.518877 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:14:12.533279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:14:42.532972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:14:53.530406 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:14:53.530455 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:15:12.533117 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:15:42.533283 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:15:53.540552 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:15:53.540615 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:16:12.533181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:16:42.533132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:16:53.550248 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:16:53.550296 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:17:12.533068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:17:42.533036 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:17:53.560931 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:17:53.560982 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:18:12.533337 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:18:42.533314 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:18:53.570692 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:18:53.570757 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:19:12.533135 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:19:42.533032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:19:53.579757 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:19:53.579803 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:20:12.533121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:20:42.533235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:20:53.588151 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:20:53.588202 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:21:12.533182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:21:42.533083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:21:53.597718 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:21:53.597788 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:22:12.533523 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:22:42.533094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:22:53.604724 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:22:53.604784 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:23:12.533183 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:23:42.533086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:23:53.613305 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:23:53.613391 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:24:12.533150 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:24:42.533181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:24:53.620669 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:24:53.620698 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:25:12.533042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:25:42.533201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:25:53.629560 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:25:53.629603 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:26:12.533243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:26:42.533266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:26:53.635509 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:26:53.635533 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:27:12.533060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:27:42.533229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:27:53.646093 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:27:53.646151 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:28:12.533066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:28:42.533220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:28:53.655788 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:28:53.655815 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:29:12.533200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:29:42.533193 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:29:53.665417 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:29:53.665461 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:30:12.533070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:30:42.533054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:30:53.681619 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:30:53.681669 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:31:12.533113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:31:42.533129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:31:53.691773 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:31:53.691826 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:32:12.533042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:32:42.533172 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:32:53.703201 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:32:53.703238 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:33:12.533203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:33:42.533068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:33:53.711614 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:33:53.711647 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:34:12.533123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:34:42.533255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:34:53.719974 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:34:53.720000 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:35:12.533055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:35:42.533050 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:35:53.728113 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:35:53.728158 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:36:12.533088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:36:42.533189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:36:53.734998 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:36:53.735047 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:37:12.532981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:37:42.533077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:37:53.743967 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:37:53.744014 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:38:12.533138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:38:42.533093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:38:53.752313 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:38:53.752384 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:39:12.533188 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:39:42.533169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:39:53.763331 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:39:53.763513 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:40:12.533239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:40:42.533079 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:40:53.772023 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:40:53.772058 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:41:12.533085 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:41:42.533204 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:41:53.779656 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:41:53.779701 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:42:12.533084 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:42:42.533118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:42:53.790001 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:42:53.790051 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:43:12.533083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:43:42.533081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:43:53.798976 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:43:53.799031 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:44:12.533100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:44:42.533015 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:44:53.808337 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:44:53.808454 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:45:12.533150 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:45:42.533127 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:45:53.818380 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:45:53.818426 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:46:12.533169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:46:42.533094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:46:53.829477 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:46:53.829519 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:47:12.533156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:47:42.533231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:47:53.838641 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:47:53.838679 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:48:12.533305 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:48:42.533069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:48:53.847770 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:48:53.847816 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:49:12.533240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:49:42.533146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:49:53.857475 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:49:53.857530 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:50:12.533243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:50:42.533212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:50:53.867282 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:50:53.867339 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:51:12.533148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:51:42.533118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:51:53.876705 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:51:53.876728 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:52:12.533112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:52:42.533109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:52:53.885783 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:52:53.885827 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:53:12.533133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:53:42.533184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:53:53.895381 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:53:53.895502 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:54:12.533299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:54:42.533169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:54:53.905161 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:54:53.905210 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:55:12.533296 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:55:42.533041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:55:53.915985 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:55:53.916054 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:56:12.533306 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:56:42.533076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:56:53.926931 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:56:53.926974 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:57:12.533035 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:57:42.533240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:57:53.935975 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:57:53.936001 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:58:12.533253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:58:42.533124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:58:53.945787 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:58:53.945837 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:59:12.533119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:59:42.533147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:59:53.955570 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:59:53.955604 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 09:00:12.533130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 09:00:42.533186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 09:00:53.965072 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 09:00:53.965130 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 09:01:12.533247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 09:01:42.533140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 09:01:53.973985 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 09:01:53.974012 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 09:02:12.533021 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 09:02:42.533045 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 09:02:53.983225 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 09:02:53.983275 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 09:03:12.533192 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 09:03:42.533041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 09:03:53.992122 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 09:03:53.992178 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 09:04:12.533128 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 09:04:42.533064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 09:04:54.000788 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 09:04:54.000835 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 09:05:12.533172 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 09:05:42.533126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 09:05:54.008064 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 09:05:54.008088 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 09:06:12.533207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 09:06:42.533098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 09:06:54.017488 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 09:06:54.017550 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 09:07:12.533199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 09:07:42.533052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 09:07:54.027233 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 09:07:54.027267 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 09:08:12.533521 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 09:08:42.533161 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 09:08:54.038083 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 09:08:54.038121 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 09:09:12.533167 metrics.go:34: INFO No non-zero metrics in the last 30s