2022/03/17 09:50:04.383447 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/17 09:50:04.383530 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/17 09:50:04.383591 metrics.go:23: INFO Metrics logging every 30s
2022/03/17 09:50:04.383733 logstash.go:90: INFO Max Retries set to: 3
2022/03/17 09:50:04.383835 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/17 09:50:04.383993 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-rpchs
2022/03/17 09:50:04.384348 async.go:63: INFO Flush Interval set to: 1s
2022/03/17 09:50:04.384375 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/17 09:50:04.387492 beat.go:221: INFO filebeat start running.
2022/03/17 09:50:04.387603 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/17 09:50:04.391572 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/17 09:50:04.391622 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/17 09:50:04.391696 crawler.go:38: INFO Loading Prospectors: 1
2022/03/17 09:50:04.391874 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/17 09:50:04.391965 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/17 09:50:04.391985 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/17 09:50:04.392009 registrar.go:236: INFO Starting Registrar
2022/03/17 09:50:04.392033 sync.go:41: INFO Start sending events to output
2022/03/17 09:50:04.392064 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/17 09:50:24.395719 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/17 09:50:24.395907 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/17 09:50:24.396216 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/17 09:50:24.396492 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/17 09:50:24.397149 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/17 09:50:24.424011 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:50:24.424083 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:50:25.498597 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:50:25.498653 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:50:27.531932 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:50:27.531987 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:50:31.557452 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:50:31.557531 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:50:34.385518 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=1 registrar.writes=1
2022/03/17 09:50:39.569406 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:50:39.569444 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:50:55.617597 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:50:55.617658 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:51:04.383974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:51:27.643125 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:51:27.643186 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:51:34.384810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:52:04.384049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:52:27.670697 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:52:27.670942 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:52:34.384136 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:53:04.384320 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:53:27.697703 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:53:27.697770 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:53:34.384228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:54:04.384005 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:54:27.720457 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:54:27.720500 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:54:34.384011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:55:04.384233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:55:27.740688 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:55:27.740857 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:55:29.421587 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/17 09:55:34.383936 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/17 09:56:04.383987 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:56:27.768958 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:56:27.769010 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:56:34.384039 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:57:04.384036 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:57:27.792164 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:57:27.792252 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:57:34.383998 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:58:04.384139 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:58:27.826811 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:58:27.826874 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:58:34.383969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:59:04.384112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 09:59:27.861988 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:59:27.862069 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 09:59:34.384106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:00:04.384299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:00:27.907712 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:00:27.907775 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:00:34.384120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:01:04.383971 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:01:27.946823 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:01:27.946898 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:01:34.384077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:02:04.384028 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:02:27.966565 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:02:27.966632 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:02:34.383986 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:03:04.384028 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:03:27.987824 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:03:27.987882 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:03:34.384035 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:04:04.383975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:04:28.008972 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:04:28.009057 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:04:34.384039 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:05:04.383966 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:05:28.027125 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:05:28.027185 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:05:34.384054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:06:04.383990 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:06:28.048717 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:06:28.048813 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:06:34.384055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:07:04.384022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:07:28.069078 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:07:28.069133 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:07:34.385495 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:08:04.384059 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:08:28.088332 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:08:28.088389 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:08:34.384046 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:09:04.383984 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:09:28.107157 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:09:28.107214 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:09:34.384112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:10:04.393453 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:10:28.126889 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:10:28.126941 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:10:34.383957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:11:04.383938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:11:28.151552 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:11:28.151607 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:11:34.384126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:12:04.384246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:12:28.179640 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:12:28.179718 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:12:34.384005 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:13:04.384839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:13:28.201584 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:13:28.201642 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:13:34.383931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:14:04.384038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:14:28.222597 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:14:28.222659 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:14:34.383954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:15:04.384052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:15:28.243798 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:15:28.243872 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:15:34.383977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:16:04.384005 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:16:28.262172 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:16:28.262215 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:16:34.383998 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:17:04.384208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:17:28.290513 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:17:28.290569 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:17:34.383971 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:18:04.384060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:18:28.313629 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:18:28.313679 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:18:34.383912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:19:04.383977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:19:28.333671 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:19:28.333736 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:19:34.384049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:20:04.383998 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:20:28.356483 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:20:28.356542 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:20:34.383901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:21:04.384071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:21:28.377812 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:21:28.377961 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:21:34.384144 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:22:04.384001 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:22:28.398335 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:22:28.398407 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:22:34.383951 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:23:04.384060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:23:28.416630 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:23:28.416719 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:23:34.384192 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:24:04.384140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:24:28.440278 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:24:28.440336 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:24:34.384023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:25:04.384010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:25:28.465918 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:25:28.465992 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:25:34.384031 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:26:04.384017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:26:28.489741 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:26:28.489822 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:26:34.383981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:27:04.384013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:27:28.509534 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:27:28.509593 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:27:34.383967 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:28:04.383972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:28:28.543645 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:28:28.543709 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:28:34.383956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:29:04.384025 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:29:28.563981 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:29:28.564110 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:29:34.384062 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:30:04.383922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:30:28.585786 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:30:28.585859 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:30:34.384008 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:31:04.383980 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:31:28.607180 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:31:28.607438 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:31:34.384142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:32:04.384012 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:32:28.628700 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:32:28.628744 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:32:34.384021 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:33:04.383950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:33:28.651153 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:33:28.651197 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:33:34.383900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:34:04.383968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:34:28.669366 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:34:28.669420 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:34:34.383938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:35:04.384164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:35:28.689293 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:35:28.689364 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:35:34.383921 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:36:04.384032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:36:28.710354 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:36:28.710402 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:36:34.383950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:37:04.384002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:37:28.745508 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:37:28.745555 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:37:34.384024 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:38:04.384014 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:38:28.769107 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:38:28.769161 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:38:34.384071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:39:04.384064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:39:28.790720 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:39:28.790781 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:39:34.383972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:40:04.384021 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:40:28.799815 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:40:28.800065 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:40:34.384024 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:41:04.384026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:41:28.832229 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:41:28.832295 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:41:34.383992 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:42:04.383913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:42:28.858214 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:42:28.858392 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:42:34.383977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:43:04.384120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:43:28.875595 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:43:28.875658 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:43:34.384092 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:44:04.384001 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:44:28.898135 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:44:28.898218 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:44:34.383968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:45:04.384382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:45:28.927567 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:45:28.927623 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:45:34.384029 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:46:04.384081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:46:28.946580 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:46:28.946623 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:46:34.384078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:47:04.384039 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:47:28.965744 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:47:28.965814 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:47:34.384023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:48:04.383998 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:48:28.985809 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:48:28.985954 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:48:34.384008 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:49:04.384139 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:49:29.004353 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:49:29.004409 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:49:34.384149 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:50:04.384090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:50:29.025629 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:50:29.025692 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:50:34.383962 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:51:04.383963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:51:29.046210 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:51:29.046289 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:51:34.384138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:52:04.384215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:52:29.065824 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:52:29.065902 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:52:34.384004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:53:04.384056 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:53:29.089645 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:53:29.089688 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:53:34.383997 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:54:04.383963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:54:29.113776 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:54:29.113846 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:54:34.384083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:55:04.384066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:55:29.142850 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:55:29.142915 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:55:34.383974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:56:04.384649 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:56:29.163061 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:56:29.163118 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:56:34.384002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:57:04.384060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:57:29.185530 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:57:29.185593 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:57:34.384706 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:58:04.383991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:58:29.204522 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:58:29.204573 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:58:34.384626 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:59:04.384107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 10:59:29.222255 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:59:29.222333 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 10:59:34.384013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:00:04.384011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:00:29.243253 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:00:29.243459 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:00:34.384167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:01:04.383992 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:01:29.268448 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:01:29.268605 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:01:34.383958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:02:04.383969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:02:29.289592 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:02:29.289653 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:02:34.383966 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:03:04.383969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:03:29.309711 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:03:29.309765 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:03:34.384037 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:04:04.383985 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:04:29.329486 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:04:29.329545 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:04:34.386321 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:05:04.384104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:05:29.348871 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:05:29.348963 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:05:34.384036 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:06:04.385488 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:06:29.378498 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:06:29.378543 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:06:34.384123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:07:04.383965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:07:29.400745 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:07:29.400816 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:07:34.383985 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:08:04.383977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:08:29.421638 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:08:29.421702 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:08:34.384018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:09:04.383954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:09:29.443533 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:09:29.444012 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:09:34.384004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:10:04.384029 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:10:29.465590 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:10:29.465638 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:10:34.383974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:11:04.388895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:11:29.490146 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:11:29.490208 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:11:34.384323 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:12:04.383979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:12:29.512625 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:12:29.512689 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:12:34.385318 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:13:04.384116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:13:29.532628 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:13:29.532690 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:13:34.383966 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:14:04.383978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:14:29.557186 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:14:29.557323 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:14:34.384036 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:15:04.383997 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:15:29.581716 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:15:29.581779 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:15:34.384275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:16:04.383985 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:16:29.602323 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:16:29.602405 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:16:34.384255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:17:04.384007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:17:29.625073 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:17:29.625137 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:17:34.384026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:18:04.384084 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:18:29.646154 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:18:29.646206 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/17 11:18:34.384020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/17 11:19:04.383989 metrics.go:34: INFO No non-zero metrics in the last 30s