2022/03/05 03:28:52.209580 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/05 03:28:52.209632 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/05 03:28:52.209739 logstash.go:90: INFO Max Retries set to: 3
2022/03/05 03:28:52.209825 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/05 03:28:52.209967 publish.go:295: INFO Publisher name: onap-vfc-generic-vnfm-driver-757795dcf7-965wl
2022/03/05 03:28:52.210232 async.go:63: INFO Flush Interval set to: 1s
2022/03/05 03:28:52.210259 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/05 03:28:52.210241 metrics.go:23: INFO Metrics logging every 30s
2022/03/05 03:28:52.211143 beat.go:221: INFO filebeat start running.
2022/03/05 03:28:52.211348 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/05 03:28:52.214995 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/05 03:28:52.215068 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/05 03:28:52.215136 crawler.go:38: INFO Loading Prospectors: 1
2022/03/05 03:28:52.215318 sync.go:41: INFO Start sending events to output
2022/03/05 03:28:52.215479 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/05 03:28:52.215464 registrar.go:236: INFO Starting Registrar
2022/03/05 03:28:52.215715 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/05 03:28:52.215828 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/05 03:28:52.215857 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/05 03:28:52.216548 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfmdriver/runtime_gvnfmdriver.log
2022/03/05 03:29:22.211015 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/05 03:29:52.210801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:30:22.210858 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:30:52.210869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:31:22.211017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:31:52.211112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:32:22.210925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:32:52.210924 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:33:22.210841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:33:52.210817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:33:57.225778 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfmdriver/runtime_gvnfmdriver.log. Closing because close_inactive of 5m0s reached.
2022/03/05 03:34:22.210944 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/05 03:34:52.210878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:35:22.210911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:35:52.211276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:36:22.210922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:36:52.210778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:37:22.210857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:37:52.210830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:38:22.210875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:38:52.210795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:39:22.210852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:39:52.210903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:40:22.210847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:40:52.210836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:41:22.210859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:41:52.210835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:42:22.210831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:42:52.210838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:43:22.210805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:43:52.211041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:44:22.210867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:44:52.210842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:45:22.210926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:45:52.210804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:46:22.210818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:46:52.210930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:47:22.210823 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:47:52.210839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:48:22.211684 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:48:52.210857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:49:22.210842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:49:52.210893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:50:22.210810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:50:52.210787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:51:22.210839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:51:52.210766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:52:22.210794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:52:52.210817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:53:22.210964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:53:52.210956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:54:22.210969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:54:52.210796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:55:22.210898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:55:52.210788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:56:22.210879 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:56:52.210799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:57:22.210824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:57:52.210781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:58:22.211407 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:58:32.407246 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfmdriver/runtime_gvnfmdriver.log
2022/03/05 03:58:37.325089 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:37.325158 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:38.340252 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:38.340313 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:40.345053 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:40.345089 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:44.353710 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:44.353745 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:52.210836 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/05 03:58:52.366154 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:52.366410 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:59:08.372282 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:59:08.372313 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:59:22.210848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:59:40.377254 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:59:40.377290 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:59:52.210827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:00:22.210763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:00:40.383348 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:00:40.383390 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:00:52.210962 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:01:22.210824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:01:40.388675 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:01:40.388715 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:01:52.210912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:02:22.210951 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:02:40.396352 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:02:40.396504 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:02:52.210814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:03:22.210818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:03:37.425485 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfmdriver/runtime_gvnfmdriver.log. Closing because close_inactive of 5m0s reached.
2022/03/05 04:03:40.401858 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:03:40.401894 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:03:52.210797 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/05 04:04:22.210827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:04:40.409926 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:04:40.409989 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:04:52.210834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:05:22.210836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:05:40.416007 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:05:40.416059 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:05:52.210812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:06:22.211030 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:06:40.421487 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:06:40.421532 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:06:52.210861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:07:22.210920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:07:40.427776 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:07:40.427813 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:07:52.210901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:08:22.210776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:08:40.434095 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:08:40.434138 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:08:52.210958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:09:22.210818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:09:40.440695 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:09:40.440744 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:09:52.210827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:10:22.210792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:10:40.446585 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:10:40.446641 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:10:52.210862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:11:22.210835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:11:40.451780 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:11:40.451836 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:11:52.210889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:12:22.210816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:12:40.457029 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:12:40.457186 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:12:52.212568 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:13:22.210857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:13:40.463858 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:13:40.463931 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:13:52.210811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:14:22.210802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:14:40.469605 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:14:40.469644 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:14:52.210807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:15:22.210786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:15:40.476857 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:15:40.476938 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:15:52.211071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:16:22.210817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:16:40.482934 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:16:40.482995 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:16:52.210775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:17:22.210835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:17:40.488131 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:17:40.488165 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:17:52.210940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:18:22.210822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:18:40.493718 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:18:40.493778 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:18:52.210790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:19:22.210837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:19:40.499849 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:19:40.499898 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:19:52.210947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:20:22.210795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:20:40.504751 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:20:40.504802 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:20:52.210906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:21:22.210856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:21:40.510191 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:21:40.510226 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:21:52.210825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:22:22.210856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:22:40.514835 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:22:40.514871 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:22:52.210808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:23:22.210833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:23:40.529207 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:23:40.529248 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:23:52.210873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:24:22.210796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:24:40.536301 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:24:40.536371 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:24:52.211706 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:25:22.210830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:25:40.541658 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:25:40.541813 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:25:52.210794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:26:22.210885 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:26:40.546836 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:26:40.546881 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:26:52.210835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:27:22.210841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:27:40.552776 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:27:40.552918 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:27:52.211147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:28:22.210800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:28:40.564756 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:28:40.564790 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:28:52.210833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:29:22.210840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:29:40.569967 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:29:40.570006 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:29:52.210794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:30:22.210817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:30:40.574734 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:30:40.574767 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:30:52.210992 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:31:22.210985 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:31:40.578782 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:31:40.578820 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:31:52.211057 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:32:22.210926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:32:40.583509 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:32:40.583647 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:32:52.210804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:33:22.210838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:33:40.587600 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:33:40.587635 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:33:52.210825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:34:22.210872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:34:40.591382 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:34:40.591419 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:34:52.210858 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:35:22.210842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:35:40.595039 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:35:40.595083 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:35:52.210856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:36:22.210846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:36:40.601383 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:36:40.601479 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:36:52.210975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:37:22.210900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:37:40.605248 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:37:40.605284 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:37:52.210782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:38:22.210864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:38:40.608964 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:38:40.609022 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:38:52.210838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:39:22.210817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:39:40.612793 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:39:40.612834 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:39:52.210830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:40:22.210791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:40:40.616584 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:40:40.616621 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:40:52.210875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:41:22.210820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:41:40.620231 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:41:40.620267 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:41:52.210933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:42:22.211001 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:42:40.623916 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:42:40.623964 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:42:52.214079 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:43:22.210917 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:43:40.627990 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:43:40.628029 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:43:52.210851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:44:22.210812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:44:40.632230 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:44:40.632282 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:44:52.210811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:45:22.210900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:45:40.636316 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:45:40.636368 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:45:52.210821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:46:22.210831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:46:40.640151 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:46:40.640186 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:46:52.210959 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:47:22.210881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:47:40.644527 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:47:40.644575 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:47:52.210806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:48:22.211124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:48:40.648997 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:48:40.649033 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:48:52.210912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:49:22.210820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:49:40.652844 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:49:40.652898 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:49:52.210838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:50:22.210822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:50:40.656764 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:50:40.656949 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:50:52.210804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:51:22.210897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:51:40.660520 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:51:40.660577 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:51:52.210981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:52:22.210841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:52:40.665131 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:52:40.665171 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:52:52.210924 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:53:22.210816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:53:40.671080 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:53:40.671134 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:53:52.210861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:54:22.210876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:54:40.675146 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:54:40.675188 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:54:52.210785 metrics.go:34: INFO No non-zero metrics in the last 30s