2022/03/24 03:12:47.192194 beat.go:285: INFO Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs]
2022/03/24 03:12:47.192248 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/24 03:12:47.192745 logstash.go:90: INFO Max Retries set to: 3
2022/03/24 03:12:47.192858 metrics.go:23: INFO Metrics logging every 30s
2022/03/24 03:12:47.192840 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/24 03:12:47.193116 publish.go:295: INFO Publisher name: onap-vfc-vnfmgr-8594ffd488-wdl75
2022/03/24 03:12:47.193354 async.go:63: INFO Flush Interval set to: 1s
2022/03/24 03:12:47.193377 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/24 03:12:47.194167 beat.go:221: INFO filebeat start running.
2022/03/24 03:12:47.194302 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/24 03:12:47.199653 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/24 03:12:47.199718 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/24 03:12:47.199778 crawler.go:38: INFO Loading Prospectors: 1
2022/03/24 03:12:47.199848 registrar.go:236: INFO Starting Registrar
2022/03/24 03:12:47.199883 sync.go:41: INFO Start sending events to output
2022/03/24 03:12:47.199969 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/24 03:12:47.200005 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/24 03:12:47.200065 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/24 03:12:47.200095 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/24 03:12:47.200617 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnfmgr/runtime_mgr.log
2022/03/24 03:13:17.193402 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=1 filebeat.harvester.running=1 filebeat.harvester.started=1 publish.events=1 registrar.states.current=1 registrar.states.update=1 registrar.writes=2
2022/03/24 03:13:47.193436 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:14:17.193213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:14:47.193246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:15:17.193459 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:15:47.193665 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:16:17.193205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:16:47.193265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:17:17.193261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:17:47.193167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:17:52.211219 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfm-vnfmgr/runtime_mgr.log. Closing because close_inactive of 5m0s reached.
2022/03/24 03:18:17.193214 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=1 filebeat.harvester.open_files=-1 filebeat.harvester.running=-1 publish.events=1 registrar.states.update=1 registrar.writes=1
2022/03/24 03:18:47.193320 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:19:17.193155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:19:47.193317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:20:17.193226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:20:47.193121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:21:17.193295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:21:47.193273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:22:17.193325 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:22:47.193456 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:23:17.193226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:23:47.193131 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:24:17.193158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:24:47.193123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:25:17.193245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:25:47.193199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:26:17.193148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:26:47.193174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:27:17.193138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:27:47.193190 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:28:17.193260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:28:47.193229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:29:17.193164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:29:47.193173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:30:17.193145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:30:47.193147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:31:17.193281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:31:47.193213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:32:17.193194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:32:47.193217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:33:17.193217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:33:47.193215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:34:17.193240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:34:47.193150 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:35:17.193149 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:35:47.193225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:36:17.193202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:36:47.193226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:37:17.193249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:37:47.193181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:38:17.193205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:38:47.193144 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:39:17.193175 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:39:47.193126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:40:17.193212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:40:17.328856 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnfmgr/runtime_mgr.log
2022/03/24 03:40:22.347208 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:22.347268 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:23.350760 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:23.350802 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:25.354399 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:25.354452 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:29.360005 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:29.360077 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:37.365723 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:37.365755 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:47.193212 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=1 filebeat.harvester.running=1 filebeat.harvester.started=1 libbeat.publisher.published_events=1
2022/03/24 03:40:53.382542 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:53.382584 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:41:17.193225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:41:25.399396 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:41:25.399537 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:41:47.193139 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:42:17.193292 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:42:25.415638 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:42:25.415674 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:42:47.193200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:43:17.193236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:43:25.433759 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:43:25.433802 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:43:47.193237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:44:17.193117 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:44:25.459961 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:44:25.460008 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:44:47.193163 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:45:17.197256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:45:22.345775 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfm-vnfmgr/runtime_mgr.log. Closing because close_inactive of 5m0s reached.
2022/03/24 03:45:25.478480 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:45:25.478529 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:45:47.193261 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=1 filebeat.harvester.open_files=-1 filebeat.harvester.running=-1
2022/03/24 03:46:17.193171 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:46:25.504672 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:46:25.504743 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:46:47.194318 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:47:17.193230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:47:25.524118 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:47:25.524159 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:47:47.193180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:48:17.193200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:48:25.551622 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:48:25.551669 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:48:47.193173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:49:17.193159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:49:25.570445 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:49:25.570517 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:49:47.193599 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:50:17.193096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:50:25.590713 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:50:25.590763 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:50:47.193191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:51:17.193223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:51:25.608498 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:51:25.608542 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:51:47.193171 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:52:17.193163 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:52:25.632671 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:52:25.632710 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:52:47.193236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:53:17.193203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:53:25.651025 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:53:25.651061 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:53:47.193152 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:54:17.193152 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:54:25.668400 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:54:25.668435 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:54:47.193706 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:55:17.193366 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:55:25.685178 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:55:25.685327 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:55:47.193148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:56:17.193205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:56:25.702167 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:56:25.702208 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:56:47.193140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:57:17.193271 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:57:25.721458 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:57:25.721497 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:57:47.193181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:58:17.193431 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:58:25.741314 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:58:25.741377 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:58:47.193230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:59:17.193182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:59:25.771191 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:59:25.771279 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:59:47.193144 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:00:17.193125 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:00:25.792160 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:00:25.792202 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:00:47.193629 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:01:17.193324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:01:25.812252 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:01:25.812301 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:01:47.193198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:02:17.193591 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:02:25.848237 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:02:25.848292 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:02:47.193205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:03:17.193138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:03:25.867995 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:03:25.868048 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:03:47.193144 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:04:17.193180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:04:25.886969 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:04:25.887005 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:04:47.193246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:05:17.193142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:05:25.904174 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:05:25.904210 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:05:47.193148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:06:17.193194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:06:25.923937 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:06:25.924143 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:06:47.193169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:07:17.193117 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:07:25.942745 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:07:25.942798 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:07:47.193133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:08:17.193185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:08:25.962839 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:08:25.962885 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:08:47.193189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:09:17.193133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:09:25.980591 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:09:25.980631 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:09:47.193136 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:10:17.193190 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:10:26.000289 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:10:26.000328 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:10:47.193182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:11:17.193192 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:11:26.017850 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:11:26.017986 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:11:47.193158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:12:17.193281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:12:26.133366 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:12:26.133408 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:12:47.193121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:13:17.193233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:13:26.156346 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:13:26.156435 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:13:47.193239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:14:17.193194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:14:26.175884 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:14:26.175929 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:14:47.193152 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:15:17.193156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:15:26.195488 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:15:26.195526 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:15:47.193218 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:16:17.193264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:16:26.215887 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:16:26.215931 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:16:47.193253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:17:17.193194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:17:26.233997 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:17:26.234048 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:17:47.193155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:18:17.193167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:18:26.254101 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:18:26.254134 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:18:47.193132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:19:17.193161 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:19:26.273197 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:19:26.273242 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:19:47.193154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:20:17.193753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:20:26.293747 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:20:26.293866 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:20:47.193211 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:21:17.193176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:21:26.312104 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:21:26.312141 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:21:47.193266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:22:17.193139 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:22:26.328975 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:22:26.329016 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:22:47.193180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:23:17.193155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:23:26.351927 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:23:26.351972 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:23:47.193352 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:24:17.193152 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:24:26.370022 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:24:26.370096 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:24:47.193131 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:25:17.193151 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:25:26.387502 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:25:26.387534 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:25:47.193130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:26:17.193301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:26:26.405693 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:26:26.405756 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:26:47.193167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:27:17.193236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:27:26.425361 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:27:26.425399 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:27:47.193164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:28:17.193172 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:28:26.445774 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:28:26.445808 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:28:47.193344 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:29:17.193303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:29:26.464827 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:29:26.464894 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:29:47.193329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:30:17.193214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:30:26.487005 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:30:26.487063 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:30:47.193391 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:31:17.193554 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:31:26.513125 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:31:26.513163 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:31:47.193177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:32:17.193236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:32:26.530456 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:32:26.530492 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:32:47.193105 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:33:17.193248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:33:26.547648 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:33:26.547681 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:33:47.193324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:34:17.193233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:34:26.566470 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:34:26.566504 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:34:47.193248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:35:17.193167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:35:26.591121 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:35:26.591169 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:35:47.193187 metrics.go:34: INFO No non-zero metrics in the last 30s