Results

          2022/03/27 03:04:50.400008 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/27 03:04:50.400103 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/27 03:04:50.400302 logstash.go:90: INFO Max Retries set to: 3
2022/03/27 03:04:50.400477 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/27 03:04:50.400701 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-k2w8j
2022/03/27 03:04:50.401084 async.go:63: INFO Flush Interval set to: 1s
2022/03/27 03:04:50.401121 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/27 03:04:50.401753 metrics.go:23: INFO Metrics logging every 30s
2022/03/27 03:04:50.401981 beat.go:221: INFO filebeat start running.
2022/03/27 03:04:50.402085 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/27 03:04:50.409467 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/27 03:04:50.409565 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/27 03:04:50.409606 crawler.go:38: INFO Loading Prospectors: 1
2022/03/27 03:04:50.409806 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/27 03:04:50.409839 registrar.go:236: INFO Starting Registrar
2022/03/27 03:04:50.409902 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/27 03:04:50.410380 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/27 03:04:50.409943 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/27 03:04:50.409945 sync.go:41: INFO Start sending events to output
2022/03/27 03:05:00.412481 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/27 03:05:00.412746 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/27 03:05:00.412542 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/27 03:05:00.413090 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/27 03:05:00.413366 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/27 03:05:00.435044 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:05:00.435088 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:05:01.444473 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:05:01.444519 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:05:03.452783 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:05:03.452836 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:05:07.475522 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:05:07.475573 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:05:15.490885 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:05:15.491105 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:05:20.402205 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=64 registrar.writes=1
2022/03/27 03:05:31.517974 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:05:31.518019 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:05:50.402317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:06:03.539880 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:06:03.539932 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:06:20.402106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:06:50.402080 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:07:03.566122 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:07:03.566311 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:07:20.402161 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:07:50.402137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:08:03.585165 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:08:03.585215 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:08:20.402144 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:08:50.402247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:09:03.603080 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:09:03.603137 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:09:20.402145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:09:50.402088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:10:03.625213 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:10:03.625271 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:10:05.429815 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/27 03:10:05.429987 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/27 03:10:05.430073 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/27 03:10:05.430159 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/27 03:10:20.402046 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=4 filebeat.harvester.open_files=-4 filebeat.harvester.running=-4
2022/03/27 03:10:20.429906 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/03/27 03:10:50.402026 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=1 filebeat.harvester.open_files=-1 filebeat.harvester.running=-1
2022/03/27 03:11:03.643246 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:11:03.643294 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:11:20.402100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:11:50.402140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:12:03.661306 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:12:03.661345 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:12:20.402004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:12:50.402041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:13:03.681878 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:13:03.681932 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:13:20.402156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:13:50.402022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:14:03.702133 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:14:03.702180 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:14:20.402027 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:14:50.402085 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:15:03.721002 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:15:03.721055 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:15:20.402086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:15:50.402268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:16:03.745358 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:16:03.745406 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:16:20.402096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:16:50.402062 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:17:03.762623 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:17:03.762670 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:17:20.402114 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:17:50.402129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:18:03.785251 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:18:03.785302 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:18:20.402008 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:18:50.402319 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:19:03.803747 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:19:03.803792 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:19:20.402053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:19:50.402075 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:20:03.821573 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:20:03.821616 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:20:20.402094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:20:50.402126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:21:03.845131 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:21:03.845174 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:21:20.402091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:21:50.403365 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:22:03.864456 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:22:03.864508 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:22:20.402036 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:22:50.402084 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:23:03.887772 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:23:03.887815 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:23:20.401999 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:23:50.402050 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:24:03.907865 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:24:03.907904 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:24:20.402066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:24:50.402234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:25:03.927771 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:25:03.927817 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:25:20.402059 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:25:50.402021 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:26:03.944954 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:26:03.945002 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:26:20.402067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:26:50.402024 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:27:03.965762 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:27:03.965810 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:27:20.402280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:27:50.402116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:28:03.983588 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:28:03.983772 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:28:20.402093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:28:50.407963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:29:04.001495 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:29:04.001546 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:29:20.402056 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:29:50.402004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:30:04.021428 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:30:04.021481 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:30:20.402220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:30:50.402098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:31:04.040361 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:31:04.040674 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:31:20.402063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:31:50.402034 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:32:04.057732 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:32:04.057771 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:32:20.402097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:32:50.402128 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:33:04.076526 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:33:04.076647 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:33:20.402068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:33:50.402068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:34:04.093128 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:34:04.093184 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:34:20.402195 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:34:50.402102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:35:04.111092 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:35:04.111158 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:35:20.402045 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:35:50.402226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:36:04.129592 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:36:04.129631 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:36:20.402082 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:36:50.402087 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:37:04.146986 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:37:04.147028 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:37:20.402083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:37:50.402032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:38:04.165847 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:38:04.166005 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:38:20.402027 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:38:50.402079 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:39:04.184208 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:39:04.184246 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:39:20.402091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:39:50.402140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:40:04.201631 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:40:04.201669 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:40:20.402025 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:40:50.402150 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:41:04.219249 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:41:04.219289 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:41:20.402100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:41:50.402137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:42:04.237418 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:42:04.237487 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:42:20.402050 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:42:50.402028 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:43:04.257991 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:43:04.258031 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:43:20.402105 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:43:50.402036 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:44:04.276691 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:44:04.276741 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:44:20.402080 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:44:50.402082 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:45:04.296229 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:45:04.296284 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:45:20.402033 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:45:50.402210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:46:04.315745 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:46:04.315967 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:46:20.402150 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:46:50.402047 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:47:04.334298 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:47:04.334333 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:47:20.402050 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:47:50.402057 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:48:04.353260 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:48:04.353303 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:48:20.402070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:48:50.402064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:49:04.374466 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:49:04.374515 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:49:20.402080 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:49:50.407597 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:50:04.386226 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:50:04.386260 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:50:20.402093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:50:50.402158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:51:04.393142 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:51:04.393187 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:51:20.402082 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:51:50.402121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:52:04.399831 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:52:04.399881 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:52:20.402025 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:52:50.402096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:53:04.413880 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:53:04.413943 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:53:20.402071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:53:50.404116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:54:04.421061 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:54:04.421108 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:54:20.402029 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:54:50.402177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:55:04.428099 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:55:04.428149 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:55:20.402135 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:55:50.402179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:56:04.434149 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:56:04.434201 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:56:20.402104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:56:50.402086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:57:04.440201 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:57:04.440246 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:57:20.402051 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:57:50.402119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:58:04.446577 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:58:04.446716 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:58:20.402114 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:58:50.401996 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:59:04.455013 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:59:04.455061 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:59:20.402052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:59:50.402160 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:00:04.462193 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:00:04.462247 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:00:20.402082 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:00:50.402121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:01:04.468732 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:01:04.468772 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:01:20.402052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:01:50.402411 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:02:04.478416 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:02:04.478463 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:02:20.402056 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:02:50.402090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:03:04.485062 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:03:04.485093 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:03:20.402240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:03:50.402073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:04:04.493115 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:04:04.493160 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:04:20.402041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:04:50.402020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:05:04.499172 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:05:04.499222 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:05:20.402178 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:05:50.402227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:06:04.508144 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:06:04.508355 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:06:20.402102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:06:50.402091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:07:04.515214 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:07:04.515356 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:07:20.402059 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:07:50.402074 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:08:04.522565 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:08:04.522616 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:08:20.402069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:08:50.403438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:09:04.529855 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:09:04.529892 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:09:20.402248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:09:50.402072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:10:04.537468 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:10:04.537515 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:10:20.402098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:10:50.402125 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:11:04.543406 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:11:04.543435 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:11:20.402073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:11:50.402006 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:12:04.550422 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:12:04.550456 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:12:20.402086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:12:50.402031 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:13:04.558527 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:13:04.558575 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:13:20.402109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:13:50.402197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:14:04.565062 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:14:04.565104 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:14:20.402230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:14:50.402106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:15:04.572417 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:15:04.572450 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:15:20.402131 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:15:50.402071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:16:04.579252 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:16:04.579289 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:16:20.402049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:16:50.402066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:17:04.585486 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:17:04.585521 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:17:20.402037 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:17:50.402137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:18:04.596582 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:18:04.596649 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:18:20.402116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:18:50.407736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:19:04.603345 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:19:04.603386 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:19:20.402141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:19:50.402118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:20:04.608674 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:20:04.608704 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:20:20.402055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:20:50.402092 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:21:04.615514 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:21:04.615560 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:21:20.402072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:21:50.402030 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:22:04.623505 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:22:04.623565 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:22:20.402559 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:22:50.402115 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:23:04.633877 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:23:04.633915 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:23:20.402075 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:23:50.402126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:24:04.639859 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:24:04.639908 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:24:20.402635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:24:50.402076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:25:04.646412 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:25:04.646450 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:25:20.402022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:25:50.402165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:26:04.653315 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:26:04.653364 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:26:20.402024 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:26:50.402063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:27:04.659810 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:27:04.659858 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:27:20.402164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:27:50.402071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:28:04.667546 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:28:04.667588 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:28:20.402057 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:28:50.402256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:29:04.673628 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:29:04.673671 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:29:20.402103 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:29:50.402081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:30:04.678961 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:30:04.678993 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:30:20.402096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:30:50.402043 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:31:04.685764 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:31:04.685815 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:31:20.402128 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:31:50.402056 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:32:04.691613 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:32:04.691643 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:32:20.402111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:32:50.402052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:33:04.698211 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:33:04.698256 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:33:20.402030 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:33:50.402117 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:34:04.704646 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:34:04.704682 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:34:20.402174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:34:50.402062 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:35:04.710497 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:35:04.710811 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:35:20.402078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:35:50.402123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:36:04.718057 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:36:04.718108 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:36:20.402105 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:36:50.402042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:37:04.726399 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:37:04.726435 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:37:20.402088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:37:50.402181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:38:04.732871 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:38:04.732923 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:38:20.402097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:38:50.402122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:39:04.739416 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:39:04.739462 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:39:20.402210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:39:50.402227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:40:04.745591 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:40:04.745624 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:40:20.402035 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:40:50.402023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:41:04.752924 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:41:04.752972 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:41:20.402050 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:41:50.402125 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:42:04.760548 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:42:04.760578 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host