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
2022/03/09 03:44:53.541637 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:45:22.358701 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:45:22.358742 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:45:23.541671 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:45:53.541622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:46:22.376382 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:46:22.376421 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:46:23.541572 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:46:53.541582 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:47:22.394545 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:47:22.394601 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:47:23.541762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:47:53.541803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:48:22.412501 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:48:22.412555 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:48:23.541564 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:48:53.541704 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:49:22.431420 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:49:22.431469 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:49:23.541763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:49:53.541551 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:50:22.453521 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:50:22.453594 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:50:23.541553 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:50:53.543053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:51:22.462573 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:51:22.462622 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:51:23.541656 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:51:53.541630 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:52:22.482345 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:52:22.482411 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:52:23.541600 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:52:53.541735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:53:22.499961 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:53:22.500015 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:53:23.541818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:53:53.541547 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:54:22.520893 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:54:22.520931 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:54:23.541592 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:54:53.541575 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:55:22.538802 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:55:22.538864 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:55:23.541603 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:55:53.541659 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:56:22.557457 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:56:22.557496 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:56:23.541633 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:56:53.541731 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:57:22.578604 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:57:22.578654 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:57:23.541719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:57:53.541628 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:58:22.596839 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:58:22.596884 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:58:23.541593 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:58:53.541583 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:59:22.614752 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:59:22.614817 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:59:23.541617 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:59:53.541662 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:00:22.632492 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:00:22.632551 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:00:23.541632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:00:53.541860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:01:22.650040 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:01:22.650095 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:01:23.541626 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:01:53.541671 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:02:22.670016 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:02:22.670083 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:02:23.541668 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:02:53.541623 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:03:22.687378 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:03:22.687615 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:03:23.541651 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:03:53.541640 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:04:22.704896 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:04:22.704940 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:04:23.541596 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:04:53.542451 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:05:22.722998 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:05:22.723049 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:05:23.541754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:05:53.541642 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:06:22.739937 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:06:22.739996 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:06:23.545383 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:06:53.541689 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:07:22.758304 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:07:22.758671 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:07:23.541665 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:07:53.541619 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:08:22.776091 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:08:22.776125 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:08:23.541578 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:08:53.541733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:09:22.794408 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:09:22.794459 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:09:23.541729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:09:53.541622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:10:22.813709 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:10:22.813767 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:10:23.541683 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:10:53.541653 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:11:22.830863 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:11:22.830917 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:11:23.541681 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:11:53.541549 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:12:22.850539 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:12:22.850585 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:12:23.541607 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:12:53.541679 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:13:22.868035 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:13:22.868084 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:13:23.541611 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:13:53.545770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:14:22.888130 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:14:22.888178 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:14:23.541574 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:14:53.541719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:15:22.909595 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:15:22.909688 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:15:23.541716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:15:53.541618 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:16:22.931085 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:16:22.931160 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:16:23.541586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:16:53.541605 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:17:22.949416 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:17:22.949468 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:17:23.541675 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:17:53.541663 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:18:22.992678 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:18:22.992753 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:18:23.541743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:18:53.541606 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:19:23.014206 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:19:23.014398 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:19:23.541557 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:19:53.541644 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:20:23.031726 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:20:23.031771 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:20:23.541649 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:20:53.541757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:21:23.050553 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:21:23.050608 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:21:23.541626 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:21:53.541673 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:22:23.072576 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:22:23.072618 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:22:23.541589 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:22:53.541622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:23:23.092811 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:23:23.092855 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:23:23.541680 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:23:53.545663 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:24:23.111441 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:24:23.111490 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:24:23.541645 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:24:53.541655 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:25:23.128795 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:25:23.128842 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:25:23.541679 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:25:53.541598 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:26:23.150752 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:26:23.150802 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:26:23.541631 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:26:53.541571 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:27:23.169107 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:27:23.169520 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:27:23.541798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:27:53.541568 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:28:23.193461 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:28:23.193531 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:28:23.541609 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:28:53.541568 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:29:23.212808 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:29:23.212852 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:29:23.543342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:29:53.541629 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:30:23.232346 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:30:23.232391 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:30:23.541594 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:30:53.541651 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:31:23.250745 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:31:23.250784 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:31:23.541647 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:31:53.541561 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:32:23.267378 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:32:23.267445 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:32:23.541623 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:32:53.541624 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:33:23.290569 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:33:23.290851 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:33:23.541603 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:33:53.541632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:34:23.308557 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:34:23.308599 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:34:23.541614 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:34:53.541582 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:35:23.324561 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:35:23.324613 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:35:23.541594 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:35:53.541617 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:36:23.345318 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:36:23.345379 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:36:23.541611 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:36:53.541623 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:37:23.362736 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:37:23.362815 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:37:23.541768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:37:53.541697 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:38:23.381318 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:38:23.381374 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:38:23.541738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:38:53.543892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:39:23.401207 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:39:23.401266 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:39:23.541654 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:39:53.541657 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:40:23.419922 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:40:23.419965 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:40:23.541686 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:40:53.541664 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:41:23.436422 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:41:23.436461 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:41:23.541599 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:41:53.541603 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:42:23.454159 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:42:23.454201 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:42:23.541681 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:42:53.541696 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:43:23.471792 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:43:23.471834 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:43:23.541669 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:43:53.541883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:44:23.490216 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:44:23.490255 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:44:23.541714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:44:53.541605 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:45:23.506590 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:45:23.506643 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:45:23.541634 metrics.go:34: INFO No non-zero metrics in the last 30s