2022/02/17 03:03:57.228151 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/02/17 03:03:57.228196 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/02/17 03:03:57.228288 metrics.go:23: INFO Metrics logging every 30s
2022/02/17 03:03:57.228314 logstash.go:90: INFO Max Retries set to: 3
2022/02/17 03:03:57.228405 outputs.go:108: INFO Activated logstash as output plugin.
2022/02/17 03:03:57.228552 publish.go:295: INFO Publisher name: onap-portal-sdk-856bc9b5d4-pvwpl
2022/02/17 03:03:57.228768 async.go:63: INFO Flush Interval set to: 1s
2022/02/17 03:03:57.228795 async.go:64: INFO Max Bulk Size set to: 2048
2022/02/17 03:03:57.229341 beat.go:221: INFO filebeat start running.
2022/02/17 03:03:57.229449 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/02/17 03:03:57.258405 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/02/17 03:03:57.258508 registrar.go:123: INFO States Loaded from registrar: 0
2022/02/17 03:03:57.258630 crawler.go:38: INFO Loading Prospectors: 1
2022/02/17 03:03:57.258839 sync.go:41: INFO Start sending events to output
2022/02/17 03:03:57.258893 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/02/17 03:03:57.258994 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/02/17 03:03:57.258995 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/02/17 03:03:57.259050 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/02/17 03:03:57.259638 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/02/17 03:03:57.259755 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/02/17 03:03:57.259903 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/02/17 03:03:57.259943 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/02/17 03:03:57.260105 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/02/17 03:03:57.260134 registrar.go:236: INFO Starting Registrar
2022/02/17 03:04:02.269793 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:04:02.269842 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:04:03.275586 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:04:03.275611 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:04:05.280877 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:04:05.280930 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:04:09.289787 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:04:09.289966 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:04:17.301514 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:04:17.301546 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:04:27.228760 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=62 registrar.writes=1
2022/02/17 03:04:33.316479 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:04:33.316524 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:04:57.228709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:05:05.327065 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:05:05.327118 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:05:27.228715 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:05:57.228606 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:06:05.336763 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:06:05.336821 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:06:27.228623 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:06:57.228664 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:07:05.343877 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:07:05.343984 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:07:27.228617 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:07:57.228614 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:08:05.356022 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:08:05.356081 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:08:27.228609 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:08:57.228738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:09:02.271701 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/02/17 03:09:05.272212 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/02/17 03:09:05.272710 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/02/17 03:09:05.364160 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:09:05.364199 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:09:08.273888 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/02/17 03:09:27.228789 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/02/17 03:09:54.281139 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/02/17 03:09:57.228802 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/02/17 03:10:05.371561 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:10:05.371611 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:10:27.228543 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:10:57.228680 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:11:05.380342 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:11:05.380392 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:11:27.228570 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:11:57.229088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:12:05.388952 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:12:05.388979 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:12:27.228612 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:12:57.228747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:13:05.397786 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:13:05.397833 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:13:27.228659 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:13:57.228719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:14:05.405553 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:14:05.405608 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:14:27.228611 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:14:57.228735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:15:05.414288 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:15:05.414336 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:15:27.228532 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:15:57.228712 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:16:05.423736 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:16:05.423762 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:16:27.228688 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:16:57.228575 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:17:05.433352 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:17:05.433495 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:17:27.228663 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:17:57.228657 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:18:05.443256 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:18:05.443307 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:18:27.228589 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:18:57.228658 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:19:05.456420 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:19:05.456470 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:19:27.228718 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:19:57.228637 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:20:05.465313 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:20:05.465350 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:20:27.228707 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:20:57.228729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:21:05.475501 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:21:05.475534 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:21:27.228519 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:21:57.228707 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:22:05.484042 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:22:05.484104 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:22:27.228738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:22:57.228649 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:23:05.493148 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:23:05.493181 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:23:27.228742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:23:57.228651 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:24:05.503181 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:24:05.503293 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:24:27.228686 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:24:57.228739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:25:05.513967 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:25:05.514019 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:25:27.228686 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:25:57.228593 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:26:05.525219 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:26:05.525267 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:26:27.228595 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:26:57.228685 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:27:05.535107 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:27:05.535155 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:27:27.228624 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:27:57.228762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:28:05.545530 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:28:05.545573 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:28:27.228939 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:28:57.228725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:29:05.555973 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:29:05.556022 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:29:27.228981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:29:57.228658 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:30:05.565646 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:30:05.565691 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:30:27.228649 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:30:57.228687 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:31:05.574489 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:31:05.574523 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:31:27.228770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:31:57.228724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:32:05.583854 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:32:05.583893 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:32:27.228652 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:32:57.228620 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:33:05.592882 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:33:05.592952 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:33:27.228729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:33:57.228730 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:34:05.602262 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:34:05.602293 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:34:27.228588 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:34:57.228701 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:35:05.610927 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:35:05.610981 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:35:27.228622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:35:57.228678 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:36:05.619610 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:36:05.619640 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:36:27.228777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:36:57.228656 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:37:05.629744 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:37:05.629795 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:37:27.228565 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:37:57.228686 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:38:05.639097 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:38:05.639147 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:38:27.228687 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:38:57.228869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:39:05.647755 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:39:05.647806 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:39:27.228651 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:39:57.228562 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:40:05.656029 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:40:05.656116 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:40:27.228661 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:40:57.228642 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:41:05.663625 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:41:05.663662 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:41:27.228728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:41:57.228645 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:42:05.673014 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:42:05.673050 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:42:27.228739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:42:57.228648 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:43:05.682255 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:43:05.682309 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:43:27.228790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:43:57.228664 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:44:05.691463 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:44:05.691501 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:44:27.228739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:44:57.228895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:45:05.702866 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:45:05.702907 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:45:27.228612 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:45:57.228546 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:46:05.714639 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:46:05.714701 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:46:27.228572 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:46:57.228635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:47:05.724451 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:47:05.724508 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:47:27.228755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:47:57.228752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:48:05.731959 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:48:05.731990 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:48:27.228726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:48:57.228553 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:49:05.741256 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:49:05.741297 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:49:27.228660 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:49:57.228736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:50:05.752600 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:50:05.752658 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:50:27.228634 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:50:57.228876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:51:05.761404 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:51:05.761465 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:51:27.228634 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:51:57.228700 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:52:05.770918 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:52:05.770955 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:52:27.228676 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:52:57.228686 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:53:05.779479 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:53:05.779513 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:53:27.228667 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:53:57.228932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:54:05.791228 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:54:05.791274 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:54:27.228751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:54:57.229792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:55:05.801474 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:55:05.801513 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:55:27.228760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:55:57.228734 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:56:05.811555 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:56:05.811616 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:56:27.228629 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:56:57.228813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:57:05.819555 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:57:05.819599 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:57:27.228642 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:57:57.228643 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:58:05.824768 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:58:05.824824 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:58:27.228693 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:58:57.228758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:59:05.833888 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:59:05.833967 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 03:59:27.230117 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 03:59:57.228781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:00:05.843229 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:00:05.843279 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:00:27.228813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:00:57.228711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:01:05.853093 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:01:05.853160 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:01:27.228666 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:01:57.228588 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:02:05.863271 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:02:05.863326 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:02:27.228676 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:02:57.228621 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:03:05.872832 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:03:05.872889 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:03:27.228554 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:03:57.228699 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:04:05.881040 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:04:05.881113 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:04:27.228648 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:04:57.228670 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:05:05.891366 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:05:05.891407 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:05:27.228589 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:05:57.228551 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:06:05.901115 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:06:05.901161 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:06:27.228612 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:06:57.228731 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:07:05.909665 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:07:05.909812 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:07:27.228757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:07:57.228650 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:08:05.918696 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:08:05.918725 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:08:27.228652 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:08:57.228736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:09:05.927077 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:09:05.927123 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:09:27.228750 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:09:57.228612 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:10:05.936927 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:10:05.936967 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:10:27.228675 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:10:57.228666 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:11:05.946523 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:11:05.946564 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:11:27.228742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:11:57.228607 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:12:05.955510 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:12:05.955547 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:12:27.228751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:12:57.228775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:13:05.965652 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:13:05.965696 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:13:27.228833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:13:57.228583 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:14:05.974637 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:14:05.974691 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:14:27.228650 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:14:57.228761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:15:05.984672 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:15:05.984709 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:15:27.228711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:15:57.228666 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:16:05.994356 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:16:05.994402 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:16:27.228708 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:16:57.228649 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:17:06.003900 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:17:06.003969 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:17:27.228699 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:17:57.228870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:18:06.016230 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:18:06.016259 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:18:27.228714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:18:57.228747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:19:06.024485 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:19:06.024556 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:19:27.228647 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:19:57.228755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:20:06.034577 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:20:06.034619 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:20:27.228665 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:20:57.228726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:21:06.044865 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:21:06.044919 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:21:27.228583 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:21:57.228572 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:22:06.056766 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:22:06.056854 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:22:27.228634 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:22:57.228620 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:23:06.065884 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:23:06.065921 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:23:27.228609 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:23:57.228578 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:24:06.075258 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:24:06.075301 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:24:27.228678 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:24:57.228620 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:25:06.085591 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:25:06.085636 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:25:27.228682 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:25:57.228656 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:26:06.097124 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:26:06.097197 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:26:27.228667 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:26:57.228680 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:27:06.107504 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:27:06.107565 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:27:27.228709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:27:57.228678 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:28:06.117672 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:28:06.117739 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:28:27.228696 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:28:57.228716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:29:06.128539 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:29:06.128596 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:29:27.228880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:29:57.228541 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:30:06.139043 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:30:06.139092 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:30:27.228602 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:30:57.228698 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:31:06.151136 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:31:06.151194 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:31:27.228685 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:31:57.228673 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:32:06.160254 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:32:06.160308 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:32:27.228720 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:32:57.228763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:33:06.172270 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:33:06.172306 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:33:27.228672 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:33:57.228699 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:34:06.180326 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:34:06.180368 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:34:27.228736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:34:57.228670 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:35:06.191467 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:35:06.191520 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:35:27.228642 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:35:57.228646 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:36:06.199760 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:36:06.199804 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:36:27.228681 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:36:57.228700 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:37:06.221037 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:37:06.221164 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:37:27.228653 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:37:57.228748 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:38:06.230938 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:38:06.231047 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:38:27.228666 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:38:57.228770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:39:06.239873 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:39:06.239902 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:39:27.230742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:39:57.228689 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:40:06.248479 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:40:06.248530 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:40:27.228590 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:40:57.228703 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:41:06.259898 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:41:06.259945 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:41:27.228657 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:41:57.228718 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:42:06.269566 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:42:06.269623 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:42:27.228762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:42:57.228713 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:43:06.278506 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:43:06.278557 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:43:27.228722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:43:57.228707 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:44:06.286611 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:44:06.286657 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:44:27.228607 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:44:57.230436 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:45:06.296853 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:45:06.296884 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:45:27.228783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:45:57.228861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:46:06.306186 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:46:06.306230 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:46:27.228687 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:46:57.228601 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:47:06.314413 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:47:06.314455 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:47:27.228694 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:47:57.228841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:48:06.322975 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:48:06.323098 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:48:27.228680 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:48:57.228707 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:49:06.332771 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:49:06.332848 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:49:27.228670 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:49:57.228642 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:50:06.341783 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:50:06.341819 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:50:27.230007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:50:57.228615 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:51:06.350390 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:51:06.350433 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:51:27.228770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:51:57.228635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:52:06.357585 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:52:06.357631 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:52:27.228692 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:52:57.228577 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:53:06.367852 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:53:06.367907 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:53:27.228676 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:53:57.228725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:54:06.376237 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:54:06.376264 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:54:27.228513 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:54:57.228557 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:55:06.385393 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:55:06.385434 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:55:27.228617 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:55:57.228661 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:56:06.395292 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:56:06.395342 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:56:27.228620 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:56:57.228572 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:57:06.405090 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:57:06.405137 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:57:27.228716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:57:57.228562 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/17 04:58:06.415637 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/17 04:58:06.415673 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host