2022/03/10 03:15:19.357459 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/10 03:15:19.357564 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/10 03:15:19.357648 metrics.go:23: INFO Metrics logging every 30s
2022/03/10 03:15:19.357754 logstash.go:90: INFO Max Retries set to: 3
2022/03/10 03:15:19.357894 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/10 03:15:19.358079 publish.go:295: INFO Publisher name: onap-vfc-generic-vnfm-driver-757795dcf7-9xp4z
2022/03/10 03:15:19.358386 async.go:63: INFO Flush Interval set to: 1s
2022/03/10 03:15:19.358421 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/10 03:15:19.359139 beat.go:221: INFO filebeat start running.
2022/03/10 03:15:19.359247 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/10 03:15:19.364767 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/10 03:15:19.364862 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/10 03:15:19.364912 crawler.go:38: INFO Loading Prospectors: 1
2022/03/10 03:15:19.365085 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/10 03:15:19.365208 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/10 03:15:19.365241 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/10 03:15:19.365253 registrar.go:236: INFO Starting Registrar
2022/03/10 03:15:19.365285 sync.go:41: INFO Start sending events to output
2022/03/10 03:15:19.365324 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/10 03:15:19.365920 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfmdriver/runtime_gvnfmdriver.log
2022/03/10 03:15:49.358023 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/10 03:16:19.357954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:16:49.357991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:17:19.358017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:17:49.358109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:18:19.357964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:18:49.357992 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:19:19.357961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:19:49.358105 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:20:19.358042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:20:24.379502 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfmdriver/runtime_gvnfmdriver.log. Closing because close_inactive of 5m0s reached.
2022/03/10 03:20:49.358012 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/10 03:21:19.358040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:21:49.357970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:22:19.357955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:22:49.357999 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:23:19.358032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:23:49.358096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:24:19.358077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:24:49.358012 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:25:19.357988 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:25:49.357941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:26:19.357989 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:26:49.358087 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:27:19.358070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:27:49.358039 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:28:19.357994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:28:49.357996 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:29:19.357992 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:29:49.358073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:30:19.358031 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:30:49.357929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:31:19.357961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:31:49.357945 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:32:19.357998 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:32:49.358056 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:33:19.358029 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:33:49.357994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:34:19.357995 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:34:49.358097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:35:19.358075 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:35:49.357913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:36:19.357995 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:36:49.357964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:37:19.358013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:37:49.358042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:38:19.357957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:38:49.357967 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:39:19.358073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:39:49.357976 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:40:19.357989 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:40:49.357936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:41:19.357971 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:41:49.357977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:42:19.357978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:42:49.357977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:43:19.358090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:43:49.358010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:44:19.358978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:44:39.500386 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfmdriver/runtime_gvnfmdriver.log
2022/03/10 03:44:39.545249 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:44:39.545636 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:44:40.548541 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:44:40.548862 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:44:42.552667 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:44:42.552922 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:44:46.559432 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:44:46.559619 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:44:49.358233 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/10 03:44:54.567674 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:44:54.567784 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:45:10.585717 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:45:10.585757 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:45:19.357936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:45:42.606766 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:45:42.606983 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:45:49.358019 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:46:19.357968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:46:42.632227 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:46:42.632280 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:46:49.357975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:47:19.357989 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:47:42.649943 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:47:42.649975 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:47:49.357947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:48:19.357914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:48:42.666664 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:48:42.666715 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:48:49.358032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:49:19.358003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:49:42.687515 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:49:42.687704 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:49:44.522160 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfmdriver/runtime_gvnfmdriver.log. Closing because close_inactive of 5m0s reached.
2022/03/10 03:49:49.357966 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/10 03:50:19.357983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:50:42.704550 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:50:42.704587 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:50:49.358014 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:51:19.357996 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:51:42.721696 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:51:42.721733 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:51:49.357988 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:52:19.357996 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:52:42.741138 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:52:42.741171 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:52:49.358017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:53:19.357966 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:53:42.758107 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:53:42.758146 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:53:49.357902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:54:19.357997 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:54:42.777115 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:54:42.777163 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:54:49.358071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:55:19.357996 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:55:42.792912 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:55:42.792943 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:55:49.357987 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:56:19.358000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:56:42.809301 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:56:42.809340 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:56:49.357951 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:57:19.357948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:57:42.827884 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:57:42.827922 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:57:49.357974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:58:19.358099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:58:42.846098 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:58:42.846165 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:58:49.358065 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:59:19.358145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:59:42.863480 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:59:42.863515 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:59:49.357996 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:00:19.357983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:00:42.881404 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:00:42.881552 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:00:49.358012 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:01:19.357955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:01:42.899970 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:01:42.900003 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:01:49.357994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:02:19.357917 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:02:42.916934 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:02:42.916973 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:02:49.357967 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:03:19.357954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:03:42.932843 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:03:42.932881 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:03:49.358856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:04:19.357971 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:04:42.949970 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:04:42.950008 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:04:49.358041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:05:19.358008 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:05:42.974132 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:05:42.974169 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:05:49.357994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:06:19.357953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:06:42.992216 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:06:42.992569 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:06:49.357987 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:07:19.357968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:07:43.008447 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:07:43.008483 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:07:49.357927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:08:19.357975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:08:43.026149 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:08:43.026185 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:08:49.358029 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:09:19.358010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:09:43.043205 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:09:43.043243 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:09:49.357915 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:10:19.357947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:10:43.061532 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:10:43.061579 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:10:49.357927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:11:19.358002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:11:43.077853 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:11:43.077904 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:11:49.357938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:12:19.357950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:12:43.094848 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:12:43.094885 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:12:49.357931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:13:19.358026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:13:43.117910 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:13:43.118129 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:13:49.357960 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:14:19.358022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:14:43.136913 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:14:43.136980 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:14:49.358087 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:15:19.357960 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:15:43.154588 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:15:43.154767 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:15:49.358017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:16:19.357974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:16:43.172316 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:16:43.172371 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:16:49.358027 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:17:19.357947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:17:43.189036 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:17:43.189086 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:17:49.357930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:18:19.357930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:18:43.206278 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:18:43.206333 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:18:49.358078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:19:19.357990 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:19:43.223493 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:19:43.223546 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:19:49.358025 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:20:19.357963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:20:43.241798 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:20:43.241846 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:20:49.358033 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:21:19.357977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:21:43.259013 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:21:43.259052 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:21:49.357966 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:22:19.357994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:22:43.276210 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:22:43.276250 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:22:49.358008 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:23:19.358053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:23:43.294139 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:23:43.294181 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:23:49.358044 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:24:19.358012 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:24:43.312197 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:24:43.312244 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:24:49.358052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:25:19.357996 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:25:43.331999 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:25:43.332038 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:25:49.357919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:26:19.357995 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:26:43.350594 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:26:43.350634 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:26:49.358033 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:27:19.358038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:27:43.366782 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:27:43.366822 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:27:49.357923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:28:19.358016 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:28:43.383443 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:28:43.383488 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:28:49.358017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:29:19.357983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:29:43.399420 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:29:43.399467 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:29:49.358049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:30:19.357954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:30:43.419038 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:30:43.419072 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:30:49.358005 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:31:19.358774 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:31:43.442746 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:31:43.442781 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:31:49.357957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:32:19.357966 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:32:43.460700 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:32:43.460747 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:32:49.357938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:33:19.358041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:33:43.477723 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:33:43.477781 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:33:49.357937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:34:19.357924 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:34:43.495122 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:34:43.495169 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:34:49.357963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:35:19.357969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:35:43.511419 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:35:43.511457 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:35:49.357930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:36:19.357960 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:36:43.528609 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:36:43.528656 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:36:49.358013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:37:19.358038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:37:43.548785 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:37:43.548826 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:37:49.358023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:38:19.358114 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:38:43.567090 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:38:43.567158 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 04:38:49.358002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:39:19.357993 metrics.go:34: INFO No non-zero metrics in the last 30s