Results

          2022/03/24 02:13:56.368224 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/24 02:13:56.368264 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/24 02:13:56.368333 logstash.go:90: INFO Max Retries set to: 3
2022/03/24 02:13:56.368380 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/24 02:13:56.368453 metrics.go:23: INFO Metrics logging every 30s
2022/03/24 02:13:56.368472 publish.go:295: INFO Publisher name: onap-portal-app-9c5c78dc6-t2pc8
2022/03/24 02:13:56.368870 async.go:63: INFO Flush Interval set to: 1s
2022/03/24 02:13:56.368976 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/24 02:13:56.369650 beat.go:221: INFO filebeat start running.
2022/03/24 02:13:56.369691 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/24 02:13:56.653818 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/24 02:13:56.653921 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/24 02:13:56.653998 crawler.go:38: INFO Loading Prospectors: 1
2022/03/24 02:13:56.654065 registrar.go:236: INFO Starting Registrar
2022/03/24 02:13:56.654273 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/24 02:13:56.654312 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/24 02:13:56.654307 sync.go:41: INFO Start sending events to output
2022/03/24 02:13:56.654550 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/24 02:13:56.654613 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/24 02:14:06.655711 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/24 02:14:06.655876 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/24 02:14:06.656054 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/24 02:14:06.656108 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/24 02:14:06.656124 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/24 02:14:11.664155 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:14:11.664181 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:14:12.668857 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:14:12.669018 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:14:14.674075 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:14:14.674360 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:14:18.682469 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:14:18.682494 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:14:26.369010 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=70 registrar.writes=1
2022/03/24 02:14:26.693220 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:14:26.693269 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:14:42.702258 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:14:42.702297 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:14:56.368824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:15:14.711409 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:15:14.711451 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:15:26.369258 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:15:56.369038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:16:14.721480 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:16:14.721530 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:16:26.369028 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:16:56.368909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:17:14.734222 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:17:14.734260 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:17:26.368819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:17:56.369015 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:18:14.742755 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:18:14.742810 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:18:26.368993 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:18:56.369037 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:19:11.667153 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/24 02:19:14.750862 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:19:14.750934 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:19:26.368924 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/24 02:19:56.368883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:20:14.761817 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:20:14.761872 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:20:26.369022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:20:56.369123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:21:14.771386 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:21:14.771445 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:21:26.369135 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:21:56.369020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:22:14.780950 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:22:14.781053 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:22:26.369038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:22:56.369162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:23:14.790177 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:23:14.790218 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:23:26.368910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:23:56.368854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:24:14.800676 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:24:14.800718 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:24:26.368965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:24:56.368784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:25:14.809660 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:25:14.809717 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:25:26.368833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:25:56.368830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:26:14.817524 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:26:14.817560 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:26:26.368897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:26:56.368888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:27:14.826728 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:27:14.826866 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:27:26.368875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:27:56.368922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:28:14.837978 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:28:14.838033 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:28:26.368831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:28:56.368948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:29:14.848595 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:29:14.848661 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:29:26.369011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:29:56.369006 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:30:14.858621 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:30:14.858666 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:30:26.368871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:30:56.369099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:31:14.868921 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:31:14.868963 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:31:26.368945 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:31:56.368884 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:32:14.877714 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:32:14.877743 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:32:26.368767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:32:56.369018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:33:14.886242 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:33:14.886367 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:33:26.369024 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:33:56.368972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:34:14.895802 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:34:14.895838 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:34:26.368952 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:34:56.368960 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:35:14.904697 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:35:14.904740 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:35:26.368881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:35:56.368862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:36:14.913924 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:36:14.913983 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:36:26.369022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:36:56.369183 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:37:14.922958 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:37:14.922993 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:37:26.368929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:37:56.368905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:38:14.931871 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:38:14.931907 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:38:26.368929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:38:56.368981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:39:14.944508 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:39:14.944555 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:39:26.368926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:39:56.368841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:40:14.954035 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:40:14.954083 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:40:26.368895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:40:56.368793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:41:14.962987 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:41:14.963046 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:41:26.368812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:41:56.368747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:42:14.971908 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:42:14.971948 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:42:26.368808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:42:56.368878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:43:14.981534 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:43:14.981583 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:43:26.368912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:43:56.368867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:44:14.991703 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:44:14.991751 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:44:26.368748 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:44:56.368978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:45:15.001648 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:45:15.001696 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:45:26.368910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:45:56.368930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:46:15.011747 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:46:15.011781 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:46:26.368867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:46:56.368875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:47:15.022013 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:47:15.022064 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:47:26.368974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:47:56.368862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:48:15.030933 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:48:15.030964 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:48:26.368835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:48:56.368931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:49:15.041262 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:49:15.041317 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:49:26.368847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:49:56.368957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:50:15.050732 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:50:15.050796 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:50:26.368919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:50:56.368852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:51:15.059803 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:51:15.059863 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:51:26.368788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:51:56.368854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:52:15.070074 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:52:15.070128 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:52:26.368998 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:52:56.369034 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:53:15.079549 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:53:15.079590 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:53:26.368999 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:53:56.369007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:54:15.089011 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:54:15.089041 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:54:26.368833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:54:56.369032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:55:15.098336 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:55:15.098377 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:55:26.368875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:55:56.368861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:56:15.108287 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:56:15.108326 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:56:26.368957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:56:56.368891 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:57:15.116808 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:57:15.116856 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:57:26.369005 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:57:56.368749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:58:15.126723 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:58:15.126771 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:58:26.369020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:58:56.368931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:59:15.135763 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:59:15.135830 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:59:26.368893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:59:56.368808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:00:15.145560 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:00:15.145584 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:00:26.368797 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:00:56.368919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:01:15.155991 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:01:15.156030 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:01:26.368894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:01:56.368867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:02:15.165059 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:02:15.165103 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:02:26.368871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:02:56.368959 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:03:15.173507 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:03:15.173555 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:03:26.369030 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:03:56.369086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:04:15.183138 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:04:15.183162 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:04:26.368789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:04:56.369031 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:05:15.192255 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:05:15.192291 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:05:26.368914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:05:56.368871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:06:15.202470 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:06:15.202636 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:06:26.368942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:06:56.368947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:07:15.212461 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:07:15.212487 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:07:26.368947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:07:56.368910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:08:15.222535 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:08:15.222610 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:08:26.368737 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:08:56.369021 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:09:15.232492 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:09:15.232534 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:09:26.368893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:09:56.368906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:10:15.241540 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:10:15.241578 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:10:26.368981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:10:56.368978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:11:15.250573 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:11:15.250612 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:11:26.368905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:11:56.368911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:12:15.261652 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:12:15.261701 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:12:26.368919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:12:56.369003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:13:15.271339 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:13:15.271485 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:13:26.368933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:13:56.368875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:14:15.282854 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:14:15.283015 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:14:26.368825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:14:56.368978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:15:15.293685 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:15:15.293737 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:15:26.368851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:15:56.368882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:16:15.304791 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:16:15.304848 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:16:26.368954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:16:56.369116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:17:15.315291 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:17:15.315339 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:17:26.368965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:17:56.369049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:18:15.324742 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:18:15.324783 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:18:26.368961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:18:56.368987 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:19:15.334356 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:19:15.334397 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:19:26.368982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:19:56.368824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:20:15.344866 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:20:15.344948 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:20:26.368968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:20:56.368892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:21:15.354746 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:21:15.354793 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:21:26.368818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:21:56.369063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:22:15.364573 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:22:15.364647 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:22:26.368880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:22:56.369030 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:23:15.374660 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:23:15.374692 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:23:26.369025 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:23:56.368864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:24:15.388031 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:24:15.388093 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:24:26.368739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:24:56.369039 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:25:15.398187 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:25:15.398231 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:25:26.368766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:25:56.368880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:26:15.407335 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:26:15.407378 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:26:26.368808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:26:56.368833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:27:15.423325 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:27:15.423385 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:27:26.368897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:27:56.368762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:28:15.433512 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:28:15.433570 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:28:26.368857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:28:56.368937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:29:15.444494 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:29:15.444542 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:29:26.368828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:29:56.368856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:30:15.454209 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:30:15.454243 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:30:26.368926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:30:56.369010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:31:15.464255 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:31:15.464298 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:31:26.368873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:31:56.368743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:32:15.473282 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:32:15.473313 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:32:26.368866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:32:56.368886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:33:15.482496 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:33:15.482535 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:33:26.368909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:33:56.368778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:34:15.492278 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:34:15.492320 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:34:26.368825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:34:56.368960 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:35:15.503279 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:35:15.503322 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:35:26.368906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:35:56.368839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:36:15.512309 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:36:15.512346 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:36:26.368891 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:36:56.368950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:37:15.521801 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:37:15.521843 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:37:26.368949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:37:56.369025 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:38:15.530144 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:38:15.530185 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:38:26.368876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:38:56.369028 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:39:15.539922 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:39:15.539951 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:39:26.368890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:39:56.368938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:40:15.551399 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:15.551444 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:26.369049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:40:56.369003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:41:15.560772 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:41:15.560813 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:41:26.368953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:41:56.368857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:42:15.571239 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:42:15.571280 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:42:26.368949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:42:56.369009 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:43:15.582155 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:43:15.582199 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:43:26.368930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:43:56.368896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:44:15.592738 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:44:15.592782 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:44:26.368901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:44:56.368846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:45:15.602088 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:45:15.602145 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:45:26.368949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:45:56.368849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:46:15.612543 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:46:15.612587 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:46:26.368869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:46:56.368900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:47:15.623706 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:47:15.623758 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:47:26.368962 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:47:56.369053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:48:15.632361 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:48:15.632409 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:48:26.368980 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:48:56.369044 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:49:15.642499 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:49:15.642555 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:49:26.368863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:49:56.368900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:50:15.652903 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:50:15.652941 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:50:26.368934 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:50:56.368969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:51:15.662618 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:51:15.662685 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:51:26.368929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:51:56.368961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:52:15.671571 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:52:15.671620 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:52:26.368827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:52:56.368864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:53:15.681744 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:53:15.681770 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:53:26.368860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:53:56.368861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:54:15.691811 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:54:15.691847 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:54:26.368878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:54:56.368913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:55:15.702220 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:55:15.702270 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:55:26.368952 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:55:56.368931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:56:15.715238 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:56:15.715282 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:56:26.368829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:56:56.368839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:57:15.725259 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:57:15.725303 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:57:26.368815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:57:56.368902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:58:15.734035 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:58:15.734075 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:58:26.368880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:58:56.368746 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:59:15.744751 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:59:15.744785 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:59:26.368867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:59:56.369073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:00:15.754720 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:00:15.754764 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:00:26.368927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:00:56.368937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:01:15.765339 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:01:15.765379 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:01:26.368884 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:01:56.368860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:02:15.775491 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:02:15.775540 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:02:26.368913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:02:56.368888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:03:15.783752 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:03:15.783862 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:03:26.368898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:03:56.368862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:04:15.794677 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:04:15.794740 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:04:26.368945 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:04:56.368958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:05:15.805188 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:05:15.805271 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:05:26.368899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:05:56.368948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:06:15.815026 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:06:15.815077 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:06:26.369099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:06:56.369017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:07:15.824974 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:07:15.825013 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:07:26.368980 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:07:56.368928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:08:15.836850 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:08:15.836895 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:08:26.368971 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:08:56.368881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:09:15.847476 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:09:15.847547 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:09:26.368984 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:09:56.369044 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:10:15.857792 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:10:15.857872 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:10:26.368907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:10:56.369122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:11:15.867561 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:11:15.867597 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:11:26.368855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:11:56.368878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:12:15.878696 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:12:15.878740 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:12:26.369011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:12:56.369273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:13:15.889017 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:13:15.889061 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:13:26.368950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:13:56.368923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:14:15.899009 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:14:15.899057 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:14:26.368900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:14:56.368838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:15:15.908646 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:15:15.908689 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:15:26.368937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:15:56.368847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:16:15.916889 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:16:15.916947 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:16:26.368714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:16:56.368974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:17:15.927052 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:17:15.927114 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:17:26.368936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:17:56.368880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:18:15.936265 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:18:15.936313 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:18:26.368923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:18:56.368953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:19:15.945903 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:19:15.945959 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:19:26.368834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:19:56.368856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:20:15.956082 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:20:15.956121 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:20:26.368840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:20:56.368862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:21:15.965441 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:21:15.965519 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:21:26.368814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:21:56.368898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:22:15.974972 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:22:15.975022 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:22:26.368860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:22:56.368967 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:23:15.983279 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:23:15.983308 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:23:26.368859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:23:56.368913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:24:15.993791 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:24:15.993869 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:24:26.368910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:24:56.368876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:25:16.005582 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:25:16.005629 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:25:26.369067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:25:56.368882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:26:16.015016 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:26:16.015084 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:26:26.368946 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:26:56.368965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:27:16.025553 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:27:16.025595 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:27:26.368913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:27:56.368939 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:28:16.036146 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:28:16.036197 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:28:26.368960 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:28:56.368925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:29:16.046629 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:29:16.046677 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:29:26.368843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:29:56.368832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:30:16.057148 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:30:16.057202 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:30:26.368930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:30:56.368936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:31:16.067814 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:31:16.067864 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:31:26.368974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:31:56.368871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:32:16.078667 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:32:16.078728 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:32:26.368982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:32:56.368933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:33:16.088312 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:33:16.088369 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:33:26.368877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:33:56.368866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:34:16.097214 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:34:16.097301 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:34:26.368918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:34:56.368954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:35:16.107942 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:35:16.108014 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:35:26.368871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:35:56.368948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:36:16.116133 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:36:16.116181 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:36:26.369104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:36:56.368882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:37:16.126297 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:37:16.126343 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:37:26.368943 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:37:56.368987 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:38:16.136727 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:38:16.136766 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:38:26.368903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:38:56.368871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:39:16.145018 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:39:16.145060 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:39:26.368820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:39:56.368812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:40:16.153384 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:40:16.153420 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:40:26.368922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:40:56.368939 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:41:16.163629 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:41:16.163681 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:41:26.368897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:41:56.368972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:42:16.172972 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:42:16.173044 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:42:26.368903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:42:56.368976 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:43:16.182480 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:43:16.182523 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:43:26.368812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:43:56.368922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:44:16.192922 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:44:16.192961 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:44:26.368818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:44:56.368963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:45:16.201497 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:45:16.201549 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:45:26.369005 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:45:56.368722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:46:16.216231 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:46:16.216262 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:46:26.368912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:46:56.368885 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:47:16.224994 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:47:16.225187 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:47:26.368880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:47:56.368878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:48:16.234666 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:48:16.234700 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:48:26.368823 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:48:56.368967 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:49:16.243976 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:49:16.244025 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:49:26.368860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:49:56.369034 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:50:16.253389 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:50:16.253422 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:50:26.368925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:50:56.368892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:51:16.263203 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:51:16.263269 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:51:26.368907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:51:56.368942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:52:16.274129 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:52:16.274180 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:52:26.368835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:52:56.368886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:53:16.282665 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:53:16.282691 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:53:26.368995 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:53:56.368775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:54:16.291740 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:54:16.291797 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:54:26.368902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:54:56.368928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:55:16.301484 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:55:16.301519 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:55:26.368786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:55:56.368854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:56:16.311676 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:56:16.311710 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:56:26.368811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:56:56.368997 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:57:16.322294 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:57:16.322340 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:57:26.369020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:57:56.368802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:58:16.331617 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:58:16.331658 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:58:26.368893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:58:56.368834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:59:16.342527 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:59:16.342576 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:59:26.368947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:59:56.368865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:00:16.353303 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:00:16.353363 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:00:26.368953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:00:56.368896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:01:16.363234 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:01:16.363285 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:01:26.368942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:01:56.368795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:02:16.372635 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:02:16.372690 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:02:26.368975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:02:56.369026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:03:16.383292 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:03:16.383361 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:03:26.369035 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:03:56.368965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:04:16.392541 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:04:16.392653 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:04:26.368808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:04:56.368866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:05:16.402186 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:05:16.402221 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:05:26.368823 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:05:56.368904 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:06:16.411522 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:06:16.411578 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:06:26.368998 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:06:56.368882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:07:16.421181 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:07:16.421234 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:07:26.369003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:07:56.368964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:08:16.429706 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:08:16.429740 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:08:26.368893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:08:56.369016 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:09:16.443305 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:09:16.443341 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:09:26.368943 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:09:56.368884 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:10:16.451284 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:10:16.451315 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:10:26.368819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:10:56.368984 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:11:16.460454 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:11:16.460490 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:11:26.368877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:11:56.368942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:12:16.469076 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:12:16.469120 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:12:26.368993 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:12:56.368943 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:13:16.487152 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:13:16.487297 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:13:26.368933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:13:56.369025 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:14:16.496721 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:14:16.496762 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:14:26.368917 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:14:56.368969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:15:16.506892 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:15:16.506957 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:15:26.368926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:15:56.368960 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:16:16.516547 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:16:16.516620 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:16:26.368864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:16:56.368841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:17:16.526205 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:17:16.526250 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:17:26.368924 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:17:56.368951 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:18:16.536347 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:18:16.536472 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:18:26.368937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:18:56.368910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:19:16.546173 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:19:16.546214 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:19:26.368971 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:19:56.368842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:20:16.555931 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:20:16.555983 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:20:26.369007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:20:56.368936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:21:16.566866 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:21:16.566950 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:21:26.368909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:21:56.368899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:22:16.576763 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:22:16.576830 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:22:26.368895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:22:56.369024 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:23:16.586217 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:23:16.586294 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:23:26.368928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:23:56.369043 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:24:16.597403 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:24:16.597455 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:24:26.368912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:24:56.368949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:25:16.606559 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:25:16.606595 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:25:26.368834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:25:56.368854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:26:16.616075 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:26:16.616110 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:26:26.368909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:26:56.368900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:27:16.624797 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:27:16.624854 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:27:26.368759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:27:56.368862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:28:16.633979 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:28:16.634020 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:28:26.368847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:28:56.369048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:29:16.643933 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:29:16.643957 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:29:26.368798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:29:56.368976 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:30:16.652325 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:30:16.652366 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:30:26.368859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:30:56.369016 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:31:16.661970 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:31:16.662012 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:31:26.368853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:31:56.368854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:32:16.671966 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:32:16.672017 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:32:26.368864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:32:56.369013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:33:16.682273 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:33:16.682319 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:33:26.368979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:33:56.368872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:34:16.691594 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:34:16.691627 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:34:26.369285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:34:56.368933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:35:16.702074 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:35:16.702158 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:35:26.368853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:35:56.368925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:36:16.711831 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:36:16.711906 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:36:26.368893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:36:56.369111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:37:16.722429 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:37:16.722473 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:37:26.368836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:37:56.368807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:38:16.732062 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:38:16.732106 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:38:26.368965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:38:56.368868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:39:16.742124 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:39:16.742177 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:39:26.368893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:39:56.368901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:40:16.753109 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:40:16.753142 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:40:26.368836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:40:56.368885 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:41:16.764177 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:41:16.764218 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:41:26.368931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:41:56.368818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:42:16.774215 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:42:16.774240 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:42:26.368952 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:42:56.368930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:43:16.784727 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:43:16.784770 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:43:26.368940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:43:56.368950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:44:16.794104 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:44:16.794143 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:44:26.368942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:44:56.368816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:45:16.804953 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:45:16.804994 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:45:26.368938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:45:56.368915 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:46:16.814718 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:46:16.814766 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:46:26.368900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:46:56.369229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:47:16.824993 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:47:16.825060 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:47:26.368834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:47:56.368897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:48:16.835401 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:48:16.835467 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:48:26.368771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:48:56.369056 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:49:16.846510 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:49:16.846557 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:49:26.369032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:49:56.368833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:50:16.856135 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:50:16.856200 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:50:26.368887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:50:56.368892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:51:16.865510 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:51:16.865564 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 05:51:26.368887 metrics.go:34: INFO No non-zero metrics in the last 30s