2022/03/24 03:12:53.166026 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/24 03:12:53.166079 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/24 03:12:53.166191 logstash.go:90: INFO Max Retries set to: 3
2022/03/24 03:12:53.166281 metrics.go:23: INFO Metrics logging every 30s
2022/03/24 03:12:53.166293 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/24 03:12:53.166602 publish.go:295: INFO Publisher name: onap-vfc-zte-vnfm-driver-65d7c4d97b-hd84b
2022/03/24 03:12:53.166936 async.go:63: INFO Flush Interval set to: 1s
2022/03/24 03:12:53.166973 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/24 03:12:53.167557 beat.go:221: INFO filebeat start running.
2022/03/24 03:12:53.167647 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/24 03:12:53.170745 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/24 03:12:53.170816 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/24 03:12:53.170881 crawler.go:38: INFO Loading Prospectors: 1
2022/03/24 03:12:53.171180 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/24 03:12:53.171372 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/24 03:12:53.171555 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/24 03:12:53.171354 sync.go:41: INFO Start sending events to output
2022/03/24 03:12:53.171736 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/24 03:12:53.171879 registrar.go:236: INFO Starting Registrar
2022/03/24 03:12:53.172758 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log
2022/03/24 03:13:23.166921 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=1 filebeat.harvester.running=1 filebeat.harvester.started=1 publish.events=1 registrar.states.current=1 registrar.states.update=1 registrar.writes=2
2022/03/24 03:13:53.166635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:14:23.166766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:14:53.166824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:15:23.167532 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:15:53.168871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:16:23.166762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:16:53.166726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:17:23.166736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:17:53.166698 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:17:58.198994 log.go:116: INFO File is inactive: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log. Closing because close_inactive of 5m0s reached.
2022/03/24 03:18:23.166902 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=1 filebeat.harvester.open_files=-1 filebeat.harvester.running=-1 publish.events=1 registrar.states.update=1 registrar.writes=1
2022/03/24 03:18:53.166708 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:19:23.166678 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:19:53.166646 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:20:23.166827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:20:53.166637 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:21:23.166716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:21:53.166599 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:22:23.166709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:22:53.166703 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:23:23.166696 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:23:53.166667 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:24:23.166641 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:24:53.166697 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:25:23.166641 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:25:53.166701 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:26:23.166621 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:26:53.166655 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:27:23.166761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:27:53.166631 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:28:23.166704 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:28:53.166773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:29:23.166637 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:29:53.166616 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:30:23.166663 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:30:53.166660 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:31:23.166676 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:31:53.166632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:32:23.166848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:32:53.166645 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:33:23.166646 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:33:53.166634 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:34:23.166646 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:34:53.166645 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:35:23.166673 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:35:53.166712 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:36:23.166735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:36:53.166769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:37:23.166656 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:37:53.166680 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:38:23.166665 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:38:53.166674 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:39:23.166754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:39:53.166704 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:40:23.166660 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:40:23.305737 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log
2022/03/24 03:40:23.345921 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:23.345986 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:24.348996 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:24.349040 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:26.353630 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:26.353663 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:30.359502 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:30.359535 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:38.365414 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:38.365455 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:53.166730 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=1 filebeat.harvester.running=1 filebeat.harvester.started=1 libbeat.publisher.published_events=1
2022/03/24 03:40:54.381970 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:54.382007 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:41:23.166786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:41:26.400996 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:41:26.401044 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:41:53.166711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:42:23.166885 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:42:26.421845 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:42:26.421891 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:42:53.166650 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:43:23.166649 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:43:26.440723 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:43:26.440780 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:43:53.166788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:44:23.166668 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:44:26.461425 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:44:26.461593 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:44:53.166656 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:45:23.166681 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:45:26.479665 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:45:26.479711 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:45:28.319725 log.go:116: INFO File is inactive: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log. Closing because close_inactive of 5m0s reached.
2022/03/24 03:45:53.166628 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/24 03:46:23.166589 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:46:26.499343 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:46:26.499385 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:46:53.166712 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:47:23.166640 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:47:26.517854 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:47:26.517893 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:47:53.166729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:48:23.166638 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:48:26.535592 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:48:26.535655 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:48:53.166701 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:49:23.166765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:49:26.553491 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:49:26.553547 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:49:53.166639 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:50:23.166619 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:50:26.572544 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:50:26.572670 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:50:53.166635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:51:23.166639 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:51:26.593743 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:51:26.593778 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:51:53.166761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:52:23.166574 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:52:26.612893 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:52:26.612934 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:52:53.166644 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:53:23.166777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:53:26.629670 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:53:26.629702 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:53:53.166738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:54:23.166865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:54:26.647907 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:54:26.647943 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:54:53.166616 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:55:23.166622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:55:26.669054 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:55:26.669090 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:55:53.166665 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:56:23.166700 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:56:26.686771 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:56:26.686806 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:56:53.166603 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:57:23.166697 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:57:26.705392 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:57:26.705433 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:57:53.166682 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:58:23.166755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:58:26.726217 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:58:26.726255 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:58:53.166651 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:59:23.166601 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:59:26.745498 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:59:26.745553 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:59:53.166643 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:00:23.166710 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:00:26.765098 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:00:26.765148 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:00:53.166752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:01:23.166636 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:01:26.785842 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:01:26.786306 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:01:53.166698 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:02:23.166669 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:02:26.806007 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:02:26.806050 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:02:53.166642 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:03:23.166677 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:03:26.824149 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:03:26.824185 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:03:53.166667 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:04:23.166722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:04:26.841651 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:04:26.841695 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:04:53.166668 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:05:23.166612 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:05:26.860780 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:05:26.860867 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:05:53.166697 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:06:23.166584 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:06:26.881683 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:06:26.881719 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:06:53.166698 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:07:23.166655 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:07:26.901688 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:07:26.901724 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:07:53.166610 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:08:23.166629 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:08:26.924609 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:08:26.924653 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:08:53.166655 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:09:23.166701 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:09:26.942239 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:09:26.942278 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:09:53.166663 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:10:23.166652 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:10:26.961662 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:10:26.961698 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:10:53.170437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:11:23.166669 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:11:26.980152 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:11:26.980183 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:11:53.166623 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:12:23.166641 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:12:26.998067 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:12:26.998116 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:12:53.166614 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:13:23.166662 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:13:27.019120 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:13:27.019161 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:13:53.166681 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:14:23.166654 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:14:27.036701 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:14:27.036744 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:14:53.166722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:15:23.166652 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:15:27.055061 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:15:27.055091 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:15:53.166593 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:16:23.166795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:16:27.072207 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:16:27.072243 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:16:53.166598 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:17:23.166606 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:17:27.089681 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:17:27.089736 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:17:53.166679 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:18:23.166701 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:18:27.109342 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:18:27.109380 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:18:53.166683 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:19:23.166643 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:19:27.129240 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:19:27.129439 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:19:53.166662 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:20:23.166644 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:20:27.146341 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:20:27.146381 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:20:53.166662 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:21:23.166643 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:21:27.168280 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:21:27.168315 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:21:53.166621 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:22:23.166607 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:22:27.188227 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:22:27.188265 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:22:53.166636 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:23:23.166639 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:23:27.206438 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:23:27.206475 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:23:53.166648 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:24:23.166623 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:24:27.224778 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:24:27.224807 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:24:53.166710 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:25:23.166644 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:25:27.251537 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:25:27.251575 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:25:53.166734 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:26:23.166638 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:26:27.268387 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:26:27.268424 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:26:53.166586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:27:23.166623 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:27:27.292932 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:27:27.292973 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:27:53.166732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:28:23.166630 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:28:27.311130 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:28:27.311299 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:28:53.166688 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:29:23.166717 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:29:27.330794 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:29:27.330937 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:29:53.166677 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:30:23.166705 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:30:27.349338 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:30:27.349514 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:30:53.166624 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:31:23.166653 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:31:27.367541 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:31:27.367580 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:31:53.166629 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:32:23.166740 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:32:27.384418 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:32:27.384491 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:32:53.166612 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:33:23.166707 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:33:27.405927 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:33:27.405968 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:33:53.166595 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:34:23.166572 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:34:27.425012 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:34:27.425055 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:34:53.166670 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:35:23.166618 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:35:27.445667 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:35:27.445724 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host