By type
2022/01/13 03:56:14.726285 beat.go:285: INFO Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs]
2022/01/13 03:56:14.726329 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/01/13 03:56:14.726397 logstash.go:90: INFO Max Retries set to: 3
2022/01/13 03:56:14.726467 outputs.go:108: INFO Activated logstash as output plugin.
2022/01/13 03:56:14.726497 metrics.go:23: INFO Metrics logging every 30s
2022/01/13 03:56:14.726598 publish.go:295: INFO Publisher name: onap-portal-app-9c5c78dc6-bp4v5
2022/01/13 03:56:14.726801 async.go:63: INFO Flush Interval set to: 1s
2022/01/13 03:56:14.726826 async.go:64: INFO Max Bulk Size set to: 2048
2022/01/13 03:56:14.727205 beat.go:221: INFO filebeat start running.
2022/01/13 03:56:14.727276 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/01/13 03:56:15.498325 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/01/13 03:56:15.498418 registrar.go:123: INFO States Loaded from registrar: 0
2022/01/13 03:56:15.498497 crawler.go:38: INFO Loading Prospectors: 1
2022/01/13 03:56:15.498596 registrar.go:236: INFO Starting Registrar
2022/01/13 03:56:15.498691 sync.go:41: INFO Start sending events to output
2022/01/13 03:56:15.498704 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/01/13 03:56:15.498769 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/01/13 03:56:15.498826 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/01/13 03:56:15.498851 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/01/13 03:56:15.499462 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/01/13 03:56:15.499658 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/01/13 03:56:15.499760 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/01/13 03:56:15.499673 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/01/13 03:56:15.499819 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/01/13 03:56:15.536971 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:56:15.537008 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:56:16.539961 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:56:16.540003 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:56:18.543056 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:56:18.543088 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:56:22.550400 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:56:22.550442 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:56:30.558541 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:56:30.558570 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:56:44.726941 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=2043 registrar.writes=1
2022/01/13 03:56:46.563823 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:56:46.563850 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:57:14.726853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 03:57:18.569693 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:57:18.569721 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:57:44.726797 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 03:58:14.726898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 03:58:18.578678 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:58:18.578729 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:58:44.726826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 03:59:14.726804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 03:59:18.586731 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:59:18.586780 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 03:59:44.726756 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:00:14.726842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:00:18.594823 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:00:18.594865 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:00:44.726817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:01:14.726823 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:01:18.601966 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:01:18.602100 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:01:20.509102 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/01/13 04:01:44.726788 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/01/13 04:02:14.726801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:02:18.610330 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:02:18.610368 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:02:44.726808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:03:14.726883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:03:18.618825 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:03:18.618865 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:03:44.726826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:04:14.726801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:04:18.626699 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:04:18.626724 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:04:44.726809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:05:14.726790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:05:18.632612 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:05:18.632645 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:05:44.726767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:06:14.726796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:06:18.641500 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:06:18.641537 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:06:44.726816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:07:14.726784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:07:18.650558 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:07:18.650588 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:07:44.726807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:08:14.726777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:08:18.659838 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:08:18.659883 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:08:44.726854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:09:14.726825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:09:18.667098 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:09:18.667152 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:09:44.726825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:10:14.726831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:10:18.676936 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:10:18.676973 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:10:44.726812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:11:14.726807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:11:18.684628 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:11:18.684679 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:11:44.726836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:12:14.726822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:12:18.692130 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:12:18.692168 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:12:44.726866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:13:14.726815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:13:18.698480 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:13:18.698518 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:13:44.726785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:14:14.726785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:14:18.709974 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:14:18.710089 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:14:44.726862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:15:14.726806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:15:18.716907 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:15:18.716938 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:15:44.726831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:16:14.726797 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:16:18.726772 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:16:18.726809 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:16:44.726759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:17:14.726806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:17:18.734079 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:17:18.734117 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:17:44.726773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:18:14.726799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:18:18.740864 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:18:18.740898 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:18:44.726998 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:19:14.726874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:19:18.748910 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:19:18.748942 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:19:44.726784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:20:14.726814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:20:18.757422 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:20:18.757454 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:20:44.726810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:21:14.726795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:21:18.764373 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:21:18.764407 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:21:44.726839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:22:14.726807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:22:18.773620 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:22:18.773653 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:22:44.726803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:23:14.726901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:23:18.784040 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:23:18.784182 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:23:44.726839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:24:14.726800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:24:18.795483 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:24:18.795522 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:24:44.726771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:25:14.726815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:25:18.802967 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:25:18.803009 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:25:44.726836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:26:14.726811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:26:18.812303 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:26:18.812344 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:26:44.726806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:27:14.727076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:27:18.819174 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:27:18.819216 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:27:44.726811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:28:14.726912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:28:18.831424 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:28:18.831458 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:28:44.726854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:29:14.726854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:29:18.838959 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:29:18.839007 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:29:44.726760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:30:14.726808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:30:18.848018 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:30:18.848047 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:30:44.726839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:31:14.726816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:31:18.854440 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:31:18.854487 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:31:44.726834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:32:14.726805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:32:18.861321 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:32:18.861360 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:32:44.726836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:33:14.726774 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:33:18.867742 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:33:18.867822 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:33:44.726812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:34:14.726811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:34:18.877016 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:34:18.877049 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:34:44.726829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:35:14.726821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:35:18.883881 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:35:18.883929 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:35:44.726833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:36:14.726803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:36:18.892605 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:36:18.892660 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:36:44.726851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:37:14.726791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:37:18.899556 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:37:18.899591 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:37:44.726811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:38:14.726867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:38:18.909967 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:38:18.910001 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:38:44.726835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:39:14.726872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:39:18.917915 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:39:18.917948 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:39:44.726848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:40:14.726783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:40:18.927688 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:40:18.927738 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:40:44.726793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:41:14.726828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:41:18.933972 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:41:18.934005 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:41:44.726799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:42:14.726829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:42:18.942054 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:42:18.942082 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:42:44.726783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:43:14.726825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:43:18.948855 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:43:18.948901 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:43:44.726825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:44:14.726836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:44:18.957268 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:44:18.957318 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:44:44.726790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:45:14.726866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:45:18.964686 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:45:18.964717 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:45:44.726846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:46:14.726833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:46:18.974560 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:46:18.974594 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:46:44.726834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:47:14.726820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:47:18.982165 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:47:18.982192 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:47:44.726839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:48:14.726825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:48:18.989755 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:48:18.989788 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:48:44.726887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:49:14.726820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:49:18.996634 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:49:18.996667 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:49:44.726794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:50:14.726749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:50:19.005653 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:50:19.005699 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:50:44.726812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:51:14.726798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:51:19.012110 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:51:19.012140 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:51:44.726822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:52:14.726815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:52:19.020840 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:52:19.020878 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:52:44.726828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:53:14.726762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:53:19.028488 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:53:19.028526 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:53:44.726801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:54:14.726832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:54:19.040052 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:54:19.040090 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:54:44.726855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:55:14.726776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:55:19.046787 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:55:19.046946 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:55:44.726838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:56:14.726789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:56:19.057913 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:56:19.057946 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:56:44.726832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:57:14.726840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:57:19.065986 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:57:19.066032 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:57:44.726802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:58:14.726795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:58:19.074712 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:58:19.074745 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:58:44.726828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:59:14.726798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 04:59:19.081269 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:59:19.081315 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 04:59:44.726838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:00:14.726792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:00:19.090646 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:00:19.090674 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:00:44.726822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:01:14.726777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:01:19.098602 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:01:19.098631 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:01:44.726871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:02:14.726836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:02:19.106875 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:02:19.106926 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:02:44.726806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:03:14.726793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:03:19.113888 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:03:19.113930 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:03:44.726832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:04:14.726948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:04:19.121537 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:04:19.121576 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:04:44.726806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:05:14.726776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:05:19.128188 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:05:19.128235 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:05:44.726821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:06:14.726804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:06:19.135561 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:06:19.135599 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:06:44.726827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:07:14.726804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:07:19.142212 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:07:19.142248 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:07:44.726788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:08:14.726780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:08:19.151087 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:08:19.151117 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:08:44.726769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:09:14.726791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:09:19.157854 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:09:19.157894 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:09:44.726807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:10:14.726752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:10:19.166452 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:10:19.166488 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:10:44.726910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:11:14.726795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:11:19.173749 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:11:19.173787 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:11:44.727032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:12:14.726802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:12:19.182552 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:12:19.182598 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:12:44.726945 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:13:14.726766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:13:19.197709 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:13:19.197738 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:13:44.726887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:14:14.726819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:14:19.206732 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:14:19.206773 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:14:44.726864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:15:14.726773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:15:19.213533 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:15:19.213565 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:15:44.726871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:16:14.726831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:16:19.222163 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:16:19.222195 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:16:44.726812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:17:14.726970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:17:19.229322 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:17:19.229450 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:17:44.726854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:18:14.726894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:18:19.240863 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:18:19.240890 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:18:44.726842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:19:14.726854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:19:19.248490 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:19:19.248518 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:19:44.726859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:20:14.726907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:20:19.333950 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:20:19.333977 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:20:44.727013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:21:14.726864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:21:19.340234 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:21:19.340275 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:21:44.726803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:22:14.726824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:22:19.350326 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:22:19.350361 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:22:44.726870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:23:14.726943 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:23:19.356671 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:23:19.356707 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:23:44.726885 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:24:14.726821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:24:19.363948 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:24:19.363991 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:24:44.726862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:25:14.726786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:25:19.370056 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:25:19.370081 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:25:44.726789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:26:14.726774 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:26:19.376910 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:26:19.376939 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:26:44.726778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:27:14.726928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:27:19.383143 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:27:19.383173 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:27:44.726892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:28:14.726829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:28:19.392204 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:28:19.392233 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:28:44.726799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:29:14.726863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:29:19.398650 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:29:19.398704 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:29:44.726863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:30:14.726887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:30:19.411784 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:30:19.411821 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:30:44.726839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:31:14.726857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:31:19.418363 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:31:19.418399 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:31:44.726846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:32:14.726933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:32:19.425284 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:32:19.425324 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:32:44.726831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:33:14.726804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:33:19.433572 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:33:19.433629 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:33:44.726824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:34:14.726861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:34:19.442351 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:34:19.442405 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:34:44.726873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:35:14.726843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:35:19.449051 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:35:19.449083 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:35:44.726919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:36:14.726859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:36:19.456622 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:36:19.456658 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:36:44.726762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:37:14.726824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:37:19.463915 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:37:19.463951 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:37:44.726833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:38:14.726774 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:38:19.471868 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:38:19.471912 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:38:44.726905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:39:14.726802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:39:19.478521 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:39:19.478555 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:39:44.726742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:40:14.726882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:40:19.486419 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:40:19.486446 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:40:44.726860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:41:14.726865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:41:19.493565 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:41:19.493603 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:41:44.726774 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:42:14.726862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:42:19.501991 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:42:19.502022 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:42:44.726842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:43:14.726757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:43:19.509048 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:43:19.509106 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:43:44.726961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:44:14.726786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:44:19.518719 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:44:19.518763 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:44:44.726865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:45:14.726892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:45:19.525609 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:45:19.525659 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:45:44.726778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:46:14.726782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:46:19.533734 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:46:19.533768 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:46:44.726878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:47:14.726849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:47:19.541261 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:47:19.541315 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:47:44.726838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:48:14.726846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:48:19.549050 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:48:19.549086 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:48:44.726883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:49:14.726856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:49:19.555633 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:49:19.555661 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:49:44.726910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:50:14.726915 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:50:19.562610 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:50:19.562644 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:50:44.726763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:51:14.726912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:51:19.568851 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:51:19.568884 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:51:44.726772 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:52:14.726849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:52:19.576298 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:52:19.576338 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:52:44.726847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:53:14.726889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:53:19.589650 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:53:19.589681 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:53:44.726778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:54:14.726827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:54:19.599817 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:54:19.599855 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:54:44.726830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:55:14.726861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:55:19.606644 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:55:19.606676 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:55:44.726863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:56:14.726898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:56:19.616489 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:56:19.616521 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:56:44.726921 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:57:14.726851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:57:19.623286 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:57:19.623320 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:57:44.726939 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:58:14.726776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:58:19.631315 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:58:19.631351 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:58:44.726869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:59:14.726852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 05:59:19.638132 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:59:19.638182 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 05:59:44.726871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:00:14.726757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:00:19.646423 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:00:19.646452 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:00:44.726889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:01:14.726815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:01:19.652871 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:01:19.652899 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:01:44.726815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:02:14.726903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:02:19.663140 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:02:19.663182 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:02:44.726870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:03:14.726769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:03:19.669939 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:03:19.669982 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:03:44.726840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:04:14.726826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:04:19.677044 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:04:19.677092 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:04:44.726947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:05:14.726812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:05:19.685754 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:05:19.685800 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:05:44.726814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:06:14.726876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:06:19.693307 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:06:19.693352 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:06:44.726951 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:07:14.726823 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:07:19.700479 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:07:19.700514 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:07:44.726855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:08:14.726896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:08:19.709206 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:08:19.709240 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:08:44.726850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:09:14.726886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:09:19.715713 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:09:19.715762 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:09:44.726889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:10:14.726850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:10:19.722941 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:10:19.722968 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:10:44.726811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:11:14.726843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:11:19.730497 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:11:19.730530 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:11:44.726853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:12:14.726804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:12:19.737022 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:12:19.737053 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:12:44.726854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:13:14.726888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:13:19.744047 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:13:19.744085 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:13:44.726880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:14:14.726871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:14:19.751527 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:14:19.751557 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:14:44.726800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:15:14.726794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:15:19.758497 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:15:19.758557 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:15:44.726812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:16:14.726783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:16:19.767881 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:16:19.767913 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:16:44.726770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:17:14.726795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:17:19.774483 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:17:19.774517 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:17:44.726836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:18:14.726852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:18:19.785069 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:18:19.785122 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:18:44.726827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:19:14.726800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:19:19.792668 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:19:19.792697 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:19:44.726801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:20:14.726826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:20:19.801464 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:20:19.801495 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:20:44.726761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:21:14.726781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:21:19.808584 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:21:19.808620 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:21:44.726856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:22:14.726780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:22:19.816737 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:22:19.816777 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:22:44.726845 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:23:14.726857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:23:19.823442 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:23:19.823498 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:23:44.726820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:24:14.726811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:24:19.832772 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:24:19.832805 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:24:44.726798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:25:14.726799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:25:19.840132 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:25:19.840179 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:25:44.726812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:26:14.726811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:26:19.849538 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:26:19.849570 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:26:44.726854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:27:14.726831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:27:19.857382 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:27:19.857514 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:27:44.726775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:28:14.726833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:28:19.865644 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:28:19.865674 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:28:44.726836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:29:14.726704 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:29:19.872215 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:29:19.872260 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:29:44.726877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:30:14.726785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:30:19.880250 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:30:19.880284 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:30:44.726822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:31:14.726807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:31:19.887120 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:31:19.887158 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:31:44.726813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:32:14.726792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:32:19.896186 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:32:19.896220 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:32:44.726902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:33:14.726779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:33:19.903291 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:33:19.903328 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:33:44.726838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:34:14.726809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:34:19.910137 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:34:19.910167 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:34:44.726833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:35:14.726802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:35:19.917352 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:35:19.917390 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:35:44.726856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:36:14.726825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:36:19.924923 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:36:19.924952 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:36:44.726829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:37:14.726794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:37:19.931419 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:37:19.931477 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:37:44.726796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:38:14.726832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:38:19.939928 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:38:19.939967 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:38:44.726794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:39:14.726791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:39:19.947196 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:39:19.947236 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:39:44.726845 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:40:14.726817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:40:19.956030 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:40:19.956061 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:40:44.726812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:41:14.726814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:41:19.962718 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:41:19.962746 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:41:44.726803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:42:14.726779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:42:19.971490 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:42:19.971526 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:42:44.726815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:43:14.726848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:43:19.978427 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:43:19.978461 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:43:44.726834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:44:14.726836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:44:19.988990 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:44:19.989028 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:44:44.726832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:45:14.726798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:45:19.997451 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:45:19.997487 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:45:44.726851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:46:14.726787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:46:20.008514 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:46:20.008542 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:46:44.726795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:47:14.726883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:47:20.017083 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:47:20.017132 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:47:44.726800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:48:14.726786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:48:20.028928 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:48:20.028962 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:48:44.726757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:49:14.726816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:49:20.035598 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:49:20.035634 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:49:44.726832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:50:14.726827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:50:20.047103 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:50:20.047149 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:50:44.726839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:51:14.726895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:51:20.058809 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:51:20.058851 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:51:44.726827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:52:14.726801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:52:20.073977 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:52:20.074009 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:52:44.726777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:53:14.726759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:53:20.081922 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:53:20.082035 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:53:44.726738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:54:14.726792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:54:20.090338 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:54:20.090371 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:54:44.726836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:55:14.726788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:55:20.097703 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:55:20.097745 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:55:44.726824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:56:14.726830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:56:20.105060 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:56:20.105099 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:56:44.726778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:57:14.726952 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:57:20.113439 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:57:20.113466 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:57:44.726825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:58:14.726760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:58:20.123362 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:58:20.123411 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:58:44.726841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:59:14.726767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 06:59:20.131366 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:59:20.131425 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 06:59:44.726841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:00:14.726766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:00:20.141545 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:00:20.141581 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:00:44.726796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:01:14.726822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:01:20.148039 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:01:20.148069 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:01:44.726822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:02:14.726814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:02:20.155183 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:02:20.155227 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:02:44.726838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:03:14.726806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:03:20.163092 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:03:20.163130 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:03:44.726826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:04:14.726858 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:04:20.174336 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:04:20.174380 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:04:44.726799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:05:14.726851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:05:20.182067 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:05:20.182098 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:05:44.726798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:06:14.726829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:06:20.193824 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:06:20.193862 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:06:44.726835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:07:14.726764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:07:20.201929 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:07:20.201991 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:07:44.726788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:08:14.726788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:08:20.211492 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:08:20.211638 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:08:44.726854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:09:14.726788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:09:20.219491 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:09:20.219521 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:09:44.726814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:10:14.726772 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:10:20.232951 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:10:20.232979 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:10:44.726779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:11:14.726794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:11:20.240698 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:11:20.240739 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:11:44.726816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:12:14.726805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:12:20.251997 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:12:20.252041 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:12:44.726779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:13:14.726787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:13:20.258613 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:13:20.258652 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:13:44.726786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:14:14.726732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:14:20.266270 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:14:20.266311 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:14:44.726780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:15:14.727066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:15:20.274522 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:15:20.274559 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:15:44.726811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:16:14.726805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:16:20.285290 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:16:20.285320 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:16:44.726793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:17:14.726835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:17:20.295217 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:17:20.295257 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:17:44.726856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:18:14.726791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:18:20.303561 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:18:20.303623 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:18:44.726792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:19:14.726760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:19:20.311563 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:19:20.311590 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:19:44.726796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:20:14.726801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:20:20.320488 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:20:20.320525 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:20:44.726853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:21:14.726741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:21:20.327268 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:21:20.327297 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:21:44.726832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:22:14.726904 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:22:20.336724 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:22:20.336757 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:22:44.726767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:23:14.726828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:23:20.344631 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:23:20.344683 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:23:44.726839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:24:14.726794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:24:20.355027 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:24:20.355056 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:24:44.726751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:25:14.726835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:25:20.363675 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:25:20.363723 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:25:44.726812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:26:14.726786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:26:20.373679 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:26:20.373703 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:26:44.726820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:27:14.726819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:27:20.381649 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:27:20.381687 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:27:44.726790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:28:14.726889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:28:20.392280 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:28:20.392311 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:28:44.727012 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:29:14.726817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:29:20.399973 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:29:20.400007 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:29:44.726825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:30:14.726787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:30:20.409518 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:30:20.409556 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:30:44.726821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:31:14.726839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:31:20.417942 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:31:20.417977 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:31:44.726792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:32:14.726800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:32:20.427445 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:32:20.427481 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:32:44.726824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:33:14.726773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:33:20.434444 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:33:20.434495 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:33:44.726819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:34:14.726798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:34:20.444111 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:34:20.444158 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:34:44.726808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:35:14.726888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:35:20.452520 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:35:20.452555 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:35:44.726853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:36:14.726794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:36:20.460909 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:36:20.460942 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:36:44.726845 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:37:14.726864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:37:20.468598 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:37:20.468631 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:37:44.726889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:38:14.726798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:38:20.479012 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:38:20.479047 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:38:44.726788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:39:14.726792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:39:20.486085 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:39:20.486127 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:39:44.726849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:40:14.726779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:40:20.494550 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:40:20.494591 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:40:44.726829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:41:14.726800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:41:20.502688 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:41:20.502725 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:41:44.726843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:42:14.726807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:42:20.512746 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:42:20.512780 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:42:44.727083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:43:14.726870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:43:20.521527 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:43:20.521563 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:43:44.726812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:44:14.726820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:44:20.536557 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:44:20.536591 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:44:44.726828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:45:14.726847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:45:20.544529 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:45:20.544578 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:45:44.726768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:46:14.726817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:46:20.554690 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:46:20.554726 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:46:44.726813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:47:14.726813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:47:20.562589 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:47:20.562622 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:47:44.726835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:48:14.726775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:48:20.573885 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:48:20.573921 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:48:44.726830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:49:14.726822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:49:20.581470 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:49:20.581507 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:49:44.726776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:50:14.726767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:50:20.589861 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:50:20.589985 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:50:44.726786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:51:14.726798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:51:20.596293 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:51:20.596321 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:51:44.726869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:52:14.726878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:52:20.608570 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:52:20.608606 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:52:44.726798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:53:14.726802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:53:20.616692 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:53:20.616737 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:53:44.726802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:54:14.726821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:54:20.627745 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:54:20.627831 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:54:44.726810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:55:14.726795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:55:20.635498 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:55:20.635561 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:55:44.726848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:56:14.726814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:56:20.645919 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:56:20.645953 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:56:44.726790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:57:14.726800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:57:20.652776 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:57:20.652812 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:57:44.726845 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:58:14.726762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:58:20.664576 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:58:20.664627 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:58:44.726830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:59:14.726795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 07:59:20.672654 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:59:20.672682 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 07:59:44.726789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:00:14.726794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:00:20.684141 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:00:20.684179 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:00:44.726798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:01:14.726819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:01:20.691905 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:01:20.691940 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:01:44.726841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:02:14.726784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:02:20.701951 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:02:20.701994 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:02:44.726834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:03:14.726759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:03:20.707965 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:03:20.707998 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:03:44.726799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:04:14.726829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:04:20.716571 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:04:20.716614 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:04:44.726796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:05:14.726811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:05:20.723999 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:05:20.724045 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:05:44.726782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:06:14.726780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:06:20.732220 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:06:20.732256 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:06:44.726824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:07:14.726801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:07:20.745293 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:07:20.745333 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:07:44.726791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:08:14.726794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:08:20.754271 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:08:20.754317 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:08:44.726894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:09:14.727621 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:09:20.760792 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:09:20.760819 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:09:44.726849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:10:14.726856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:10:20.769764 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:10:20.769799 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:10:44.726900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:11:14.726811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:11:20.777066 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:11:20.777099 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:11:44.726818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:12:14.726873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:12:20.786852 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:12:20.786889 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:12:44.727042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:13:14.726863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:13:20.794635 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:13:20.794669 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:13:44.726833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:14:14.726836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:14:20.806106 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:14:20.806134 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:14:44.726815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:15:14.726789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:15:20.814085 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:15:20.814117 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:15:44.726775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:16:14.726798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:16:20.822544 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:16:20.822576 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:16:44.726882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:17:14.726810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:17:20.830382 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:17:20.830409 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:17:44.726900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:18:14.726780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:18:20.844723 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:18:20.844753 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:18:44.726829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:19:14.726780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:19:20.852055 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:19:20.852112 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:19:44.726813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:20:14.726808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:20:20.861542 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:20:20.861576 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:20:44.726908 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:21:14.726788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:21:20.870270 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:21:20.870301 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:21:44.726810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:22:14.726836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:22:20.878888 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:22:20.878965 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:22:44.726869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:23:14.726811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:23:20.885429 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:23:20.885527 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:23:44.726799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:24:14.726767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:24:20.895005 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:24:20.895039 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:24:44.726808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:25:14.726759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:25:20.902220 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:25:20.902267 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:25:44.726941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:26:14.726785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:26:20.911465 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:26:20.911500 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:26:44.726851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:27:14.726808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:27:20.919315 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:27:20.919394 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:27:44.726786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:28:14.726823 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:28:20.927631 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:28:20.927659 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:28:44.726983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:29:14.726748 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:29:20.935221 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:29:20.935264 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:29:44.726900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:30:14.726792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:30:20.944698 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:30:20.944754 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:30:44.726795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:31:14.726824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:31:20.953477 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:31:20.953515 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:31:44.726818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:32:14.726848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:32:20.963993 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:32:20.964026 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:32:44.726791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:33:14.726918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:33:20.971620 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:33:20.971662 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:33:44.726873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:34:14.726827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:34:20.981973 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:34:20.982002 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:34:44.726849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:35:14.726833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:35:20.988284 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:35:20.988315 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:35:44.726827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:36:14.726772 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:36:20.998578 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:36:20.998610 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:36:44.726757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:37:14.726813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:37:21.006391 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:37:21.006584 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:37:44.726833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:38:14.726815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:38:21.016808 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:38:21.016843 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:38:44.726819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:39:14.726848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:39:21.029054 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:39:21.029102 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:39:44.726841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:40:14.726865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:40:21.037066 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:40:21.037106 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:40:44.726835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:41:14.726798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:41:21.044474 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:41:21.044507 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:41:44.726759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:42:14.726828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:42:21.053600 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:42:21.053635 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:42:44.726852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:43:14.726840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:43:21.061199 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:43:21.061228 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:43:44.726776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:44:14.726846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:44:21.070072 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:44:21.070102 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:44:44.726782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:45:14.726840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:45:21.077143 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:45:21.077187 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:45:44.726775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:46:14.726821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:46:21.087888 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:46:21.087936 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:46:44.726868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:47:14.726855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:47:21.096171 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:47:21.096225 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:47:44.726809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:48:14.726792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:48:21.103473 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:48:21.103504 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:48:44.726798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:49:14.726820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:49:21.110037 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:49:21.110067 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:49:44.726844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:50:14.726790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:50:21.119446 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:50:21.119478 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:50:44.726836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:51:14.726878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:51:21.126883 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:51:21.127013 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:51:44.726767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:52:14.726909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:52:21.136478 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:52:21.136545 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:52:44.726802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:53:14.726829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:53:21.144608 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:53:21.144640 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:53:44.726866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:54:14.726817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:54:21.152174 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:54:21.152225 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:54:44.726790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:55:14.726815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:55:21.162257 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:55:21.162293 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:55:44.726773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:56:14.726834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:56:21.170404 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:56:21.170439 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:56:44.726845 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:57:14.726841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:57:21.177303 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:57:21.177337 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:57:44.726828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:58:14.726809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:58:21.185106 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:58:21.185143 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:58:44.726911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:59:14.726757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 08:59:21.192078 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:59:21.192119 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 08:59:44.726834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 09:00:14.726878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 09:00:21.200061 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 09:00:21.200100 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 09:00:44.726758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 09:01:14.726815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 09:01:21.207941 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 09:01:21.207974 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 09:01:44.726842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 09:02:14.726776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 09:02:21.217323 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 09:02:21.217353 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 09:02:44.726775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 09:03:14.726786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 09:03:21.225247 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 09:03:21.225284 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 09:03:44.726831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 09:04:14.726836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 09:04:21.233007 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 09:04:21.233041 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 09:04:44.726834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 09:05:14.726789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 09:05:21.239473 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 09:05:21.239518 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 09:05:44.726842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 09:06:14.726873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 09:06:21.247984 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 09:06:21.248015 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 09:06:44.726875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 09:07:14.726811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 09:07:21.256265 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 09:07:21.256305 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 09:07:44.726818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 09:08:14.726785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 09:08:21.266906 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 09:08:21.266951 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/13 09:08:44.726798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/13 09:09:14.726831 metrics.go:34: INFO No non-zero metrics in the last 30s