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