Results

          2022/03/09 03:04:53.537534 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/09 03:04:53.537601 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/09 03:04:53.537723 logstash.go:90: INFO Max Retries set to: 3
2022/03/09 03:04:53.537842 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/09 03:04:53.538002 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-2ljj9
2022/03/09 03:04:53.538294 async.go:63: INFO Flush Interval set to: 1s
2022/03/09 03:04:53.538322 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/09 03:04:53.539012 beat.go:221: INFO filebeat start running.
2022/03/09 03:04:53.539122 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/09 03:04:53.541287 metrics.go:23: INFO Metrics logging every 30s
2022/03/09 03:04:53.542528 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/09 03:04:53.542616 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/09 03:04:53.542649 crawler.go:38: INFO Loading Prospectors: 1
2022/03/09 03:04:53.542911 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/09 03:04:53.543037 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/09 03:04:53.543061 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/09 03:04:53.543111 registrar.go:236: INFO Starting Registrar
2022/03/09 03:04:53.543157 sync.go:41: INFO Start sending events to output
2022/03/09 03:04:53.543210 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/09 03:05:13.547631 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/09 03:05:13.548029 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/09 03:05:13.548084 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/09 03:05:13.548098 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/09 03:05:13.548178 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/09 03:05:18.568079 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:05:18.568135 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:05:19.572308 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:05:19.572341 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:05:21.576837 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:05:21.576903 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:05:23.542046 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/09 03:05:25.589231 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:05:25.589283 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:05:33.597010 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:05:33.597082 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:05:49.617235 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:05:49.617277 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:05:53.541736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:06:21.637663 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:06:21.637827 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:06:23.541657 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:06:53.541787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:07:21.656712 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:07:21.656779 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:07:23.541752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:07:53.541555 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:08:21.675007 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:08:21.675054 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:08:23.541721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:08:53.541615 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:09:21.692622 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:09:21.692665 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:09:23.541650 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:09:53.541725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:10:18.559004 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/09 03:10:18.559033 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/09 03:10:18.561473 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/09 03:10:18.561530 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/09 03:10:21.713309 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:10:21.713346 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:10:23.541633 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/09 03:10:28.566110 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/03/09 03:10:53.541632 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/09 03:11:21.735458 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:11:21.735503 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:11:23.541658 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:11:53.541784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:12:21.753407 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:12:21.753444 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:12:23.541602 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:12:53.541662 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:13:21.770211 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:13:21.770265 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:13:23.541672 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:13:53.541570 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:14:21.787369 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:14:21.787410 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:14:23.541616 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:14:53.541662 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:15:21.804298 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:15:21.804336 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:15:23.541633 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:15:53.541725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:16:21.822954 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:16:21.823012 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:16:23.541598 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:16:53.541574 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:17:21.839939 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:17:21.839979 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:17:23.541581 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:17:53.541669 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:18:21.862365 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:18:21.862402 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:18:23.541622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:18:53.541600 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:19:21.877727 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:19:21.877812 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:19:23.541999 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:19:53.541636 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:20:21.897193 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:20:21.897230 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:20:23.541766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:20:53.541665 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:21:21.919379 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:21:21.919416 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:21:23.541591 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:21:53.541602 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:22:21.939101 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:22:21.939135 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:22:23.541637 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:22:53.541806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:23:21.958509 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:23:21.958551 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:23:23.541657 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:23:53.541706 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:24:21.975682 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:24:21.975717 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:24:23.541654 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:24:53.541620 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:25:21.993730 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:25:21.993793 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:25:23.541557 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:25:53.541700 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:26:22.013094 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:26:22.013154 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:26:23.541569 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:26:53.542007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:27:22.032220 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:27:22.032692 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:27:23.541714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:27:53.541894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:28:22.051542 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:28:22.051749 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:28:23.541707 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:28:53.541636 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:29:22.069695 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:29:22.069746 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:29:23.541622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:29:53.541642 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:30:22.087013 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:30:22.087057 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:30:23.541584 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:30:53.541614 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:31:22.104712 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:31:22.104752 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:31:23.541644 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:31:53.541661 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:32:22.122650 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:32:22.122798 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:32:23.541614 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:32:53.541604 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:33:22.140262 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:33:22.140321 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:33:23.541633 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:33:53.541671 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:34:22.157530 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:34:22.157583 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:34:23.541596 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:34:53.542189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:35:22.173962 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:35:22.174110 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:35:23.541578 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:35:53.541608 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:36:22.191577 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:36:22.191624 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:36:23.541814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:36:53.541872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:37:22.208641 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:37:22.208695 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:37:23.541663 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:37:53.541613 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:38:22.226421 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:38:22.226473 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:38:23.541611 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:38:53.541605 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:39:22.244631 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:39:22.244676 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:39:23.541595 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:39:53.541665 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:40:22.261525 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:40:22.261560 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:40:23.541587 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:40:53.541673 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:41:22.280292 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:41:22.280332 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:41:23.541606 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:41:53.541695 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:42:22.297600 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:42:22.297663 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:42:23.541645 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:42:53.541668 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:43:22.318267 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:43:22.318337 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:43:23.541681 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:43:53.541696 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:44:22.340891 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:44:22.340944 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:44:23.541554 metrics.go:34: INFO No non-zero metrics in the last 30s