Results

          2022/03/04 03:10:49.227576 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/03/04 03:10:49.227646 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/04 03:10:49.227726 logstash.go:90: INFO Max Retries set to: 3
2022/03/04 03:10:49.227807 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/04 03:10:49.227819 metrics.go:23: INFO Metrics logging every 30s
2022/03/04 03:10:49.227926 publish.go:295: INFO Publisher name: onap-portal-sdk-856bc9b5d4-fn7wh
2022/03/04 03:10:49.228085 async.go:63: INFO Flush Interval set to: 1s
2022/03/04 03:10:49.228099 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/04 03:10:49.228576 beat.go:221: INFO filebeat start running.
2022/03/04 03:10:49.228672 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/04 03:10:49.406213 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/04 03:10:49.406318 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/04 03:10:49.406425 registrar.go:236: INFO Starting Registrar
2022/03/04 03:10:49.406518 crawler.go:38: INFO Loading Prospectors: 1
2022/03/04 03:10:49.406609 sync.go:41: INFO Start sending events to output
2022/03/04 03:10:49.406714 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/04 03:10:49.406834 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/04 03:10:49.406933 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/04 03:10:49.406959 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/04 03:11:19.228198 metrics.go:39: INFO Non-zero metrics in the last 30s: registrar.writes=1
2022/03/04 03:11:29.409869 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/04 03:11:29.410208 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/04 03:11:29.410732 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/04 03:11:29.411269 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/04 03:11:29.411480 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/04 03:11:34.765250 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:11:34.765304 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:11:35.769916 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:11:35.769949 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:11:37.774665 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:11:37.774714 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:11:41.790020 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:11:41.790059 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:11:49.228255 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=54
2022/03/04 03:11:49.798578 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:11:49.798616 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:12:05.825894 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:12:05.825930 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:12:19.228233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:12:37.836911 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:12:37.836966 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:12:49.228232 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:13:19.228142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:13:37.846411 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:13:37.846479 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:13:49.228241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:14:19.228346 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:14:37.854399 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:14:37.854444 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:14:49.228197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:15:19.228127 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:15:37.862851 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:15:37.862888 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:15:49.228217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:16:19.228277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:16:34.425122 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/04 03:16:37.872338 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:16:37.872364 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:16:49.228207 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/04 03:16:59.425801 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/04 03:16:59.425808 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/04 03:16:59.425813 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/04 03:17:19.228243 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-3
2022/03/04 03:17:37.881480 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:17:37.881523 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:17:49.228164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:18:19.228246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:18:37.891315 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:18:37.891348 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:18:49.228230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:19:19.228324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:19:37.902905 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:19:37.902949 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:19:49.228160 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:20:19.228317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:20:37.912386 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:20:37.912440 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:20:49.228204 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:21:19.228278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:21:37.921729 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:21:37.921753 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:21:49.232069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:22:19.228130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:22:37.932054 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:22:37.932098 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:22:49.228127 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:23:19.228223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:23:37.941418 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:23:37.941450 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:23:49.228216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:24:19.228301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:24:37.951174 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:24:37.951214 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:24:49.228241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:25:19.228135 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:25:37.961473 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:25:37.961529 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:25:49.228437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:26:19.228265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:26:37.970317 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:26:37.970362 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:26:49.228122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:27:19.228109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:27:37.979060 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:27:37.979089 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:27:49.228259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:28:19.228296 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:28:37.988228 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:28:37.988272 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:28:49.228103 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:29:19.228226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:29:37.997766 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:29:37.997814 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:29:49.228226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:30:19.228286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:30:38.007213 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:30:38.007251 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:30:49.228073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:31:19.228253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:31:38.049741 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:31:38.049814 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:31:49.228165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:32:19.228309 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:32:38.059879 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:32:38.059929 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:32:49.228241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:33:19.228217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:33:38.070321 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:33:38.070354 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:33:49.228163 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:34:19.228155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:34:38.079180 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:34:38.079232 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:34:49.228185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:35:19.228301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:35:38.088704 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:35:38.088743 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:35:49.228256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:36:19.228185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:36:38.099236 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:36:38.099273 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:36:49.228197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:37:19.228237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:37:38.109505 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:37:38.109537 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:37:49.228316 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:38:19.228327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:38:38.120414 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:38:38.120568 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:38:49.228128 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:39:19.228181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:39:38.130047 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:39:38.130095 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:39:49.228190 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:40:19.228389 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:40:38.140058 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:40:38.140093 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:40:49.228236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:41:19.228111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:41:38.150639 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:41:38.150782 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:41:49.228194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:42:19.228220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:42:38.160684 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:42:38.160742 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:42:49.228168 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:43:19.228213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:43:38.172585 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:43:38.172758 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:43:49.228306 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:44:19.228370 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:44:38.182791 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:44:38.182831 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:44:49.228179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:45:19.228130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:45:38.192415 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:45:38.192463 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:45:49.228322 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:46:19.228302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:46:38.202800 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:46:38.202847 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:46:49.228243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:47:19.228355 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:47:38.213488 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:47:38.213551 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:47:49.228319 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:48:19.228205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:48:38.222789 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:48:38.222856 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:48:49.228303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:49:19.228232 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:49:38.233505 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:49:38.233556 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:49:49.228365 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:50:19.228259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:50:38.245279 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:50:38.245312 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:50:49.228216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:51:19.228231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:51:38.252929 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:51:38.252967 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:51:49.228094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:52:19.228277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:52:38.262197 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:52:38.262253 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:52:49.228227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:53:19.228189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:53:38.270849 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:53:38.270968 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:53:49.228249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:54:19.228251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:54:38.277779 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:54:38.277819 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:54:49.228265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:55:19.228409 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:55:38.285067 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:55:38.285106 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:55:49.228269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:56:19.228259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:56:38.293246 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:56:38.293301 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:56:49.228356 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:57:19.228194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:57:38.300896 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:57:38.300945 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:57:49.228304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:58:19.228244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:58:38.309849 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:58:38.309998 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:58:49.228375 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:59:19.228180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:59:38.317980 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:59:38.318130 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:59:49.228275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:00:19.228257 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:00:38.326035 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:00:38.326312 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:00:49.228316 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:01:19.228216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:01:38.333929 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:01:38.333962 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:01:49.228271 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:02:19.228545 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:02:38.341744 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:02:38.341793 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:02:49.228146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:03:19.229981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:03:38.350262 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:03:38.350314 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:03:49.228179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:04:19.228294 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:04:38.358908 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:04:38.358955 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:04:49.228245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:05:19.228284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:05:38.367219 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:05:38.367290 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:05:49.228249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:06:19.228270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:06:38.373633 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:06:38.373658 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:06:49.228194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:07:19.228200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:07:38.381872 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:07:38.381908 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:07:49.228237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:08:19.228355 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:08:38.388802 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:08:38.388869 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:08:49.228154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:09:19.228200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:09:38.397183 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:09:38.397219 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:09:49.228461 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:10:19.228156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:10:38.405970 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:10:38.406055 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:10:49.228280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:11:19.228273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:11:38.413520 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:11:38.413549 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:11:49.228300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:12:19.228251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:12:38.421776 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:12:38.421820 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:12:49.228324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:13:19.228335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:13:38.429759 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:13:38.429823 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:13:49.228235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:14:19.228307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:14:38.437775 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:14:38.437819 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:14:49.228398 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:15:19.228188 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:15:38.445804 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:15:38.445848 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:15:49.228263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:16:19.228243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:16:38.455025 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:16:38.455070 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:16:49.228300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:17:19.228310 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:17:38.463384 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:17:38.463432 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:17:49.228366 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:18:19.228207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:18:38.470101 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:18:38.470139 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:18:49.228385 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:19:19.228320 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:19:38.477658 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:19:38.477712 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:19:49.228209 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:20:19.228277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:20:38.486578 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:20:38.486620 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:20:49.228299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:21:19.228243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:21:38.494549 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:21:38.494589 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:21:49.228137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:22:19.228322 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:22:38.502254 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:22:38.502286 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:22:49.228190 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:23:19.228187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:23:38.510590 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:23:38.510631 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:23:49.228231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:24:19.228292 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:24:38.518538 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:24:38.518582 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:24:49.228122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:25:19.228329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:25:38.526179 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:25:38.526218 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:25:49.228177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:26:19.228317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:26:38.533128 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:26:38.533171 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:26:49.228400 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:27:19.228276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:27:38.540555 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:27:38.540605 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:27:49.228276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:28:19.228334 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:28:38.548686 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:28:38.548726 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:28:49.228267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:29:19.228211 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:29:38.556569 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:29:38.556623 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:29:49.228317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:30:19.228250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:30:38.563090 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:30:38.563120 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:30:49.228407 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:31:19.228360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:31:38.571594 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:31:38.571647 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:31:49.228314 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:32:19.228380 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:32:38.580798 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:32:38.580851 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:32:49.228322 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:33:19.228247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:33:38.589431 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:33:38.589485 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:33:49.228310 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:34:19.228538 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:34:38.599096 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:34:38.599138 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:34:49.228280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:35:19.228267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:35:38.607379 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:35:38.607443 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:35:49.228183 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:36:19.228206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:36:38.615705 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:36:38.615756 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:36:49.228271 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:37:19.228129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:37:38.621766 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:37:38.621795 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:37:49.228251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:38:19.228186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:38:38.630556 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:38:38.630595 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:38:49.228187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:39:19.228273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:39:38.639317 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:39:38.639376 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:39:49.228265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:40:19.228145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:40:38.647297 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:40:38.647338 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:40:49.228184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:41:19.228173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:41:38.654158 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:41:38.654202 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:41:49.228349 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:42:19.228257 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:42:38.662193 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:42:38.662418 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:42:49.228254 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:43:19.228142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:43:38.670376 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:43:38.670430 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:43:49.228174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:44:19.228265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:44:38.678318 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:44:38.678370 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:44:49.228199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:45:19.228143 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:45:38.685130 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:45:38.685177 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:45:49.228200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:46:19.228315 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:46:38.692218 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:46:38.692262 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:46:49.228158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:47:19.228131 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:47:38.700716 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:47:38.700771 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:47:49.228233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:48:19.228122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:48:38.708830 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:48:38.708879 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:48:49.228237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:49:19.228225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:49:38.716276 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:49:38.716343 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:49:49.228116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:50:19.228211 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:50:38.723893 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:50:38.723924 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:50:49.228299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:51:19.228235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:51:38.730532 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:51:38.730577 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:51:49.228265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:52:19.228241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:52:38.738394 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:52:38.738444 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:52:49.228291 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:53:19.228156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:53:38.745939 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:53:38.745966 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:53:49.228318 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:54:19.228272 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:54:38.753301 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:54:38.753342 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:54:49.228175 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:55:19.228227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:55:38.761775 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:55:38.761842 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:55:49.228227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:56:19.228213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:56:38.768880 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:56:38.768942 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:56:49.228243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:57:19.228161 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:57:38.777474 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:57:38.777538 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:57:49.228175 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:58:19.228321 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:58:38.785093 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:58:38.785131 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:58:49.228130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:59:19.228172 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:59:38.793896 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:59:38.793931 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:59:49.228215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:00:19.228254 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:00:38.802949 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:00:38.803012 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:00:49.228147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:01:19.228276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:01:38.811870 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:01:38.811912 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:01:49.228356 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:02:19.228308 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:02:38.819028 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:02:38.819062 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:02:49.228305 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:03:19.228176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:03:38.826873 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:03:38.826940 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:03:49.228253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:04:19.228166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:04:38.834318 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:04:38.834354 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:04:49.228263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:05:19.228191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:05:38.841674 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:05:38.841710 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:05:49.228202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:06:19.228299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:06:38.849308 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:06:38.849350 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:06:49.228176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:07:19.228190 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:07:38.856963 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:07:38.857027 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:07:49.228390 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:08:19.228307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:08:38.864389 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:08:38.864434 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:08:49.228158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:09:19.228261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:09:38.871834 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:09:38.871885 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:09:49.228148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:10:19.228276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:10:38.879680 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:10:38.879729 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:10:49.228245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:11:19.228202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:11:38.887347 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:11:38.887403 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:11:49.228220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:12:19.228211 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:12:38.895402 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:12:38.895447 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:12:49.228197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:13:19.228224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:13:38.904075 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:13:38.904118 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:13:49.228245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:14:19.228247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:14:39.155222 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:14:39.155276 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:14:49.228319 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:15:19.228265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:15:39.163075 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:15:39.163122 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:15:49.228312 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:16:19.228253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:16:39.171137 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:16:39.171192 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:16:49.228276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:17:19.228225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:17:39.179365 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:17:39.179405 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:17:49.228454 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:18:19.228218 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:18:39.187496 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:18:39.187548 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:18:49.228252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:19:19.228226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:19:39.196163 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:19:39.196212 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:19:49.228209 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:20:19.228347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:20:39.202908 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:20:39.202945 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:20:49.228229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:21:19.228329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:21:39.212036 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:21:39.212063 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:21:49.228246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:22:19.228238 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:22:39.220897 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:22:39.220933 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:22:49.228224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:23:19.228114 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:23:39.228988 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:23:39.229041 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:23:49.228168 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:24:19.228313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:24:39.236520 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:24:39.236576 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:24:49.228309 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:25:19.228217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:25:39.245890 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:25:39.245943 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:25:49.228234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:26:19.228313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:26:39.255544 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:26:39.255607 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:26:49.228241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:27:19.228187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:27:39.262581 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:27:39.262621 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:27:49.228262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:28:19.228220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:28:39.269971 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:28:39.270009 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:28:49.228304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:29:19.228266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:29:39.277699 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:29:39.277725 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:29:49.228206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:30:19.228339 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:30:39.284767 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:30:39.284836 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:30:49.228243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:31:19.228348 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:31:39.291769 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:31:39.291805 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:31:49.228263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:32:19.228216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:32:39.299763 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:32:39.299814 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:32:49.228134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:33:19.228202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:33:39.306443 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:33:39.306479 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:33:49.228320 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:34:19.228347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:34:39.314045 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:34:39.314083 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:34:49.228257 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:35:19.228228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:35:39.321976 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:35:39.322024 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:35:49.228336 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:36:19.228298 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:36:39.328943 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:36:39.328981 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:36:49.228242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:37:19.228170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:37:39.340802 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:37:39.340839 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:37:49.228142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:38:19.228245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:38:39.348677 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:38:39.348720 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:38:49.228293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:39:19.228217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:39:39.355514 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:39:39.355544 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:39:49.228294 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:40:19.228289 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:40:39.363931 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:40:39.363967 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:40:49.228353 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:41:19.228114 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:41:39.373140 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:41:39.373193 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:41:49.228272 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:42:19.228333 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:42:39.382018 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:42:39.382059 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:42:49.228305 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:43:19.228470 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:43:39.390891 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:43:39.390941 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:43:49.228301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:44:19.228338 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:44:39.398638 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:44:39.398675 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:44:49.228114 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:45:19.228154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:45:39.406666 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:45:39.406729 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:45:49.228391 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:46:19.228305 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:46:39.414776 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:46:39.414916 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:46:49.228218 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:47:19.228206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:47:39.422887 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:47:39.422926 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:47:49.228219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:48:19.228318 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:48:39.430219 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:48:39.430269 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:48:49.228203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:49:19.228221 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:49:39.436847 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:49:39.436900 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:49:49.228138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:50:19.228239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:50:39.446001 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:50:39.446036 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:50:49.228200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:51:19.228294 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:51:39.454713 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:51:39.454761 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:51:49.228238 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:52:19.228227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:52:39.462501 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:52:39.462542 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:52:49.228267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:53:19.228243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:53:39.469928 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:53:39.469957 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:53:49.228174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:54:19.228176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:54:39.477727 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:54:39.477841 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:54:49.228276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:55:19.228077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:55:39.485038 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:55:39.485067 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:55:49.228270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:56:19.228201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:56:39.493944 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:56:39.494005 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:56:49.228312 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:57:19.228198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:57:39.501302 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:57:39.501347 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:57:49.228263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:58:19.228166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:58:39.511220 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:58:39.511264 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:58:49.228207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:59:19.228253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:59:39.518950 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:59:39.518996 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:59:49.228267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:00:19.228193 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:00:39.527009 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:00:39.527048 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:00:49.228231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:01:19.228264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:01:39.534845 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:01:39.534894 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:01:49.228214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:02:19.228263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:02:39.543854 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:02:39.543926 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:02:49.228270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:03:19.228227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:03:39.551657 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:03:39.551688 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:03:49.228225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:04:19.228247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:04:39.559101 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:04:39.559137 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:04:49.228184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:05:19.228231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:05:39.566917 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:05:39.567087 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:05:49.228165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:06:19.228338 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:06:39.574132 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:06:39.574178 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:06:49.228274 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:07:19.228209 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:07:39.582502 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:07:39.582560 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:07:49.228278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:08:19.228328 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:08:39.590917 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:08:39.590979 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:08:49.228148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:09:19.228291 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:09:39.599344 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:09:39.599384 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:09:49.228246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:10:19.228299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:10:39.607412 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:10:39.607479 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:10:49.228329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:11:19.228249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:11:39.615047 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:11:39.615101 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:11:49.228342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:12:19.228318 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:12:39.621250 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:12:39.621284 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:12:49.228290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:13:19.228274 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:13:39.628752 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:13:39.628821 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:13:49.228296 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:14:19.228193 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:14:39.636811 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:14:39.636846 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:14:49.228274 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:15:19.228219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:15:39.644844 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:15:39.644891 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:15:49.228196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:16:19.228184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:16:39.651795 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:16:39.651832 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:16:49.228226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:17:19.228327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:17:39.661399 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:17:39.661465 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:17:49.228209 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:18:19.228210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:18:39.669528 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:18:39.669564 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:18:49.228397 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:19:19.228246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:19:39.677051 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:19:39.677086 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:19:49.228331 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:20:19.228288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:20:39.683948 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:20:39.683980 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:20:49.228191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:21:19.228246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:21:39.692609 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:21:39.692654 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:21:49.228278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:22:19.228228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:22:39.700690 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:22:39.700738 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:22:49.228218 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:23:19.228345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:23:39.708137 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:23:39.708173 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:23:49.228301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:24:19.228397 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:24:39.716767 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:24:39.716825 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:24:49.228430 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:25:19.228250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:25:39.724763 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:25:39.724809 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:25:49.228169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:26:19.228168 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:26:39.731780 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:26:39.731816 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:26:49.228391 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:27:19.228378 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:27:39.740066 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:27:39.740104 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:27:49.228231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:28:19.228498 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:28:39.747547 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:28:39.747599 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:28:49.228214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:29:19.228275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:29:39.755905 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:29:39.755964 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:29:49.228275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:30:19.228468 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:30:39.763685 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:30:39.763722 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:30:49.228255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:31:19.228421 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:31:39.770187 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:31:39.770233 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:31:49.228345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:32:19.228243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:32:39.777779 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:32:39.777820 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:32:49.228337 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:33:19.228243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:33:39.785724 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:33:39.785759 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:33:49.228388 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:34:19.228308 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:34:39.793185 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:34:39.793222 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:34:49.228385 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:35:19.228206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:35:39.800741 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:35:39.800867 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:35:49.228433 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:36:19.228305 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:36:39.808384 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:36:39.808422 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:36:49.228161 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:37:19.228426 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:37:39.815231 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:37:39.815269 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:37:49.228200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:38:19.228433 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:38:39.822266 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:38:39.822313 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:38:49.228296 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:39:19.228401 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:39:39.829417 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:39:39.829471 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:39:49.228192 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:40:19.228319 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:40:39.837282 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:40:39.837318 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:40:49.228342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:41:19.228214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:41:39.845816 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:41:39.845874 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:41:49.228222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:42:19.228119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:42:39.853285 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:42:39.853325 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:42:49.228222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:43:19.228032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:43:39.860151 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:43:39.860198 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:43:49.228329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:44:19.228392 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:44:39.867641 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:44:39.867686 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:44:49.228335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:45:19.228307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:45:39.874715 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:45:39.874755 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:45:49.228354 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:46:19.228336 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:46:39.882762 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:46:39.882812 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:46:49.228168 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:47:19.228209 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:47:39.890536 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:47:39.890568 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:47:49.228352 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:48:19.228196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:48:39.898710 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:48:39.898767 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:48:49.228156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:49:19.228276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:49:39.910663 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:49:39.910696 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:49:49.228286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:50:19.228286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:50:39.918022 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:50:39.918073 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:50:49.228165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:51:19.228266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:51:39.925201 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:51:39.925245 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:51:49.228209 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:52:19.228316 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:52:39.932198 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:52:39.932324 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:52:49.228253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:53:19.228102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:53:39.939880 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:53:39.939924 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:53:49.228354 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:54:19.228334 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:54:39.946928 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:54:39.946975 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:54:49.228369 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:55:19.228269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:55:39.955831 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:55:39.955881 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:55:49.228173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:56:19.228337 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:56:39.965118 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:56:39.965180 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:56:49.228376 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:57:19.228198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:57:39.973255 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:57:39.973291 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:57:49.228329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:58:19.228368 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:58:39.979842 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:58:39.979884 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:58:49.228210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:59:19.228313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:59:39.987307 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:59:39.987358 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:59:49.228359 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:00:19.228325 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:00:39.994338 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:00:39.994374 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:00:49.228156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:01:19.228175 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:01:40.001282 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:01:40.001322 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:01:49.228166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:02:19.228420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:02:40.009473 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:02:40.009528 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:02:49.228341 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:03:19.228217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:03:40.017406 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:03:40.017466 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:03:49.228163 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:04:19.228372 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:04:40.023873 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:04:40.023923 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:04:49.228360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:05:19.228191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:05:40.032148 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:05:40.032214 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:05:49.228341 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:06:19.228196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:06:40.041317 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:06:40.041359 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:06:49.228302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:07:19.228403 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:07:40.048814 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:07:40.048868 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:07:49.228272 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:08:19.228368 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:08:40.056494 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:08:40.056541 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:08:49.228267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:09:19.228180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:09:40.064453 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:09:40.064524 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:09:49.228447 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:10:19.228341 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:10:40.071991 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:10:40.072021 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:10:49.228352 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:11:19.228272 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:11:40.079129 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:11:40.079179 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:11:49.228381 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:12:19.228230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:12:40.085988 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:12:40.086038 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:12:49.228392 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:13:19.228302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:13:40.093383 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:13:40.093421 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:13:49.228385 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:14:19.228406 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:14:40.100787 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:14:40.100829 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:14:49.228121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:15:19.228148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:15:40.108476 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:15:40.108522 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:15:49.228327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:16:19.228341 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:16:40.116884 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:16:40.116915 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:16:49.228246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:17:19.228183 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:17:40.125374 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:17:40.125415 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:17:49.228229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:18:19.228199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:18:40.131662 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:18:40.131700 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:18:49.228194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:19:19.228229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:19:40.139942 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:19:40.140012 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:19:49.228174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:20:19.228224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:20:40.147413 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:20:40.147453 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:20:49.228233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:21:19.228229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:21:40.155895 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:21:40.155938 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:21:49.228209 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:22:19.228211 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:22:40.164537 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:22:40.164581 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:22:49.228084 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:23:19.228455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:23:40.173480 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:23:40.173531 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:23:49.228376 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:24:19.228368 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:24:40.179869 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:24:40.179909 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:24:49.228247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:25:19.228317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:25:40.187399 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:25:40.187440 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:25:49.228165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:26:19.228224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:26:40.195862 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:26:40.195920 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:26:49.228369 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:27:19.228408 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:27:40.202782 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:27:40.202844 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:27:49.228351 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:28:19.228184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:28:40.210830 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:28:40.210879 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:28:49.228422 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:29:19.228218 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:29:40.218524 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:29:40.218571 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:29:49.228327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:30:19.228186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:30:40.226923 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:30:40.226965 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:30:49.228359 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:31:19.228280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:31:40.234249 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:31:40.234290 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:31:49.228226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:32:19.228250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:32:40.242641 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:32:40.242681 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:32:49.228188 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:33:19.228374 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:33:40.250437 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:33:40.250473 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:33:49.228329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:34:19.228355 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:34:40.258310 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:34:40.258383 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:34:49.228392 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:35:19.228444 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:35:40.265289 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:35:40.265335 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:35:49.228212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:36:19.228193 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:36:40.272404 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:36:40.272444 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:36:49.228259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:37:19.228265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:37:40.281673 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:37:40.281717 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:37:49.228227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:38:19.228408 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:38:40.289733 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:38:40.289789 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:38:49.228415 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:39:19.228296 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:39:40.297465 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:39:40.297505 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:39:49.228146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:40:19.228305 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:40:40.305334 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:40:40.305379 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:40:49.228224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:41:19.228268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:41:40.313035 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:41:40.313079 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:41:49.228221 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:42:19.228202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:42:40.321842 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:42:40.321911 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:42:49.228291 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:43:19.228138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:43:40.329555 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:43:40.329596 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:43:49.228217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:44:19.228170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:44:40.336829 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:44:40.336863 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:44:49.228260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:45:19.228211 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:45:40.344266 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:45:40.344317 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:45:49.228239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:46:19.228121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:46:40.352517 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:46:40.352568 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:46:49.228310 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:47:19.228108 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:47:40.361103 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:47:40.361135 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:47:49.228198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:48:19.228187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:48:40.371985 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:48:40.372023 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:48:49.228191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:49:19.228219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:49:40.379029 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:49:40.379086 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:49:49.228165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:50:19.228199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:50:40.386178 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:50:40.386211 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:50:49.228286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:51:19.228117 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:51:40.393110 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:51:40.393159 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:51:49.228167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:52:19.228131 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:52:40.400166 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:52:40.400200 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:52:49.228257 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:53:19.228259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:53:40.407872 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:53:40.407925 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:53:49.228182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:54:19.228235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:54:40.416081 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:54:40.416123 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:54:49.228224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:55:19.228159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:55:40.423854 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:55:40.423953 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:55:49.228150 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:56:19.228226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:56:40.430717 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:56:40.430757 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:56:49.228327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:57:19.228195 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:57:40.437607 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:57:40.437667 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:57:49.228159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:58:19.228261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:58:40.445635 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:58:40.445669 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:58:49.228266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:59:19.228223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:59:40.453913 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:59:40.453961 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:59:49.228219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:00:19.228336 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:00:40.461683 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:00:40.461737 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:00:49.228307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:01:19.228189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:01:40.469100 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:01:40.469144 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:01:49.228154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:02:19.228176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:02:40.475925 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:02:40.475980 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:02:49.228194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:03:19.228184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:03:40.482670 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:03:40.482701 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:03:49.228205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:04:19.228205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:04:40.489815 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:04:40.489865 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:04:49.228195 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:05:19.228135 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:05:40.497800 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:05:40.497850 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:05:49.228193 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:06:19.228200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:06:40.505095 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:06:40.505141 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:06:49.228178 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:07:19.228102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:07:40.512126 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:07:40.512210 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:07:49.228141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:08:19.228323 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:08:40.518774 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:08:40.518831 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:08:49.228381 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:09:19.228150 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:09:40.525358 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:09:40.525396 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:09:49.228307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:10:19.228327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:10:40.531884 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:10:40.531916 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:10:49.228305 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:11:19.228302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:11:40.541302 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:11:40.541345 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:11:49.228264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:12:19.228372 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:12:40.547861 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:12:40.547901 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:12:49.228108 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:13:19.228222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:13:40.555650 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:13:40.555700 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:13:49.228341 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:14:19.228354 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:14:40.564808 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:14:40.564852 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:14:49.228299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:15:19.228260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:15:40.573722 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:15:40.573760 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:15:49.228244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:16:19.228309 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:16:40.581159 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:16:40.581192 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:16:49.228252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:17:19.228250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:17:40.590425 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:17:40.590471 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:17:49.228263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:18:19.228292 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:18:40.597289 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:18:40.597332 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:18:49.228224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:19:19.228198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:19:40.605154 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:19:40.605210 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:19:49.228196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:20:19.228217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:20:40.612858 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:20:40.612897 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:20:49.228267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:21:19.228270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:21:40.622081 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:21:40.622111 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:21:49.228302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:22:19.228277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:22:40.629604 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:22:40.629662 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:22:49.228269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:23:19.228209 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:23:40.640758 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:23:40.640796 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:23:49.228221 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:24:19.228352 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:24:40.647718 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:24:40.647772 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:24:49.228176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:25:19.228268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:25:40.657164 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:25:40.657213 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:25:49.228367 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:26:19.228364 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:26:40.666137 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:26:40.666168 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:26:49.228187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:27:19.228481 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:27:40.686798 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:27:40.686834 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:27:49.228181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:28:19.228208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:28:40.693959 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:28:40.694057 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:28:49.228258 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:29:19.228387 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:29:40.701098 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:29:40.701223 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:29:49.228255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:30:19.228268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:30:40.709630 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:30:40.709709 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:30:49.228273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:31:19.228189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:31:40.717287 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:31:40.717322 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:31:49.228252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:32:19.228361 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:32:40.724690 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:32:40.724729 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:32:49.228323 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:33:19.228376 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:33:40.733956 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:33:40.733985 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:33:49.228235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:34:19.228267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:34:40.741046 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:34:40.741074 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:34:49.228288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:35:19.228315 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:35:40.748642 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:35:40.748687 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:35:49.228269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:36:19.228299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:36:40.761156 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:36:40.761204 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:36:49.228181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:37:19.228147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:37:40.769236 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:37:40.769290 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:37:49.228312 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:38:19.228325 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:38:40.776804 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:38:40.776867 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:38:49.228294 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:39:19.228244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:39:40.785342 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:39:40.785384 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:39:49.228379 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:40:19.228267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:40:40.792960 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:40:40.793017 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:40:49.228196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:41:19.228195 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:41:40.799530 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:41:40.799585 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:41:49.228463 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:42:19.228186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:42:40.806508 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:42:40.806550 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:42:49.228307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:43:19.228284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:43:40.814579 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:43:40.814623 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:43:49.228250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:44:19.228329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:44:40.821610 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:44:40.821658 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:44:49.228182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:45:19.228312 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:45:40.828922 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:45:40.828957 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:45:49.228340 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:46:19.228141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:46:40.836664 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:46:40.836731 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:46:49.228142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:47:19.228458 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:47:40.845719 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:47:40.845768 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:47:49.228232 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:48:19.228167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:48:40.853447 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:48:40.853501 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:48:49.228181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:49:19.228221 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:49:40.861322 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:49:40.861357 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:49:49.228158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:50:19.228303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:50:40.872969 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:50:40.873001 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:50:49.228221 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:51:19.228120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:51:40.880130 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:51:40.880170 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:51:49.228280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:52:19.228197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:52:40.886652 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:52:40.886689 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:52:49.228212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:53:19.228244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:53:40.893749 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:53:40.893794 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:53:49.228145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:54:19.228188 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:54:40.901421 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:54:40.901473 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:54:49.228249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:55:19.228268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:55:40.908789 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:55:40.908827 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:55:49.228217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:56:19.228227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:56:40.915849 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:56:40.915897 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:56:49.228238 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:57:19.228284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:57:40.925210 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:57:40.925256 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:57:49.228092 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:58:19.228174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:58:40.935956 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:58:40.935993 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:58:49.228185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:59:19.228233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:59:40.943635 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:59:40.943683 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:59:49.228250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:00:19.228249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:00:40.950077 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:00:40.950110 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:00:49.228213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:01:19.228122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:01:40.958371 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:01:40.958411 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:01:49.228190 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:02:19.228156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:02:40.966167 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:02:40.966202 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:02:49.228249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:03:19.228167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:03:40.973702 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:03:40.973735 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:03:49.228189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:04:19.228265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:04:40.980875 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:04:40.980913 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:04:49.228259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:05:19.228183 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:05:40.988862 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:05:40.988906 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:05:49.228271 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:06:19.228135 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:06:40.997502 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:06:40.997551 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:06:49.228254 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:07:19.228244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:07:41.004484 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:07:41.004521 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:07:49.228280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:08:19.228256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:08:41.011867 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:08:41.011910 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:08:49.228142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:09:19.228353 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:09:41.022129 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:09:41.022180 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:09:49.228221 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:10:19.228327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:10:41.030118 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:10:41.030180 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:10:49.228121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:11:19.228316 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:11:41.037031 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:11:41.037092 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:11:49.228220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:12:19.228133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:12:41.045374 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:12:41.045417 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:12:49.228181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:13:19.228245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:13:41.052963 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:13:41.053007 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:13:49.228114 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:14:19.228310 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:14:41.060619 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:14:41.060666 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:14:49.228287 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:15:19.228221 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:15:41.067969 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:15:41.068011 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:15:49.228165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:16:19.228270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:16:41.076410 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:16:41.076441 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:16:49.228190 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:17:19.228180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:17:41.084966 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:17:41.085007 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:17:49.228244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:18:19.228214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:18:41.092372 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:18:41.092422 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:18:49.228147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:19:19.228324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:19:41.099918 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:19:41.099950 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:19:49.228303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:20:19.228282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:20:41.111045 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:20:41.111091 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:20:49.228304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:21:19.228408 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:21:41.124268 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:21:41.124299 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:21:49.228230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:22:19.228321 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:22:41.133026 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:22:41.133076 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:22:49.228179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:23:19.228279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:23:41.159067 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:23:41.159121 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:23:49.228239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:24:19.228251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:24:41.167995 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:24:41.168052 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:24:49.228220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:25:19.228173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:25:41.175472 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:25:41.175510 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:25:49.228250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:26:19.228177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:26:41.182956 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:26:41.183005 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:26:49.228233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:27:19.228392 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:27:41.189046 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:27:41.189089 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:27:49.228231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:28:19.228184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:28:41.196148 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:28:41.196191 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:28:49.228223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:29:19.228276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:29:41.203324 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:29:41.203365 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:29:49.228177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:30:19.228175 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:30:41.212406 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:30:41.212561 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:30:49.228241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:31:19.228199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:31:41.221004 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:31:41.221051 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:31:49.228149 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:32:19.228182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:32:41.229104 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:32:41.229157 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:32:49.228185 metrics.go:34: INFO No non-zero metrics in the last 30s