Results

          2022/01/04 02:49:33.467787 beat.go:285: INFO Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs]
2022/01/04 02:49:33.467821 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/01/04 02:49:33.467905 logstash.go:90: INFO Max Retries set to: 3
2022/01/04 02:49:33.467967 outputs.go:108: INFO Activated logstash as output plugin.
2022/01/04 02:49:33.468026 metrics.go:23: INFO Metrics logging every 30s
2022/01/04 02:49:33.468101 publish.go:295: INFO Publisher name: onap-portal-app-9c5c78dc6-pm79b
2022/01/04 02:49:33.468276 async.go:63: INFO Flush Interval set to: 1s
2022/01/04 02:49:33.468300 async.go:64: INFO Max Bulk Size set to: 2048
2022/01/04 02:49:33.468740 beat.go:221: INFO filebeat start running.
2022/01/04 02:49:33.468852 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/01/04 02:49:33.475613 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/01/04 02:49:33.475685 registrar.go:123: INFO States Loaded from registrar: 0
2022/01/04 02:49:33.475745 crawler.go:38: INFO Loading Prospectors: 1
2022/01/04 02:49:33.475843 registrar.go:236: INFO Starting Registrar
2022/01/04 02:49:33.475974 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/01/04 02:49:33.476006 sync.go:41: INFO Start sending events to output
2022/01/04 02:49:33.476090 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/01/04 02:49:33.476097 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/01/04 02:49:33.476178 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/01/04 02:49:43.477717 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/01/04 02:49:43.477783 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/01/04 02:49:43.477740 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/01/04 02:49:43.478049 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/01/04 02:49:43.478215 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/01/04 02:49:48.487162 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 02:49:48.487200 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 02:49:49.490920 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 02:49:49.490946 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 02:49:51.494536 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 02:49:51.494572 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 02:49:55.503561 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 02:49:55.503599 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 02:50:03.468842 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=76 registrar.writes=1
2022/01/04 02:50:03.512464 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 02:50:03.512540 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 02:50:19.523012 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 02:50:19.523091 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 02:50:33.468338 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 02:50:51.534933 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 02:50:51.534971 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 02:51:03.468369 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 02:51:33.468388 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 02:51:51.545598 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 02:51:51.545649 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 02:52:03.468509 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 02:52:33.468326 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 02:52:51.555858 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 02:52:51.555908 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 02:53:03.468310 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 02:53:33.468298 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 02:53:51.566111 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 02:53:51.566156 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 02:54:03.468367 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 02:54:33.468399 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 02:54:48.487766 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/01/04 02:54:51.578574 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 02:54:51.578607 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 02:55:03.468424 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/01/04 02:55:33.468332 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 02:55:51.589601 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 02:55:51.589629 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 02:56:03.468588 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 02:56:33.468557 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 02:56:51.603063 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 02:56:51.603115 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 02:57:03.468546 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 02:57:33.468441 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 02:57:51.611920 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 02:57:51.611948 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 02:58:03.468499 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 02:58:33.468417 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 02:58:51.622694 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 02:58:51.622741 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 02:59:03.468563 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 02:59:33.468623 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 02:59:51.633693 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 02:59:51.633740 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:00:03.468513 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:00:33.468278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:00:51.646128 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:00:51.646157 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:01:03.468500 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:01:33.468559 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:01:51.656356 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:01:51.656403 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:02:03.468529 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:02:33.468500 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:02:51.668035 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:02:51.668080 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:03:03.468306 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:03:33.468430 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:03:51.678248 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:03:51.678288 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:04:03.468379 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:04:33.468353 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:04:51.693046 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:04:51.693086 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:05:03.468359 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:05:33.468452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:05:51.704650 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:05:51.704696 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:06:03.468484 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:06:33.468514 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:06:51.724453 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:06:51.724494 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:07:03.468465 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:07:33.468624 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:07:51.733928 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:07:51.733978 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:08:03.468343 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:08:33.468437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:08:51.747190 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:08:51.747239 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:09:03.468446 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:09:33.468373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:09:51.756457 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:09:51.756521 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:10:03.468444 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:10:33.468312 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:10:51.767315 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:10:51.767340 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:11:03.468449 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:11:33.468497 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:11:51.777542 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:11:51.777596 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:12:03.468368 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:12:33.468458 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:12:51.789335 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:12:51.789379 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:13:03.468387 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:13:33.468465 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:13:51.799607 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:13:51.799635 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:14:03.468386 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:14:33.468355 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:14:51.810659 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:14:51.810697 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:15:03.468472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:15:33.468382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:15:51.821538 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:15:51.821823 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:16:03.468464 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:16:33.468455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:16:51.834470 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:16:51.834515 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:17:03.468430 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:17:33.468390 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:17:51.845196 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:17:51.845260 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:18:03.468434 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:18:33.468382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:18:51.855902 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:18:51.855931 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:19:03.468581 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:19:33.468512 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:19:51.865724 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:19:51.865770 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:20:03.468435 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:20:33.468452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:20:51.878899 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:20:51.878947 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:21:03.468396 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:21:33.468474 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:21:51.888671 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:21:51.888708 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:22:03.468477 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:22:33.468484 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:22:51.904680 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:22:51.904711 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:23:03.468556 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:23:33.468615 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:23:51.914768 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:23:51.914816 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:24:03.468419 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:24:33.468434 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:24:51.926695 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:24:51.926801 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:25:03.468373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:25:33.468394 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:25:51.936673 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:25:51.936720 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:26:03.468439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:26:33.468387 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:26:51.947648 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:26:51.947700 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:27:03.468495 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:27:33.468475 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:27:51.957231 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:27:51.957286 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:28:03.468491 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:28:33.468457 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:28:51.969614 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:28:51.969669 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:29:03.468417 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:29:33.468551 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:29:51.980730 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:29:51.980787 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:30:03.468395 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:30:33.468342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:30:51.992606 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:30:51.992643 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:31:03.468536 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:31:33.468357 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:31:52.002314 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:31:52.002341 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:32:03.468366 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:32:33.468377 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:32:52.012953 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:32:52.012989 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:33:03.468430 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:33:33.468391 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:33:52.023302 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:33:52.023342 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:34:03.468436 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:34:33.468311 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:34:52.032699 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:34:52.032745 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:35:03.468312 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:35:33.468453 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:35:52.042824 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:35:52.042867 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:36:03.468352 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:36:33.468535 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:36:52.053043 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:36:52.053085 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:37:03.468496 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:37:33.468501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:37:52.061840 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:37:52.061872 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:38:03.468553 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:38:33.468476 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:38:52.071724 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:38:52.071758 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:39:03.468350 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:39:33.468434 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:39:52.082461 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:39:52.082521 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:40:03.468448 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:40:33.468397 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:40:52.095392 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:40:52.095462 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:41:03.468512 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:41:33.468415 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:41:52.103270 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:41:52.103313 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:42:03.468427 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:42:33.468365 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:42:52.118374 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:42:52.118427 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:43:03.469352 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:43:33.468587 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:43:52.127622 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:43:52.127677 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:44:03.468633 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:44:33.468617 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:44:52.138029 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:44:52.138096 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:45:03.468350 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:45:33.468360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:45:52.148592 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:45:52.148636 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:46:03.468393 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:46:33.468470 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:46:52.161213 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:46:52.161262 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:47:03.468497 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:47:33.468499 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:47:52.170548 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:47:52.170585 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:48:03.468414 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:48:33.468400 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:48:52.183828 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:48:52.183860 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:49:03.468452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:49:33.468316 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:49:52.192386 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:49:52.192433 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:50:03.468302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:50:33.468331 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:50:52.203266 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:50:52.203308 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:51:03.468354 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:51:33.468746 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:51:52.214297 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:51:52.214352 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:52:03.468410 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:52:33.468478 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:52:52.226423 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:52:52.226454 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:53:03.468441 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:53:33.468396 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:53:52.234860 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:53:52.234888 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:54:03.468248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:54:33.468407 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:54:52.245941 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:54:52.245972 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:55:03.468468 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:55:33.468364 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:55:52.256022 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:55:52.256054 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:56:03.468496 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:56:33.468411 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:56:52.267493 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:56:52.267532 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:57:03.468418 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:57:33.468489 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:57:52.277833 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:57:52.277884 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:58:03.468531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:58:33.473095 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:58:52.288748 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:58:52.288786 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:59:03.468391 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:59:33.468486 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:59:52.299581 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:59:52.299651 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:00:03.468496 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:00:33.468414 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:00:52.311202 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:00:52.311229 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:01:03.468440 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:01:33.468428 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:01:52.320411 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:01:52.320483 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:02:03.468504 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:02:33.468439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:02:52.332943 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:02:52.332991 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:03:03.468443 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:03:33.468414 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:03:52.342126 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:03:52.342158 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:04:03.468406 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:04:33.468417 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:04:52.352605 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:04:52.352644 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:05:03.468531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:05:33.468444 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:05:52.362605 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:05:52.362636 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:06:03.468469 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:06:33.468421 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:06:52.372022 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:06:52.372066 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:07:03.468453 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:07:33.468517 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:07:52.381342 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:07:52.381389 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:08:03.468432 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:08:33.468472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:08:52.392476 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:08:52.392513 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:09:03.468410 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:09:33.468360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:09:52.401019 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:09:52.401047 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:10:03.468472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:10:33.468494 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:10:52.411923 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:10:52.411955 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:11:03.468459 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:11:33.468341 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:11:52.421868 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:11:52.421901 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:12:03.468372 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:12:33.468537 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:12:52.432845 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:12:52.432884 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:13:03.468420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:13:33.468438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:13:52.448591 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:13:52.448632 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:14:03.468410 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:14:33.468312 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:14:52.460357 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:14:52.460400 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:15:03.468515 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:15:33.468478 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:15:52.472725 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:15:52.472784 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:16:03.468300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:16:33.468556 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:16:52.482594 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:16:52.482646 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:17:03.468398 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:17:33.468360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:17:52.493050 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:17:52.493086 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:18:03.468422 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:18:33.468372 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:18:52.503711 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:18:52.503759 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:19:03.468411 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:19:33.468494 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:19:52.513913 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:19:52.513949 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:20:03.468446 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:20:33.468465 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:20:52.523325 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:20:52.523379 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:21:03.468600 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:21:33.468333 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:21:52.532958 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:21:52.533007 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:22:03.468484 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:22:33.468295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:22:52.545822 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:22:52.545879 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:23:03.468504 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:23:33.468559 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:23:52.556520 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:23:52.556570 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:24:03.468438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:24:33.468488 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:24:52.567427 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:24:52.567454 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:25:03.468492 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:25:33.468477 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:25:52.580260 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:25:52.580301 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:26:03.468485 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:26:33.468478 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:26:52.591345 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:26:52.591393 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:27:03.468380 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:27:33.468489 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:27:52.600884 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:27:52.600932 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:28:03.468528 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:28:33.468486 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:28:52.613021 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:28:52.613064 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:29:03.468516 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:29:33.468485 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:29:52.624156 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:29:52.624201 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:30:03.468428 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:30:33.468423 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:30:52.636039 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:30:52.636366 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:31:03.469109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:31:33.468776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:31:52.647856 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:31:52.647897 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:32:03.468476 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:32:33.468537 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:32:52.658370 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:32:52.658396 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:33:03.468575 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:33:33.468418 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:33:52.669746 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:33:52.669790 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:34:03.468581 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:34:33.468656 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:34:52.681907 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:34:52.681948 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:35:03.468410 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:35:33.468698 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:35:52.690942 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:35:52.690999 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:36:03.468405 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:36:33.468350 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:36:52.703531 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:36:52.703573 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:37:03.468573 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:37:33.468377 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:37:52.714768 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:37:52.714835 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:38:03.468508 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:38:33.468412 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:38:52.725317 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:38:52.725383 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:39:03.468593 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:39:33.468438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:39:52.736125 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:39:52.736174 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:40:03.468421 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:40:33.468339 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:40:52.748205 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:40:52.748240 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:41:03.468384 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:41:33.468419 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:41:52.759848 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:41:52.759902 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:42:03.468426 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:42:33.468361 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:42:52.770254 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:42:52.770302 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:43:03.468417 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:43:33.468437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:43:52.781084 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:43:52.781131 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:44:03.468359 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:44:33.468420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:44:52.792749 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:44:52.792786 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:45:03.468476 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:45:33.468415 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:45:52.803344 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:45:52.803388 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:46:03.468265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:46:33.468456 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:46:52.818008 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:46:52.818078 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:47:03.468490 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:47:33.468374 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:47:52.826806 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:47:52.826838 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:48:03.468497 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:48:33.468488 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:48:52.838896 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:48:52.838950 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:49:03.468436 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:49:33.468428 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:49:52.847612 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:49:52.847637 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:50:03.468350 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:50:33.468498 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:50:52.858730 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:50:52.858782 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:51:03.468456 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:51:33.468354 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:51:52.873374 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:51:52.873416 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:52:03.468436 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:52:33.468435 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:52:52.885648 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:52:52.885700 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:53:03.468414 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:53:33.468419 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:53:52.894153 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:53:52.894195 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:54:03.468410 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:54:33.468395 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:54:52.906667 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:54:52.906711 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:55:03.468439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:55:33.468440 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:55:52.917180 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:55:52.917221 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:56:03.468460 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:56:33.468325 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:56:52.929792 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:56:52.929825 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:57:03.468460 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:57:33.468392 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:57:52.941054 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:57:52.941101 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:58:03.468520 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:58:33.468460 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:58:52.953523 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:58:52.953569 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:59:03.468382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:59:33.468471 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:59:52.965130 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:59:52.965164 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:00:03.468250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:00:33.468448 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:00:52.975216 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:00:52.975282 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:01:03.468482 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:01:33.468412 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:01:52.985690 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:01:52.985738 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:02:03.468452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:02:33.468456 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:02:52.999008 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:02:52.999063 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:03:03.468390 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:03:33.468424 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:03:53.010140 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:03:53.010213 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:04:03.468525 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:04:33.468282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:04:53.022990 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:04:53.023033 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:05:03.468536 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:05:33.468469 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:05:53.034564 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:05:53.034608 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:06:03.468405 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:06:33.468427 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:06:53.048332 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:06:53.048376 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:07:03.468335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:07:33.468508 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:07:53.056391 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:07:53.056445 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:08:03.468424 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:08:33.468371 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:08:53.070078 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:08:53.070138 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:09:03.468409 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:09:33.468547 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:09:53.080444 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:09:53.080490 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:10:03.468485 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:10:33.468520 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:10:53.092282 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:10:53.092313 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:11:03.468295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:11:33.468564 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:11:53.104252 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:11:53.104310 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:12:03.468438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:12:33.468338 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:12:53.116394 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:12:53.116446 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:13:03.468462 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:13:33.468405 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:13:53.127233 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:13:53.127286 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:14:03.468380 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:14:33.468401 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:14:53.137956 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:14:53.137996 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:15:03.468498 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:15:33.468539 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:15:53.148445 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:15:53.148488 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:16:03.468457 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:16:33.468453 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:16:53.158782 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:16:53.158807 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:17:03.468302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:17:33.468551 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:17:53.167427 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:17:53.167507 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:18:03.468339 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:18:33.468419 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:18:53.180428 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:18:53.180491 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:19:03.468424 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:19:33.468462 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:19:53.190839 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:19:53.190899 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:20:03.468333 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:20:33.468511 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:20:53.202689 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:20:53.202730 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:21:03.468541 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:21:33.468433 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:21:53.212436 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:21:53.212476 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:22:03.468334 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:22:33.468316 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:22:53.221146 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:22:53.221174 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:23:03.468473 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:23:33.468359 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:23:53.232096 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:23:53.232216 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:24:03.468375 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:24:33.468441 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:24:53.243931 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:24:53.243981 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:25:03.468489 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:25:33.468456 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:25:53.254131 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:25:53.254170 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:26:03.468362 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:26:33.468420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:26:53.266609 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:26:53.266669 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:27:03.468346 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:27:33.468426 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:27:53.276103 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:27:53.276165 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:28:03.468485 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:28:33.468543 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:28:53.286250 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:28:53.286314 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:29:03.468442 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:29:33.468366 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:29:53.296433 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:29:53.296480 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:30:03.468437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:30:33.468518 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:30:53.308275 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:30:53.308310 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:31:03.468413 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:31:33.468457 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:31:53.318877 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:31:53.318919 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:32:03.468487 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:32:33.468420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:32:53.329538 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:32:53.329608 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:33:03.468433 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:33:33.468480 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:33:53.338670 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:33:53.338708 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:34:03.468635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:34:33.468382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:34:53.347446 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:34:53.347490 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:35:03.468535 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:35:33.468497 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:35:53.357117 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:35:53.357159 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:36:03.468409 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:36:33.468447 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:36:53.367047 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:36:53.367085 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:37:03.468394 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:37:33.468412 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:37:53.375485 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:37:53.375655 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:38:03.468359 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:38:33.468411 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:38:53.386195 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:38:53.386242 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:39:03.468393 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:39:33.468496 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:39:53.396979 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:39:53.397024 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:40:03.468493 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:40:33.468569 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:40:53.439716 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:40:53.439757 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:41:03.468362 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:41:33.468436 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:41:53.454335 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:41:53.454386 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:42:03.468367 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:42:33.468443 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:42:53.463827 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:42:53.463858 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:43:03.468503 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:43:33.468490 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:43:53.471940 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:43:53.471984 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:44:03.468464 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:44:33.468562 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:44:53.480410 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:44:53.480462 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:45:03.468438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:45:33.468452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:45:53.490119 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:45:53.490171 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:46:03.468386 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:46:33.468544 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:46:53.498145 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:46:53.498200 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:47:03.468398 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:47:33.468360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:47:53.507539 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:47:53.507592 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:48:03.468592 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:48:33.468505 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:48:53.517612 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:48:53.517655 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:49:03.468468 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:49:33.468369 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:49:53.527287 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:49:53.527332 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:50:03.468616 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:50:33.468385 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:50:53.537028 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:50:53.537063 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:51:03.468373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:51:33.468440 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:51:53.546258 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:51:53.546319 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:52:03.468417 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:52:33.468414 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:52:53.556851 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:52:53.556895 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:53:03.468455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:53:33.468436 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:53:53.565864 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:53:53.565901 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:54:03.468337 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:54:33.468297 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:54:53.576649 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:54:53.576688 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:55:03.468406 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:55:33.468527 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:55:53.586549 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:55:53.586593 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:56:03.468394 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:56:33.468447 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:56:53.596757 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:56:53.596860 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:57:03.468412 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:57:33.468433 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:57:53.606088 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:57:53.606119 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:58:03.468522 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:58:33.468459 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:58:53.617996 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:58:53.618043 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:59:03.468533 metrics.go:34: INFO No non-zero metrics in the last 30s