By type
2022/03/24 02:13:22.427222 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:22.427301 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/24 02:13:22.427385 logstash.go:90: INFO Max Retries set to: 3
2022/03/24 02:13:22.427453 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/24 02:13:22.427489 metrics.go:23: INFO Metrics logging every 30s
2022/03/24 02:13:22.427592 publish.go:295: INFO Publisher name: onap-portal-sdk-856bc9b5d4-4w752
2022/03/24 02:13:22.427771 async.go:63: INFO Flush Interval set to: 1s
2022/03/24 02:13:22.427790 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/24 02:13:22.428228 beat.go:221: INFO filebeat start running.
2022/03/24 02:13:22.428291 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/24 02:13:22.805690 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/24 02:13:22.805777 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/24 02:13:22.805827 crawler.go:38: INFO Loading Prospectors: 1
2022/03/24 02:13:22.805993 registrar.go:236: INFO Starting Registrar
2022/03/24 02:13:22.806080 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/24 02:13:22.806097 sync.go:41: INFO Start sending events to output
2022/03/24 02:13:22.806158 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/24 02:13:22.806245 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/24 02:13:22.806309 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/24 02:13:52.427871 metrics.go:39: INFO Non-zero metrics in the last 30s: registrar.writes=1
2022/03/24 02:14:02.809069 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/24 02:14:02.809198 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/24 02:14:02.809229 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/24 02:14:02.809242 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/24 02:14:02.809372 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/24 02:14:02.818396 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:02.818431 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:03.823526 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:03.823676 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:05.828713 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:05.828834 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:09.844876 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:09.844937 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:17.854636 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:17.854661 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:22.428126 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=28
2022/03/24 02:14:33.864056 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:33.864096 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:52.427880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:15:05.873263 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:05.873295 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:22.428023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:15:52.428016 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:16:05.884987 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:05.885033 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:22.428066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:16:52.427910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:17:05.897766 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:05.897840 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:22.427874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:17:52.427912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:18:05.909272 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:05.909316 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:22.427916 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:18:52.427927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:19:05.919544 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:05.919691 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:07.821449 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/24 02:19:22.427948 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/24 02:19:22.822304 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/24 02:19:22.822362 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/24 02:19:22.822402 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/24 02:19:52.427862 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-3
2022/03/24 02:20:05.929285 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:05.929317 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:22.427938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:20:52.427861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:21:05.939605 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:05.939636 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:22.427838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:21:52.427968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:22:05.949485 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:05.949567 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:22.427954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:22:52.427844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:23:05.960107 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:05.960135 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:22.427966 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:23:52.428032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:24:05.969259 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:05.969298 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:22.427919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:24:52.427976 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:25:05.979356 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:05.979404 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:22.427870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:25:52.427978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:26:05.988380 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:05.988436 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:22.427931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:26:52.427855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:27:05.998921 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:05.998978 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:22.428135 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:27:52.430449 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:28:06.011631 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:06.011692 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:22.428126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:28:52.427873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:29:06.020668 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:06.020717 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:22.427941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:29:52.427946 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:30:06.031809 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:06.031847 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:22.427915 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:30:52.427900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:31:06.042484 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:06.042520 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:22.427850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:31:52.427842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:32:06.053553 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:06.053593 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:22.427950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:32:52.427979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:33:06.064040 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:06.064083 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:22.427831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:33:52.427953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:34:06.073266 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:06.073297 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:22.427853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:34:52.427954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:35:06.083152 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:06.083182 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:22.427945 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:35:52.427978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:36:06.092877 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:06.092931 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:22.427826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:36:52.427889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:37:06.101901 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:06.101933 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:22.427812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:37:52.427826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:38:06.111725 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:06.111779 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:22.427994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:38:52.428047 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:39:06.121636 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:06.121670 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:22.427836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:39:52.428012 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:40:06.131639 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:06.131679 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:22.427926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:40:52.427835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:41:06.141825 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:06.141872 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:22.427848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:41:52.427995 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:42:06.151281 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:06.151310 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:22.427934 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:42:52.428005 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:43:06.162338 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:06.162372 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:22.427900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:43:52.427923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:44:06.170073 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:06.170118 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:22.427950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:44:52.428011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:45:06.178253 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:06.178310 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:22.427865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:45:52.427926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:46:06.188864 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:06.188908 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:22.427968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:46:52.427969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:47:06.197833 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:06.197890 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:22.427880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:47:52.427887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:48:06.206823 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:06.206872 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:22.427989 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:48:52.427899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:49:06.215849 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:06.215892 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:22.427961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:49:52.428003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:50:06.225069 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:06.225103 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:22.427822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:50:52.427936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:51:06.243336 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:06.243375 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:22.427878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:51:52.427771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:52:06.250514 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:06.250587 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:22.427902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:52:52.427907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:53:06.261597 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:06.261642 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:22.427855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:53:52.427947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:54:06.269005 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:06.269050 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:22.427796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:54:52.427872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:55:06.278380 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:06.278497 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:22.427880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:55:52.427966 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:56:06.288525 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:06.288577 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:22.427924 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:56:52.428014 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:57:06.298884 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:06.298948 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:22.427911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:57:52.427914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:58:06.308386 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:06.308414 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:22.427948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:58:52.427916 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:59:06.317182 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:06.317229 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:22.428102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 02:59:52.427895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:00:06.325732 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:06.325923 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:22.427935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:00:52.427893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:01:06.336040 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:06.336085 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:22.427843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:01:52.427911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:02:06.345737 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:06.345773 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:22.428076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:02:52.427921 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:03:06.356547 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:06.356585 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:22.427894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:03:52.427943 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:04:06.367381 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:06.367429 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:22.427940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:04:52.427950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:05:06.376751 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:06.376820 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:22.427795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:05:52.427892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:06:06.387388 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:06.387431 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:22.427843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:06:52.427947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:07:06.400617 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:06.400654 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:22.427926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:07:52.427944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:08:06.409640 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:06.409673 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:22.427947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:08:52.427869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:09:06.421603 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:06.421660 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:22.427991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:09:52.427839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:10:06.430066 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:06.430100 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:22.427879 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:10:52.427896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:11:06.439712 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:06.439741 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:22.427861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:11:52.427977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:12:06.449389 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:06.449439 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:22.427829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:12:52.427814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:13:06.461953 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:06.461983 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:22.427957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:13:52.427950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:14:06.471875 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:06.471919 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:22.427877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:14:52.427997 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:15:06.485501 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:06.485530 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:22.427901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:15:52.427943 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:16:06.494714 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:06.494755 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:22.427845 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:16:52.427955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:17:06.505193 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:06.505352 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:22.427857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:17:52.427954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:18:06.513662 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:06.513704 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:22.427896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:18:52.427981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:19:06.527125 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:06.527169 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:22.427860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:19:52.428003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:20:06.537556 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:06.537604 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:22.427952 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:20:52.427819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:21:06.553236 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:06.553273 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:22.427880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:21:52.427903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:22:06.565586 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:06.565631 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:22.427936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:22:52.427920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:23:06.575443 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:06.575487 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:22.428011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:23:52.427929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:24:06.583959 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:06.583991 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:22.427928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:24:52.427854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:25:06.593818 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:06.593859 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:22.427960 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:25:52.427958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:26:06.603574 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:06.603621 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:22.427819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:26:52.427833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:27:06.613830 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:06.613884 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:22.427922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:27:52.428022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:28:06.623569 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:06.623616 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:22.427953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:28:52.427818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:29:06.633661 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:06.633718 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:22.427969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:29:52.427942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:30:06.644370 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:06.644410 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:22.427856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:30:52.427880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:31:06.656987 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:06.657035 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:22.427860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:31:52.427952 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:32:06.666748 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:06.666800 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:22.427895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:32:52.427979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:33:06.677414 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:06.677497 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:22.427901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:33:52.427872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:34:06.688489 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:06.688537 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:22.427863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:34:52.427897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:35:06.699177 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:06.699248 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:22.427968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:35:52.428015 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:36:06.707889 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:06.707927 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:22.427990 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:36:52.427991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:37:06.719283 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:06.719311 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:22.427918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:37:52.427916 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:38:06.728236 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:06.728296 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:22.428084 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:38:52.427891 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:39:06.738726 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:06.738763 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:22.427881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:39:52.427928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:40:06.749757 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:06.749804 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:22.427854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:40:52.427939 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:41:06.759278 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:06.759321 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:22.427971 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:41:52.427991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:42:06.768600 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:06.768659 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:22.427934 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:42:52.427975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:43:06.779699 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:06.779748 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:22.427910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:43:52.427929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:44:06.790145 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:06.790190 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:22.427950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:44:52.427918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:45:06.800852 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:06.800893 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:22.428049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:45:52.427883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:46:06.811715 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:06.811756 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:22.427804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:46:52.427826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:47:06.822213 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:06.822286 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:22.427964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:47:52.427933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:48:06.831905 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:06.831947 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:22.427761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:48:52.427859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:49:06.845236 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:06.845277 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:22.427849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:49:52.427868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:50:06.854803 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:06.854849 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:22.427871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:50:52.427950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:51:06.864481 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:06.864515 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:22.427829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:51:52.427829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:52:06.873706 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:06.873753 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:22.427993 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:52:52.427870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:53:06.883568 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:06.883605 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:22.427849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:53:52.427954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:54:06.892922 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:06.892989 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:22.427874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:54:52.427798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:55:06.903946 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:06.903994 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:22.427900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:55:52.427930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:56:06.913175 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:06.913200 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:22.427861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:56:52.427999 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:57:06.922004 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:06.922046 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:22.427918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:57:52.432876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:58:06.932412 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:06.932459 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:22.427906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:58:52.427989 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:59:06.941631 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:06.941681 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:22.427886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:59:52.427935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:00:06.954417 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:06.954462 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:22.427794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:00:52.427976 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:01:06.965670 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:06.965702 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:22.427855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:01:52.427998 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:02:06.977934 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:06.977965 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:22.428049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:02:52.427860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:03:06.990708 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:06.990740 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:22.427850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:03:52.427953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:04:07.000517 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:07.000585 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:22.428035 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:04:52.427885 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:05:07.011647 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:07.011706 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:22.427957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:05:52.427896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:06:07.021371 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:07.021410 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:22.427800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:06:52.427942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:07:07.035264 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:07.035292 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:22.427912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:07:52.427813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:08:07.045447 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:07.045497 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:22.427984 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:08:52.430450 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:09:07.057429 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:07.057468 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:22.427939 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:09:52.427902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:10:07.067194 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:07.067238 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:22.428072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:10:52.427968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:11:07.077197 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:07.077245 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:22.427958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:11:52.427982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:12:07.086404 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:07.086450 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:22.427987 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:12:52.427924 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:13:07.097349 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:07.097391 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:22.427913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:13:52.427936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:14:07.109520 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:07.109579 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:22.427926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:14:52.427975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:15:07.118841 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:07.118883 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:22.427839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:15:52.427937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:16:07.126665 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:07.126712 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:22.427923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:16:52.427974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:17:07.136994 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:07.137023 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:22.427941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:17:52.427890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:18:07.147684 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:07.147717 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:22.427869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:18:52.427880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:19:07.159364 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:07.159399 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:22.427857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:19:52.427900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:20:07.203570 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:07.203615 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:22.427970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:20:52.427857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:21:07.213626 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:07.213652 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:22.427844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:21:52.427894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:22:07.224617 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:07.224657 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:22.427961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:22:52.427847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:23:07.234490 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:07.234531 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:22.427953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:23:52.427875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:24:07.245439 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:07.245483 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:22.427957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:24:52.427914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:25:07.257799 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:07.257840 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:22.427956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:25:52.427899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:26:07.266835 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:07.266866 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:22.427905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:26:52.427816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:27:07.277869 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:07.277907 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:22.427925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:27:52.427929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:28:07.289973 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:07.289999 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:22.427966 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:28:52.427921 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:29:07.301334 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:07.301480 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:22.427869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:29:52.427923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:30:07.312111 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:07.312143 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:22.427889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:30:52.427883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:31:07.322452 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:07.322499 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:22.427905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:31:52.427917 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:32:07.340531 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:07.340589 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:22.427953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:32:52.427971 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:33:07.352196 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:07.352332 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:22.427932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:33:52.427943 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:34:07.363643 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:07.363685 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:22.427936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:34:52.427896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:35:07.374997 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:07.375056 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:22.427888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:35:52.427825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:36:07.386170 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:07.386216 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:22.427948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:36:52.427888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:37:07.397503 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:07.397540 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:22.427844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:37:52.427911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:38:07.407637 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:07.407682 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:22.427960 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:38:52.427895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:39:07.418462 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:07.418503 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:22.427974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:39:52.427966 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:40:07.429697 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:07.429736 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:22.427887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:40:52.427906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:41:07.440114 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:07.440159 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:22.428102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:41:52.427952 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:42:07.450863 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:07.450901 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:22.427907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:42:52.427944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:43:07.462321 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:07.462369 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:22.427941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:43:52.427912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:44:07.472351 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:07.472382 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:22.427877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:44:52.427938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:45:07.481590 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:07.481627 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:22.427937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:45:52.427997 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:46:07.492571 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:07.492610 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:22.427876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:46:52.427787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:47:07.505678 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:07.505715 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:22.427774 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:47:52.427972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:48:07.517282 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:07.517337 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:22.428079 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:48:52.427923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:49:07.527709 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:07.527748 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:22.427919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:49:52.427930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:50:07.538703 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:07.538744 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:22.427917 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:50:52.428068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:51:07.549359 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:07.549401 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:22.427887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:51:52.427985 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:52:07.561634 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:07.561680 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:22.427861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:52:52.427831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:53:07.573249 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:07.573288 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:22.427859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:53:52.427901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:54:07.582645 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:07.582702 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:22.427860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:54:52.427834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:55:07.592837 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:07.592886 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:22.427935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:55:52.427796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:56:07.603727 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:07.603770 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:22.427983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:56:52.428004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:57:07.613403 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:07.613475 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:22.427798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:57:52.427853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:58:07.622062 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:07.622117 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:22.427822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:58:52.427788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:59:07.631975 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:07.632027 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:22.427973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:59:52.427896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:00:07.650055 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:07.650089 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:22.427942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:00:52.427991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:01:07.661072 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:07.661112 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:22.427919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:01:52.427876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:02:07.671683 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:07.671721 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:22.427919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:02:52.427807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:03:07.682679 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:07.682709 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:22.427908 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:03:52.427913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:04:07.692907 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:07.692953 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:22.427864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:04:52.427915 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:05:07.704563 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:07.704616 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:22.427804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:05:52.427988 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:06:07.713806 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:07.713841 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:22.427983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:06:52.427931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:07:07.725236 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:07.725275 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:22.427943 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:07:52.427948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:08:07.735306 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:07.735338 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:22.427907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:08:52.427892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:09:07.747112 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:07.747152 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:22.427989 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:09:52.427931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:10:07.757898 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:07.757936 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:22.428002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:10:52.428000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:11:07.769384 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:07.769417 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:22.427888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:11:52.427952 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:12:07.779632 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:07.779664 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:22.427848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:12:52.427949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:13:07.791911 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:07.791960 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:22.427822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:13:52.427863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:14:07.800592 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:07.800616 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:22.427969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:14:52.427825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:15:07.810831 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:07.810870 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:22.427973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:15:52.427947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:16:07.821252 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:07.821286 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:22.427917 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:16:52.427856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:17:07.832833 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:07.832884 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:22.427822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:17:52.427857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:18:07.844318 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:07.844351 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:22.427780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:18:52.427969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:19:07.856279 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:07.856349 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:22.427881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:19:52.427804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:20:07.868065 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:07.868112 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:22.427999 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:20:52.427899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:21:07.878430 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:07.878475 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:22.427938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:21:52.427875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:22:07.889833 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:07.889887 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:22.427870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:22:52.427913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:23:07.900009 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:07.900077 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:22.427946 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:23:52.427928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:24:07.909638 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:07.909719 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:22.427841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:24:52.427877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:25:07.920949 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:07.920993 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:22.427922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:25:52.427963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:26:07.930302 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:07.930352 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:22.427977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:26:52.427953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:27:07.940934 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:07.940973 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:22.427909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:27:52.427883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:28:07.952207 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:07.952260 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:22.428011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:28:52.427925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:29:07.965290 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:07.965400 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:22.427878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:29:52.428032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:30:07.974119 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:07.974164 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:22.427930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:30:52.427909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:31:07.985774 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:07.985811 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:22.427822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:31:52.427862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:32:07.994895 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:07.994934 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:22.427938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:32:52.427832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:33:08.005386 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:08.005436 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:22.427945 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:33:52.427989 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:34:08.016080 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:08.016118 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:22.427926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:34:52.427907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:35:08.027099 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:08.027132 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:22.427966 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:35:52.427965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:36:08.038732 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:08.038789 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:22.427929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:36:52.427920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:37:08.048422 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:08.048458 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:22.427926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:37:52.427895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:38:08.059767 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:08.059836 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:22.427934 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:38:52.427862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:39:08.071324 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:08.071364 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:22.427993 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:39:52.427915 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:40:08.081228 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:08.081319 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:22.427902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:40:52.427820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:41:08.090371 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:08.090400 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:22.427853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:41:52.427824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:42:08.100997 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:08.101040 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:22.427932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:42:52.427940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:43:08.110943 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:08.110982 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:22.427846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:43:52.427843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:44:08.162152 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:08.162194 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:22.427844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:44:52.427913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:45:08.173050 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:08.173086 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:22.427878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:45:52.427867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:46:08.181307 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:08.181351 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:22.427787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:46:52.427908 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:47:08.191528 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:08.191582 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:22.427890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:47:52.427991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:48:08.200923 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:08.200956 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:22.427940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:48:52.427934 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:49:08.211067 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:08.211110 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:22.427976 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:49:52.427888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:50:08.221769 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:08.221821 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:22.427912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:50:52.427935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 05:51:08.233296 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:08.233323 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:22.427853 metrics.go:34: INFO No non-zero metrics in the last 30s