2022/03/15 03:13:13.364051 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/15 03:13:13.364109 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/15 03:13:13.364211 logstash.go:90: INFO Max Retries set to: 3
2022/03/15 03:13:13.364297 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/15 03:13:13.364531 metrics.go:23: INFO Metrics logging every 30s
2022/03/15 03:13:13.364734 publish.go:295: INFO Publisher name: onap-vfc-nslcm-54bbdbd75d-96ngb
2022/03/15 03:13:13.365034 async.go:63: INFO Flush Interval set to: 1s
2022/03/15 03:13:13.365064 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/15 03:13:13.365988 beat.go:221: INFO filebeat start running.
2022/03/15 03:13:13.366308 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/15 03:13:13.378335 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/15 03:13:13.378439 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/15 03:13:13.378490 crawler.go:38: INFO Loading Prospectors: 1
2022/03/15 03:13:13.378538 registrar.go:236: INFO Starting Registrar
2022/03/15 03:13:13.378732 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/15 03:13:13.378723 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/15 03:13:13.378781 sync.go:41: INFO Start sending events to output
2022/03/15 03:13:13.378900 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/15 03:13:13.378942 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/15 03:13:13.379627 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/nslcm/runtime_nslcm.log
2022/03/15 03:13:43.365156 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/15 03:14:13.364958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:14:43.365111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:15:13.364889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:15:43.364948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:16:13.365097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:16:43.365533 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:17:13.364849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:17:43.364927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:18:13.364910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:18:18.400272 log.go:116: INFO File is inactive: /var/log/onap/vfc/nslcm/runtime_nslcm.log. Closing because close_inactive of 5m0s reached.
2022/03/15 03:18:43.365131 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/15 03:19:13.364867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:19:43.364975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:20:13.364982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:20:43.365007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:21:13.364973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:21:43.364868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:22:13.365041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:22:43.364960 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:23:13.365245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:23:43.364824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:24:13.364856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:24:43.366301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:25:13.365066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:25:43.364869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:26:13.364883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:26:43.364809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:27:13.364868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:27:43.364979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:28:13.365002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:28:43.364831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:29:13.364928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:29:43.364972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:30:13.364980 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:30:43.364913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:31:13.364947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:31:43.364939 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:32:13.364884 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:32:43.364839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:33:13.364869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:33:43.364931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:34:13.364988 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:34:43.364973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:35:13.364920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:35:43.365022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:36:13.365039 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:36:43.364966 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:37:13.364869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:37:43.365377 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:38:13.364847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:38:43.364860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:39:13.364873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:39:43.364913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:40:13.364862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:40:43.364897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:41:13.364882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:41:43.366209 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:42:13.366350 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:42:13.618015 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/nslcm/runtime_nslcm.log
2022/03/15 03:42:18.541695 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:42:18.541725 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:42:19.547827 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:42:19.547882 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:42:21.552108 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:42:21.552141 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:42:25.558684 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:42:25.558726 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:42:33.565699 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:42:33.565751 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:42:43.364917 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/15 03:42:49.574609 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:42:49.574649 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:43:13.364902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:43:21.579449 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:43:21.579870 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:43:43.364821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:44:13.364867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:44:21.585873 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:44:21.585918 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:44:43.364907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:45:13.364838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:45:21.590302 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:45:21.590446 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:45:43.364897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:46:13.364911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:46:21.594626 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:46:21.594671 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:46:43.364938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:47:13.364986 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:47:18.638922 log.go:116: INFO File is inactive: /var/log/onap/vfc/nslcm/runtime_nslcm.log. Closing because close_inactive of 5m0s reached.
2022/03/15 03:47:21.599542 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:47:21.599706 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:47:43.364903 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/15 03:48:13.366136 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:48:21.604491 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:48:21.604562 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:48:43.364942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:49:13.364876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:49:21.609303 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:49:21.609378 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:49:43.364898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:50:13.364846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:50:21.613726 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:50:21.613770 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:50:43.364790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:51:13.364837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:51:21.617561 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:51:21.617597 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:51:43.364873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:52:13.364970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:52:21.622346 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:52:21.622388 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:52:43.364899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:53:13.364932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:53:21.627595 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:53:21.627692 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:53:43.364938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:54:13.364833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:54:21.633702 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:54:21.633743 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:54:43.364805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:55:13.364888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:55:21.638769 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:55:21.638814 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:55:43.364852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:56:13.364944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:56:21.642884 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:56:21.642958 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:56:43.364884 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:57:13.364952 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:57:21.647272 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:57:21.647328 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:57:43.364933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:58:13.364840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:58:21.652420 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:58:21.652633 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:58:43.364862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:59:13.364880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:59:21.658541 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:59:21.658643 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:59:43.364955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:00:13.365078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:00:21.663616 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:00:21.663730 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:00:43.364867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:01:13.364898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:01:21.668225 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:01:21.668264 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:01:43.364826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:02:13.364961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:02:21.673833 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:02:21.674326 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:02:43.364950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:03:13.365016 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:03:21.679647 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:03:21.679684 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:03:43.365030 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:04:13.364935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:04:21.683638 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:04:21.683687 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:04:43.364996 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:05:13.364980 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:05:21.688654 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:05:21.688701 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:05:43.364795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:06:13.364952 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:06:21.694286 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:06:21.694447 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:06:43.364967 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:07:13.365098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:07:21.701071 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:07:21.701118 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:07:43.364938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:08:13.364906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:08:21.706271 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:08:21.706543 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:08:43.364875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:09:13.364917 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:09:21.710826 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:09:21.710864 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:09:43.364857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:10:13.364839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:10:21.715226 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:10:21.715293 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:10:43.364828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:11:13.364905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:11:21.720115 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:11:21.720158 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:11:43.364908 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:12:13.364903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:12:21.724581 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:12:21.724623 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:12:43.364910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:13:13.364836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:13:21.729193 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:13:21.729282 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:13:43.364976 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:14:13.364863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:14:21.733142 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:14:21.733191 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:14:43.364941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:15:13.364993 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:15:21.737873 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:15:21.738441 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:15:43.364936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:16:13.364821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:16:21.742044 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:16:21.742115 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:16:43.364903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:17:13.364919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:17:21.746092 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:17:21.746248 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:17:43.364863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:18:13.364998 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:18:21.752875 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:18:21.752959 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:18:43.364898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:19:13.364971 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:19:21.774912 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:19:21.774994 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:19:43.364911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:20:13.364934 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:20:21.782731 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:20:21.782774 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:20:43.364830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:21:13.364919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:21:21.788471 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:21:21.788526 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:21:43.364937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:22:13.364967 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:22:21.795576 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:22:21.795620 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:22:43.364997 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:23:13.364863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:23:21.801853 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:23:21.801903 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:23:43.365073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:24:13.365317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:24:21.807733 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:24:21.807779 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:24:43.364855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:25:13.364863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:25:21.814163 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:25:21.814221 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:25:43.365010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:26:13.364925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:26:21.821047 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:26:21.821091 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:26:43.364941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:27:13.366451 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:27:21.826552 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:27:21.826719 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 04:27:43.364870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 04:28:13.364810 metrics.go:34: INFO No non-zero metrics in the last 30s