Results

          2022/03/04 03:11:26.663940 beat.go:285: INFO Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs]
2022/03/04 03:11:26.663991 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/04 03:11:26.664054 logstash.go:90: INFO Max Retries set to: 3
2022/03/04 03:11:26.664128 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/04 03:11:26.664297 publish.go:295: INFO Publisher name: onap-portal-app-9c5c78dc6-59rbs
2022/03/04 03:11:26.664575 async.go:63: INFO Flush Interval set to: 1s
2022/03/04 03:11:26.664606 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/04 03:11:26.665640 beat.go:221: INFO filebeat start running.
2022/03/04 03:11:26.665860 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/04 03:11:26.667424 metrics.go:23: INFO Metrics logging every 30s
2022/03/04 03:11:27.432698 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/04 03:11:27.432804 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/04 03:11:27.432893 crawler.go:38: INFO Loading Prospectors: 1
2022/03/04 03:11:27.433004 registrar.go:236: INFO Starting Registrar
2022/03/04 03:11:27.433089 sync.go:41: INFO Start sending events to output
2022/03/04 03:11:27.433210 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/04 03:11:27.433234 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/04 03:11:27.433322 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/04 03:11:27.433350 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/04 03:11:37.434945 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/04 03:11:37.435122 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/04 03:11:37.435192 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/04 03:11:37.435269 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/04 03:11:37.435520 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/04 03:11:42.455677 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:11:42.455717 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:11:43.460088 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:11:43.460133 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:11:45.469391 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:11:45.469435 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:11:49.476914 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:11:49.476956 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:11:56.667840 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=71 registrar.writes=1
2022/03/04 03:11:57.486296 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:11:57.486343 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:12:13.496599 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:12:13.496635 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:12:26.667815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:12:45.507897 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:12:45.507926 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:12:56.667794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:13:26.667774 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:13:45.516105 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:13:45.516145 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:13:56.667960 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:14:26.667920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:14:45.525641 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:14:45.525688 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:14:56.667825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:15:26.667742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:15:45.534838 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:15:45.534878 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:15:56.667838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:16:26.668012 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:16:42.451882 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/04 03:16:45.542258 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:16:45.542305 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:16:56.667971 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/04 03:17:26.667820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:17:45.550192 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:17:45.550237 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:17:56.667870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:18:26.667882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:18:45.560586 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:18:45.560632 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:18:56.667914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:19:26.667782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:19:45.569954 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:19:45.569993 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:19:56.668436 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:20:26.667825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:20:45.578304 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:20:45.578356 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:20:56.667829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:21:26.667826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:21:45.586216 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:21:45.586259 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:21:56.667782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:22:26.667818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:22:45.598777 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:22:45.598824 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:22:56.667886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:23:26.667831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:23:45.611072 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:23:45.611185 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:23:56.667991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:24:26.667951 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:24:45.621774 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:24:45.621867 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:24:56.667743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:25:26.667874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:25:45.631280 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:25:45.631314 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:25:56.667732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:26:26.668083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:26:45.638508 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:26:45.638552 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:26:56.667916 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:27:26.667800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:27:45.648314 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:27:45.648358 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:27:56.667776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:28:26.667795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:28:45.657730 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:28:45.657779 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:28:56.667754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:29:26.667809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:29:45.665720 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:29:45.665761 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:29:56.667893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:30:26.667796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:30:45.673468 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:30:45.673521 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:30:56.667934 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:31:26.667748 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:31:45.685060 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:31:45.685106 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:31:56.667824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:32:26.667887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:32:45.694263 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:32:45.694324 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:32:56.667956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:33:26.667846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:33:45.705607 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:33:45.705654 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:33:56.667816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:34:26.667779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:34:45.713449 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:34:45.713509 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:34:56.667940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:35:26.667889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:35:45.722749 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:35:45.722792 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:35:56.667732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:36:26.667933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:36:45.732805 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:36:45.732844 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:36:56.667725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:37:26.667762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:37:45.741698 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:37:45.741757 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:37:56.667913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:38:26.667816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:38:45.750849 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:38:45.750891 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:38:56.667834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:39:26.667871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:39:45.759766 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:39:45.759810 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:39:56.667850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:40:26.667827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:40:45.770015 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:40:45.770100 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:40:56.667946 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:41:26.667995 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:41:45.778560 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:41:45.778607 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:41:56.667802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:42:26.667870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:42:45.787901 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:42:45.787936 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:42:56.667922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:43:26.667845 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:43:45.797181 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:43:45.797221 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:43:56.667843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:44:26.667941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:44:45.806712 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:44:45.806755 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:44:56.667978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:45:26.667902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:45:45.814398 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:45:45.814733 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:45:56.667865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:46:26.667902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:46:45.823863 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:46:45.823910 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:46:56.667946 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:47:26.667963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:47:45.833459 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:47:45.833504 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:47:56.667910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:48:26.668053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:48:45.841214 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:48:45.841249 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:48:56.667900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:49:26.667823 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:49:45.849510 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:49:45.849578 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:49:56.667817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:50:26.667897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:50:45.859827 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:50:45.859868 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:50:56.667794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:51:26.667794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:51:45.867824 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:51:45.867877 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:51:56.667872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:52:26.667765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:52:45.876948 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:52:45.877006 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:52:56.667766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:53:26.667948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:53:45.887961 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:53:45.888012 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:53:56.667840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:54:26.667829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:54:45.897371 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:54:45.897446 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:54:56.667760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:55:26.667836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:55:45.907425 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:55:45.907458 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:55:56.667978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:56:26.667891 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:56:45.914894 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:56:45.914928 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:56:56.667862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:57:26.667811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:57:45.923951 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:57:45.923997 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:57:56.667865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:58:26.667916 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:58:45.932627 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:58:45.932673 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:58:56.667881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:59:26.668032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 03:59:45.942442 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:59:45.942485 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 03:59:56.667937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:00:26.667896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:00:45.951304 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:00:45.951349 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:00:56.667859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:01:26.667885 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:01:45.961932 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:01:45.961976 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:01:56.667869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:02:26.667750 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:02:45.972820 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:02:45.972865 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:02:56.667911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:03:26.667797 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:03:45.980183 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:03:45.980231 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:03:56.667864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:04:26.667800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:04:45.988753 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:04:45.988809 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:04:56.667826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:05:26.667783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:05:45.998324 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:05:45.998376 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:05:56.667858 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:06:26.667999 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:06:46.008227 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:06:46.008303 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:06:56.667819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:07:26.667899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:07:46.016925 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:07:46.017027 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:07:56.667837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:08:26.667836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:08:46.026867 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:08:46.026898 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:08:56.667908 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:09:26.667811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:09:46.035093 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:09:46.035128 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:09:56.667916 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:10:26.667929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:10:46.043395 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:10:46.043443 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:10:56.667736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:11:26.667835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:11:46.053560 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:11:46.053605 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:11:56.667839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:12:26.667761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:12:46.063441 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:12:46.063488 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:12:56.667886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:13:26.667780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:13:46.073599 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:13:46.073644 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:13:56.667817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:14:26.667897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:14:46.083325 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:14:46.083367 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:14:56.667844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:15:26.667991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:15:46.093142 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:15:46.093207 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:15:56.667828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:16:26.667847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:16:46.103104 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:16:46.103157 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:16:56.667753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:17:26.667858 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:17:46.112177 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:17:46.112226 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:17:56.668038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:18:26.667870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:18:46.121852 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:18:46.121885 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:18:56.667853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:19:26.667828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:19:46.131246 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:19:46.131286 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:19:56.667833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:20:26.667984 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:20:46.140485 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:20:46.140516 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:20:56.667749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:21:26.667781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:21:46.148950 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:21:46.149006 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:21:56.668104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:22:26.667783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:22:46.158980 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:22:46.159031 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:22:56.668018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:23:26.667765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:23:46.171812 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:23:46.171851 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:23:56.667925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:24:26.667835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:24:46.181228 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:24:46.181272 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:24:56.667812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:25:26.667843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:25:46.190918 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:25:46.190957 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:25:56.668027 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:26:26.667822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:26:46.200612 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:26:46.200646 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:26:56.667968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:27:26.667805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:27:46.208430 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:27:46.208494 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:27:56.667819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:28:26.667755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:28:46.217543 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:28:46.217579 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:28:56.667942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:29:26.667739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:29:46.226078 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:29:46.226115 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:29:56.668008 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:30:26.668122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:30:46.234698 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:30:46.234733 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:30:56.667921 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:31:26.667850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:31:46.244364 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:31:46.244414 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:31:56.667950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:32:26.667853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:32:46.253510 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:32:46.253581 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:32:56.667756 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:33:26.667727 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:33:46.263280 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:33:46.263359 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:33:56.668001 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:34:26.667983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:34:46.272024 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:34:46.272083 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:34:56.667781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:35:26.667802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:35:46.281114 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:35:46.281143 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:35:56.667967 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:36:26.667774 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:36:46.289305 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:36:46.289345 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:36:56.667905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:37:26.668012 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:37:46.298738 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:37:46.298782 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:37:56.667930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:38:26.667793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:38:46.309498 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:38:46.309551 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:38:56.667808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:39:26.668019 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:39:46.318221 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:39:46.318346 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:39:56.667981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:40:26.667962 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:40:46.326971 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:40:46.327130 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:40:56.667795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:41:26.667823 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:41:46.335784 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:41:46.335817 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:41:56.668003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:42:26.667842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:42:46.344367 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:42:46.344409 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:42:56.667800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:43:26.667919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:43:46.354398 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:43:46.354447 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:43:56.667878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:44:26.668152 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:44:46.363900 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:44:46.363947 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:44:56.667892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:45:26.667838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:45:46.372524 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:45:46.372556 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:45:56.668227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:46:26.667825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:46:46.381572 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:46:46.381604 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:46:56.667908 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:47:26.667751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:47:46.391769 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:47:46.391819 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:47:56.667976 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:48:26.667794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:48:46.399719 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:48:46.399746 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:48:56.667783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:49:26.667828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:49:46.409538 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:49:46.409600 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:49:56.667898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:50:26.667905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:50:46.420196 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:50:46.420250 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:50:56.667854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:51:26.667849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:51:46.429403 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:51:46.429446 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:51:56.667865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:52:26.668004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:52:46.438676 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:52:46.438716 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:52:56.667866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:53:26.667833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:53:46.447319 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:53:46.447352 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:53:56.667865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:54:26.667841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:54:46.457296 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:54:46.457351 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:54:56.667784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:55:26.667970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:55:46.467104 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:55:46.467154 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:55:56.667790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:56:26.667775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:56:46.476655 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:56:46.476690 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:56:56.667884 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:57:26.667773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:57:46.486729 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:57:46.486778 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:57:56.667853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:58:26.667765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:58:46.496965 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:58:46.497027 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:58:56.667909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:59:26.667890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 04:59:46.506777 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:59:46.506810 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 04:59:56.667808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:00:26.667890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:00:46.515113 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:00:46.515149 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:00:56.667888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:01:26.667935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:01:46.524389 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:01:46.524429 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:01:56.667905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:02:26.667835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:02:46.533259 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:02:46.533296 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:02:56.667913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:03:26.667892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:03:46.543595 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:03:46.543631 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:03:56.667806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:04:26.667790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:04:46.551885 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:04:46.551928 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:04:56.667873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:05:26.667801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:05:46.561518 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:05:46.561554 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:05:56.667758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:06:26.667864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:06:46.570350 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:06:46.570401 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:06:56.667993 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:07:26.667891 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:07:46.581193 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:07:46.581242 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:07:56.667838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:08:26.667720 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:08:46.591929 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:08:46.591975 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:08:56.667874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:09:26.667730 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:09:46.602851 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:09:46.602883 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:09:56.667832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:10:26.667828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:10:46.610311 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:10:46.610356 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:10:56.667936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:11:26.667854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:11:46.619632 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:11:46.619671 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:11:56.667742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:12:26.667830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:12:46.628019 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:12:46.628131 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:12:56.667967 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:13:26.667972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:13:46.637137 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:13:46.637164 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:13:56.667877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:14:26.667921 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:14:46.646629 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:14:46.646687 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:14:56.667877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:15:26.667859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:15:46.656250 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:15:46.656282 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:15:56.667874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:16:26.667800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:16:46.666110 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:16:46.666159 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:16:56.667937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:17:26.667945 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:17:46.675514 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:17:46.675551 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:17:56.667820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:18:26.667916 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:18:46.685462 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:18:46.685496 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:18:56.667842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:19:26.667880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:19:46.695919 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:19:46.695971 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:19:56.667865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:20:26.667903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:20:46.705630 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:20:46.705777 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:20:56.667872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:21:26.667855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:21:46.715497 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:21:46.715529 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:21:56.667710 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:22:26.667955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:22:46.725596 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:22:46.725628 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:22:56.667825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:23:26.667805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:23:46.735057 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:23:46.735087 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:23:56.667864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:24:26.667900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:24:46.744565 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:24:46.744606 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:24:56.667899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:25:26.667852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:25:46.754054 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:25:46.754090 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:25:56.668044 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:26:26.667839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:26:46.763407 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:26:46.763448 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:26:56.667857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:27:26.667800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:27:46.773722 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:27:46.773755 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:27:56.667859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:28:26.667770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:28:46.782188 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:28:46.782228 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:28:56.667808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:29:26.667937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:29:46.791252 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:29:46.791297 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:29:56.667876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:30:26.667835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:30:46.800714 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:30:46.800753 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:30:56.667923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:31:26.667776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:31:46.808521 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:31:46.808558 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:31:56.667883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:32:26.668104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:32:46.818461 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:32:46.818502 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:32:56.667825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:33:26.667781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:33:46.828516 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:33:46.828553 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:33:56.667745 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:34:26.667823 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:34:46.837685 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:34:46.837715 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:34:56.667855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:35:26.667817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:35:46.847395 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:35:46.847436 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:35:56.667810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:36:26.667718 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:36:46.857433 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:36:46.857465 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:36:56.667861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:37:26.667835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:37:46.865634 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:37:46.865766 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:37:56.667801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:38:26.667868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:38:46.875487 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:38:46.875537 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:38:56.667864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:39:26.667847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:39:46.885826 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:39:46.885866 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:39:56.667833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:40:26.667867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:40:46.894718 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:40:46.894766 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:40:56.667856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:41:26.668019 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:41:46.909242 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:41:46.909287 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:41:56.667825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:42:26.667812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:42:46.919422 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:42:46.919487 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:42:56.667995 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:43:26.667831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:43:46.930974 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:43:46.931025 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:43:56.668000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:44:26.667804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:44:46.940397 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:44:46.940428 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:44:56.667852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:45:26.667789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:45:46.950613 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:45:46.950686 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:45:56.667982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:46:26.667794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:46:46.961438 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:46:46.961493 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:46:56.667801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:47:26.667880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:47:46.972565 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:47:46.972606 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:47:56.667903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:48:26.667807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:48:46.983674 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:48:46.983796 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:48:56.667980 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:49:26.668158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:49:46.993800 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:49:46.993848 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:49:56.667862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:50:26.667824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:50:47.002342 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:50:47.002371 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:50:56.667857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:51:26.667898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:51:47.010735 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:51:47.010783 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:51:56.667814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:52:26.667747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:52:47.020904 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:52:47.020949 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:52:56.667816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:53:26.667775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:53:47.030012 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:53:47.030048 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:53:56.667925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:54:26.667824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:54:47.038618 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:54:47.038658 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:54:56.667923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:55:26.667792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:55:47.049248 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:55:47.049302 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:55:56.667811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:56:26.667895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:56:47.058082 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:56:47.058127 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:56:56.667799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:57:26.667810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:57:47.067118 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:57:47.067178 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:57:56.667920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:58:26.667743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:58:47.077044 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:58:47.077093 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:58:56.667926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:59:26.667875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 05:59:47.086561 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:59:47.086620 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 05:59:56.667803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:00:26.667931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:00:47.096827 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:00:47.096875 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:00:56.667807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:01:26.667799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:01:47.105203 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:01:47.105251 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:01:56.667774 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:02:26.667847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:02:47.115602 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:02:47.115650 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:02:56.667952 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:03:26.667889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:03:47.125873 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:03:47.125956 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:03:56.667824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:04:26.667817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:04:47.135288 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:04:47.135343 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:04:56.667857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:05:26.667912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:05:47.146114 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:05:47.146146 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:05:56.667862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:06:26.668250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:06:47.156506 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:06:47.156567 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:06:56.667813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:07:26.667861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:07:47.165707 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:07:47.165737 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:07:56.667868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:08:26.667796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:08:47.176163 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:08:47.176203 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:08:56.667840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:09:26.667836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:09:47.185781 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:09:47.185829 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:09:56.667928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:10:26.667814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:10:47.194328 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:10:47.194368 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:10:56.667844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:11:26.667832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:11:47.203164 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:11:47.203235 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:11:56.667846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:12:26.667767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:12:47.211842 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:12:47.211869 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:12:56.668097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:13:26.667954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:13:47.222159 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:13:47.222205 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:13:56.667921 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:14:26.667832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:14:47.232268 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:14:47.232299 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:14:56.667970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:15:26.667788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:15:47.242152 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:15:47.242185 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:15:56.667892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:16:26.667899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:16:47.250914 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:16:47.250948 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:16:56.667916 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:17:26.668144 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:17:47.260722 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:17:47.260780 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:17:56.667771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:18:26.667904 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:18:47.270743 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:18:47.270778 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:18:56.667764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:19:26.667852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:19:47.280005 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:19:47.280088 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:19:56.667760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:20:26.667797 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:20:47.291388 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:20:47.291427 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:20:56.667839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:21:26.667795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:21:47.301864 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:21:47.301918 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:21:56.667727 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:22:26.667905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:22:47.310235 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:22:47.310278 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:22:56.667813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:23:26.667871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:23:47.318766 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:23:47.318832 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:23:56.667875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:24:26.667761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:24:47.328592 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:24:47.328653 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:24:56.668089 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:25:26.667862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:25:47.339523 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:25:47.339559 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:25:56.667888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:26:26.667713 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:26:47.351369 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:26:47.351441 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:26:56.667854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:27:26.668163 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:27:47.359992 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:27:47.360055 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:27:56.667801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:28:26.667802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:28:47.370233 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:28:47.370280 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:28:56.667979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:29:26.667831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:29:47.381739 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:29:47.381793 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:29:56.667868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:30:26.667835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:30:47.392896 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:30:47.392940 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:30:56.667953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:31:26.667734 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:31:47.401351 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:31:47.401396 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:31:56.667881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:32:26.667917 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:32:47.411455 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:32:47.411505 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:32:56.667963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:33:26.667846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:33:47.421474 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:33:47.421530 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:33:56.667757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:34:26.667773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:34:47.430355 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:34:47.430400 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:34:56.667817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:35:26.668003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:35:47.440439 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:35:47.440486 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:35:56.667839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:36:26.667961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:36:47.449988 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:36:47.450022 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:36:56.667914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:37:26.668009 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:37:47.458856 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:37:47.458902 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:37:56.667816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:38:26.667849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:38:47.468556 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:38:47.468593 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:38:56.667922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:39:26.667905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:39:47.479607 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:39:47.479647 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:39:56.667789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:40:26.667914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:40:47.491353 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:40:47.491402 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:40:56.667833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:41:26.667810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:41:47.499814 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:41:47.499929 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:41:56.667890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:42:26.667804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:42:47.508298 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:42:47.508345 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:42:56.667853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:43:26.667762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:43:47.518464 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:43:47.518497 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:43:56.667806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:44:26.667837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:44:47.527986 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:44:47.528035 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:44:56.667818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:45:26.668002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:45:47.536714 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:45:47.536753 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:45:56.667730 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:46:26.667831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:46:47.546624 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:46:47.546704 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:46:56.667789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:47:26.667934 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:47:47.557534 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:47:47.557582 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:47:56.668068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:48:26.667799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:48:47.566007 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:48:47.566052 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:48:56.668057 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:49:26.667791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:49:47.576808 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:49:47.576844 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:49:56.667900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:50:26.667846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:50:47.587079 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:50:47.587147 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:50:56.667938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:51:26.668012 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:51:47.597390 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:51:47.597443 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:51:56.667897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:52:26.667828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:52:47.605599 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:52:47.605645 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:52:56.667758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:53:26.667739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:53:47.617076 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:53:47.617113 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:53:56.667762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:54:26.667783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:54:47.626388 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:54:47.626419 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:54:56.667809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:55:26.667843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:55:47.634424 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:55:47.634485 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:55:56.667803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:56:26.667799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:56:47.643922 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:56:47.643964 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:56:56.667781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:57:26.667807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:57:47.654670 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:57:47.654700 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:57:56.667749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:58:26.667920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:58:47.667124 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:58:47.667184 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:58:56.668044 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:59:26.667960 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 06:59:47.676223 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:59:47.676273 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 06:59:56.667968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:00:26.667813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:00:47.685866 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:00:47.685902 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:00:56.668072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:01:26.667927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:01:47.695538 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:01:47.695605 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:01:56.667912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:02:26.667757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:02:47.703947 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:02:47.703986 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:02:56.668001 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:03:26.667819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:03:47.714321 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:03:47.714367 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:03:56.667963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:04:26.668020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:04:47.725386 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:04:47.725450 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:04:56.667889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:05:26.667808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:05:47.735439 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:05:47.735494 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:05:56.667786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:06:26.667777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:06:47.745504 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:06:47.745548 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:06:56.667759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:07:26.667918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:07:47.755780 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:07:47.755832 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:07:56.667945 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:08:26.667817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:08:47.766184 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:08:47.766227 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:08:56.667724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:09:26.667737 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:09:47.776744 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:09:47.776775 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:09:56.667986 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:10:26.667954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:10:47.785225 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:10:47.785270 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:10:56.667780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:11:26.667820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:11:47.795367 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:11:47.795427 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:11:56.668146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:12:26.667807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:12:47.806765 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:12:47.806804 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:12:56.668023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:13:26.667824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:13:47.816365 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:13:47.816399 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:13:56.667793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:14:26.667818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:14:47.825085 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:14:47.825142 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:14:56.667792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:15:26.667953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:15:47.835114 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:15:47.835153 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:15:56.668000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:16:26.667899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:16:47.842823 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:16:47.842864 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:16:56.668057 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:17:26.667981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:17:47.854051 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:17:47.854099 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:17:56.667763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:18:26.667897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:18:47.865883 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:18:47.865927 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:18:56.668099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:19:26.667765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:19:47.877421 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:19:47.877456 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:19:56.667955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:20:26.667910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:20:47.887663 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:20:47.887694 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:20:56.667978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:21:26.667875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:21:47.898554 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:21:47.898583 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:21:56.668020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:22:26.667883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:22:47.908182 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:22:47.908213 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:22:56.667925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:23:26.667864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:23:47.916590 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:23:47.916635 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:23:56.667923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:24:26.668444 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:24:47.924614 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:24:47.924647 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:24:56.667983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:25:26.667990 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:25:47.934625 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:25:47.934696 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:25:56.667922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:26:26.667721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:26:47.945506 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:26:47.945556 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:26:56.667942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:27:26.667870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:27:47.955018 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:27:47.955051 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:27:56.667969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:28:26.667843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:28:47.966303 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:28:47.966336 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:28:56.667952 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:29:26.667936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:29:47.976917 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:29:47.976959 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:29:56.668043 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:30:26.667962 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:30:47.986353 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:30:47.986490 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:30:56.668037 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:31:26.667736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:31:47.995153 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:31:47.995195 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:31:56.667949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:32:26.667951 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:32:48.003780 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:32:48.003881 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:32:56.667770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:33:26.667946 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:33:48.011751 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:33:48.011780 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:33:56.667953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:34:26.668032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:34:48.020280 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:34:48.020358 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:34:56.667956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:35:26.667793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:35:48.029591 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:35:48.029626 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:35:56.667963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:36:26.667801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:36:48.039375 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:36:48.039427 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:36:56.667932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:37:26.667908 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:37:48.048193 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:37:48.048242 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:37:56.667831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:38:26.667821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:38:48.056336 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:38:48.056386 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:38:56.667837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:39:26.668054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:39:48.064364 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:39:48.064410 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:39:56.668031 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:40:26.667994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:40:48.074499 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:40:48.074543 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:40:56.667797 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:41:26.667786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:41:48.082688 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:41:48.082725 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:41:56.667812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:42:26.667983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:42:48.090058 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:42:48.090115 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:42:56.668018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:43:26.667769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:43:48.109175 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:43:48.109217 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:43:56.667799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:44:26.667805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:44:48.118649 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:44:48.118683 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:44:56.667797 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:45:26.667794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:45:48.127472 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:45:48.127512 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:45:56.667815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:46:26.667781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:46:48.135636 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:46:48.135677 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:46:56.667968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:47:26.667755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:47:48.144629 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:47:48.144666 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:47:56.667763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:48:26.667988 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:48:48.153532 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:48:48.153579 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:48:56.667848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:49:26.667984 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:49:48.163541 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:49:48.163586 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:49:56.667965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:50:26.667856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:50:48.172108 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:50:48.172159 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:50:56.667758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:51:26.667793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:51:48.180814 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:51:48.180865 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:51:56.667790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:52:26.667769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:52:48.190648 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:52:48.190682 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:52:56.667852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:53:26.667955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:53:48.198547 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:53:48.198610 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:53:56.667988 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:54:26.667828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:54:48.207751 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:54:48.207791 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:54:56.667792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:55:26.667758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:55:48.215215 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:55:48.215265 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:55:56.667769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:56:26.667740 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:56:48.224224 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:56:48.224267 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:56:56.667921 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:57:26.668026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:57:48.234405 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:57:48.234441 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:57:56.668021 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:58:26.667773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:58:48.242984 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:58:48.243035 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:58:56.667753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:59:26.667764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 07:59:48.251953 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:59:48.252001 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 07:59:56.667803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:00:26.667961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:00:48.263171 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:00:48.263220 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:00:56.667977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:01:26.667952 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:01:48.273864 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:01:48.273901 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:01:56.667995 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:02:26.667909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:02:48.284301 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:02:48.284337 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:02:56.668040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:03:26.667949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:03:48.294113 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:03:48.294152 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:03:56.667969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:04:26.667910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:04:48.308849 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:04:48.308888 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:04:56.667957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:05:26.667944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:05:48.316759 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:05:48.316792 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:05:56.667800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:06:26.667998 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:06:48.326562 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:06:48.326611 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:06:56.667952 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:07:26.668040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:07:48.335321 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:07:48.335352 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:07:56.667927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:08:26.667875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:08:48.343131 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:08:48.343171 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:08:56.667837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:09:26.667817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:09:48.351799 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:09:48.351853 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:09:56.667790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:10:26.667867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:10:48.360897 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:10:48.360947 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:10:56.667806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:11:26.667793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:11:48.371038 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:11:48.371085 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:11:56.667784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:12:26.667742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:12:48.381493 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:12:48.381525 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:12:56.667868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:13:26.667800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:13:48.391961 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:13:48.392014 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:13:56.667783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:14:26.667748 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:14:48.408043 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:14:48.408087 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:14:56.667791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:15:26.668105 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:15:48.418455 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:15:48.418496 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:15:56.667774 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:16:26.667775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:16:48.434597 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:16:48.434642 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:16:56.667850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:17:26.667929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:17:48.442433 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:17:48.442465 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:17:56.667848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:18:26.667717 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:18:48.452404 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:18:48.452441 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:18:56.667763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:19:26.667882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:19:48.463015 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:19:48.463086 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:19:56.667879 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:20:26.667767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:20:48.472647 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:20:48.472698 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:20:56.667911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:21:26.667739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:21:48.484225 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:21:48.484282 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:21:56.667813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:22:26.667808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:22:48.493226 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:22:48.493272 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:22:56.667781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:23:26.667794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:23:48.502918 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:23:48.502979 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:23:56.667790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:24:26.667832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:24:48.512641 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:24:48.512691 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:24:56.667802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:25:26.667779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:25:48.521365 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:25:48.521418 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:25:56.667805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:26:26.667803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:26:48.532074 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:26:48.532336 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:26:56.667772 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:27:26.667908 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:27:48.541478 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:27:48.541527 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:27:56.667825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:28:26.667937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:28:48.550356 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:28:48.550392 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:28:56.667777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:29:26.667770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:29:48.559090 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:29:48.559146 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:29:56.667776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:30:26.667782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:30:48.568759 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:30:48.568793 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:30:56.667827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:31:26.667743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:31:48.578565 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:31:48.578592 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:31:56.667911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:32:26.667725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:32:48.588942 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:32:48.589022 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:32:56.667729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:33:26.667794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:33:48.598634 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:33:48.598674 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:33:56.667822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:34:26.667869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:34:48.607933 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:34:48.607980 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:34:56.667847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:35:26.667893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:35:48.616537 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:35:48.616581 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:35:56.667863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:36:26.667817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:36:48.624839 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:36:48.624887 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:36:56.667847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:37:26.667875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:37:48.633418 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:37:48.633468 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:37:56.667860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:38:26.667844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:38:48.640506 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:38:48.640556 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:38:56.667781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:39:26.667877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:39:48.655042 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:39:48.655087 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:39:56.667997 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:40:26.667923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:40:48.676582 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:40:48.676617 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:40:56.668023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:41:26.667988 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:41:48.684845 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:41:48.684877 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:41:56.667907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:42:26.667926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:42:48.696893 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:42:48.696932 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:42:56.667881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:43:26.667884 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:43:48.706096 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:43:48.706130 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:43:56.667811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:44:26.667983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:44:48.715944 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:44:48.715989 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:44:56.667896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:45:26.667961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:45:48.725244 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:45:48.725296 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:45:56.667967 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:46:26.667721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:46:48.734116 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:46:48.734160 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:46:56.667973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:47:26.667956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:47:48.742369 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:47:48.742415 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:47:56.667982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:48:26.667734 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:48:48.750784 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:48:48.750814 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:48:56.667842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:49:26.668076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:49:48.758551 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:49:48.758592 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:49:56.667838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:50:26.667904 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:50:48.771383 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:50:48.771439 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:50:56.667817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:51:26.667773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:51:48.780068 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:51:48.780122 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:51:56.667808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:52:26.667920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:52:48.787914 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:52:48.787961 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:52:56.667827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:53:26.668918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:53:48.796362 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:53:48.796424 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:53:56.667892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:54:26.667799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:54:48.804599 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:54:48.804643 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:54:56.667996 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:55:26.667752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:55:48.815986 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:55:48.816027 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:55:56.667770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:56:26.667790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:56:48.824868 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:56:48.824904 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:56:56.667819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:57:26.667814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:57:48.833528 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:57:48.833573 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:57:56.667830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:58:26.667816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:58:48.844447 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:58:48.844490 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:58:56.667862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:59:26.667843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 08:59:48.853394 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:59:48.853430 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 08:59:56.667737 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:00:26.667791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:00:48.865305 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:00:48.865350 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:00:56.667810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:01:26.667932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:01:48.873581 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:01:48.873626 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:01:56.667801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:02:26.667771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:02:48.882831 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:02:48.882896 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:02:56.667818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:03:26.667762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:03:48.892540 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:03:48.892672 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:03:56.667904 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:04:26.667844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:04:48.907278 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:04:48.907326 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:04:56.667818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:05:26.667856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:05:48.916720 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:05:48.916753 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:05:56.667788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:06:26.667777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:06:48.926283 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:06:48.926325 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:06:56.667782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:07:26.667835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:07:48.949297 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:07:48.949341 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:07:56.667828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:08:26.667792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:08:48.958880 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:08:48.958917 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:08:56.667797 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:09:26.667836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:09:48.975752 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:09:48.975792 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:09:56.667922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:10:26.668051 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:10:48.987309 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:10:48.987363 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:10:56.667853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:11:26.667756 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:11:49.003086 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:11:49.003121 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:11:56.667866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:12:26.667820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:12:49.011874 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:12:49.011914 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:12:56.667875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:13:26.668800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:13:49.020514 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:13:49.020549 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:13:56.667884 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:14:26.667882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:14:49.037481 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:14:49.037528 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:14:56.667842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:15:26.667821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:15:49.057607 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:15:49.057705 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:15:56.667910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:16:26.667809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:16:49.076119 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:16:49.076158 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:16:56.667848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:17:26.667887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:17:49.092606 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:17:49.092755 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:17:56.667920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:18:26.667791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:18:49.106167 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:18:49.106203 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:18:56.667816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:19:26.667960 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:19:49.116292 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:19:49.116336 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:19:56.667913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:20:26.667879 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:20:49.125413 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:20:49.125459 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:20:56.667822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:21:26.667819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:21:49.134936 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:21:49.134980 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:21:56.667883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:22:26.667748 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:22:49.145520 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:22:49.145584 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:22:56.667978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:23:26.667804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:23:49.156832 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:23:49.156959 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:23:56.667769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:24:26.667853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:24:49.172082 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:24:49.172125 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:24:56.667884 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:25:26.667916 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:25:49.181737 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:25:49.181773 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:25:56.667841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:26:26.667742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:26:49.191998 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:26:49.192041 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:26:56.667925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:27:26.667760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:27:49.200630 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:27:49.200664 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:27:56.667867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:28:26.667805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:28:49.209453 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:28:49.209488 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:28:56.667787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:29:26.667855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:29:49.219408 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:29:49.219445 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:29:56.667840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:30:26.667872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:30:49.230674 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:30:49.230710 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:30:56.667836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:31:26.667804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:31:49.241204 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:31:49.241237 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:31:56.667779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:32:26.667813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:32:49.252658 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:32:49.252726 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:32:56.667829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:33:26.667857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:33:49.265549 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:33:49.265590 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:33:56.667913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:34:26.667785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:34:49.274895 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:34:49.274946 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:34:56.667889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:35:26.667766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:35:49.289718 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:35:49.289754 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:35:56.667887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:36:26.667830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:36:49.302174 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:36:49.302224 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:36:56.667874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:37:26.667931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:37:49.312408 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:37:49.312437 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:37:56.667854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:38:26.667891 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:38:49.330305 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:38:49.330345 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:38:56.667867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:39:26.667817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:39:49.334080 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:39:49.334113 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:39:56.667891 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:40:26.667910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:40:49.338503 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:40:49.338545 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:40:56.667759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:41:26.667942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:41:49.342205 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:41:49.342241 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:41:56.667885 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:42:26.667904 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:42:49.346335 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:42:49.346378 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:42:56.667938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:43:26.667988 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:43:49.350089 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:43:49.350146 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:43:56.667815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:44:26.667764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:44:49.354975 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:44:49.355010 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:44:56.667811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:45:26.667852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:45:49.359505 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:45:49.359553 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:45:56.667890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:46:26.667875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:46:49.364146 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:46:49.364184 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:46:56.667931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:47:26.667910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:47:49.369254 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:47:49.369311 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:47:56.667834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:48:26.667873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:48:49.374211 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:48:49.374265 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:48:56.667764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:49:26.667886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:49:49.379357 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:49:49.379409 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:49:56.668063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:50:26.667877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:50:49.383465 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:50:49.383498 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:50:56.667894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:51:26.667914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:51:49.388389 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:51:49.388440 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:51:56.667887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:52:26.667822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:52:49.392835 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:52:49.392883 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:52:56.667812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:53:26.667857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:53:49.398253 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:53:49.398527 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:53:56.667827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:54:26.667775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:54:49.403042 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:54:49.403086 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:54:56.667833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:55:26.667778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:55:49.406960 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:55:49.407008 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:55:56.667859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:56:26.667796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:56:49.412602 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:56:49.412643 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:56:56.667944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:57:26.667788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:57:49.417358 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:57:49.417425 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:57:56.667883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:58:26.667839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:58:49.422107 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:58:49.422163 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:58:56.667835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:59:26.667814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 09:59:49.426749 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:59:49.426802 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 09:59:56.667843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:00:26.667964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:00:49.431142 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:00:49.431179 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:00:56.667692 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:01:26.667873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:01:49.435175 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:01:49.435207 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:01:56.667834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:02:26.667747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:02:49.440180 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:02:49.440228 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:02:56.667826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:03:26.667846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:03:49.445844 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:03:49.445889 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:03:56.667739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:04:26.667750 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:04:49.450029 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:04:49.450087 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:04:56.667887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:05:26.667783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:05:49.454483 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:05:49.454546 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:05:56.668014 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:06:26.667897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:06:49.459388 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:06:49.459459 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:06:56.667798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:07:26.667830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:07:49.463465 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:07:49.463494 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:07:56.668054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:08:26.667800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:08:49.467898 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:08:49.467948 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:08:56.668044 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:09:26.667777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:09:49.472248 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:09:49.472287 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:09:56.667896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:10:26.667884 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:10:49.476235 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:10:49.476297 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:10:56.667964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:11:26.667974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:11:49.480699 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:11:49.480760 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:11:56.667843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:12:26.667788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:12:49.485784 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:12:49.485841 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:12:56.667756 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:13:26.667945 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:13:49.489681 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:13:49.489727 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:13:56.667751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:14:26.667801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:14:49.494495 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:14:49.494531 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:14:56.667893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:15:26.667746 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:15:49.499229 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:15:49.499271 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:15:56.667878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:16:26.667876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:16:49.503327 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:16:49.503375 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:16:56.667807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:17:26.667852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:17:49.508372 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:17:49.508425 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:17:56.667753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:18:26.667961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:18:49.513034 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:18:49.513074 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:18:56.667895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:19:26.667804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:19:49.517252 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:19:49.517278 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:19:56.667879 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:20:26.667889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:20:49.522081 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:20:49.522136 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:20:56.667883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:21:26.667734 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:21:49.526176 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:21:49.526224 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:21:56.667756 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:22:26.667769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:22:49.530054 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:22:49.530201 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:22:56.667789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:23:26.667862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:23:49.534266 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:23:49.534369 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:23:56.667849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:24:26.667822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:24:49.539934 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:24:49.539970 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:24:56.667774 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:25:26.667821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:25:49.544224 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:25:49.544270 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:25:56.667841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:26:26.667858 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:26:49.548050 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:26:49.548090 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:26:56.667848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:27:26.667819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:27:49.552741 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:27:49.552799 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:27:56.667920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:28:26.667827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:28:49.556490 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:28:49.556523 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:28:56.667897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:29:26.667763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:29:49.560571 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:29:49.560613 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:29:56.667837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:30:26.667855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:30:49.565027 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:30:49.565167 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:30:56.667860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:31:26.667809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:31:49.569596 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:31:49.569632 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:31:56.667875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:32:26.667876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:32:49.573567 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:32:49.573609 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:32:56.667766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:33:26.667774 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:33:49.578063 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:33:49.578102 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:33:56.668033 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:34:26.667910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:34:49.582337 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:34:49.582410 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:34:56.667946 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:35:26.669351 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:35:49.586481 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:35:49.586514 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:35:56.667877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:36:26.667879 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:36:49.590064 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:36:49.590103 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:36:56.667918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:37:26.667735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:37:49.594151 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:37:49.594180 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:37:56.667800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:38:26.667807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:38:49.598909 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:38:49.598951 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:38:56.667947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:39:26.668004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:39:49.603486 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:39:49.603549 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:39:56.667827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:40:26.667867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:40:49.609241 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:40:49.609275 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:40:56.667725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:41:26.667788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:41:49.614769 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:41:49.614819 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:41:56.667854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:42:26.667920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:42:49.624683 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:42:49.624721 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:42:56.667824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:43:26.667848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:43:49.629644 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:43:49.629720 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:43:56.667714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:44:26.667792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:44:49.635311 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:44:49.635370 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:44:56.667786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:45:26.667769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:45:49.640466 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:45:49.640500 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:45:56.667940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:46:26.667872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:46:49.645350 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:46:49.645385 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:46:56.667825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:47:26.668062 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/04 10:47:49.651174 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:47:49.651211 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/04 10:47:56.667882 metrics.go:34: INFO No non-zero metrics in the last 30s