2022/03/10 03:15:07.222750 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:07.222795 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/10 03:15:07.222896 logstash.go:90: INFO Max Retries set to: 3
2022/03/10 03:15:07.222904 metrics.go:23: INFO Metrics logging every 30s
2022/03/10 03:15:07.222954 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/10 03:15:07.223069 publish.go:295: INFO Publisher name: onap-vfc-zte-vnfm-driver-65d7c4d97b-l78w6
2022/03/10 03:15:07.223284 async.go:63: INFO Flush Interval set to: 1s
2022/03/10 03:15:07.223308 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/10 03:15:07.223738 beat.go:221: INFO filebeat start running.
2022/03/10 03:15:07.223885 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/10 03:15:07.229046 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/10 03:15:07.229165 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/10 03:15:07.229209 crawler.go:38: INFO Loading Prospectors: 1
2022/03/10 03:15:07.229514 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/10 03:15:07.229524 sync.go:41: INFO Start sending events to output
2022/03/10 03:15:07.229614 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/10 03:15:07.229735 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/10 03:15:07.229686 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/10 03:15:07.229882 registrar.go:236: INFO Starting Registrar
2022/03/10 03:15:07.231016 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log
2022/03/10 03:15:37.224182 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:07.223382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:16:37.227503 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:17:07.223447 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:17:37.223259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:18:07.223278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:18:37.223354 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:19:07.223299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:19:37.223346 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:20:07.223510 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:20:12.247930 log.go:116: INFO File is inactive: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log. Closing because close_inactive of 5m0s reached.
2022/03/10 03:20:37.223633 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:07.223345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:21:37.223505 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:22:07.223277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:22:37.223374 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:23:07.223275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:23:37.223379 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:24:07.223520 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:24:37.223330 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:25:07.223335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:25:37.223551 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:26:07.223306 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:26:37.223305 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:27:07.223337 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:27:37.223443 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:28:07.223408 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:28:37.223490 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:29:07.223247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:29:37.223319 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:30:07.223281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:30:37.223451 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:31:07.223292 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:31:37.223364 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:32:07.223367 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:32:37.223323 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:33:07.223345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:33:37.223420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:34:07.223432 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:34:37.223255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:35:07.223280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:35:37.223543 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:36:07.223287 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:36:37.223279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:37:07.223310 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:37:37.223412 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:38:07.223229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:38:37.224250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:39:07.223282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:39:37.223358 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:40:07.223272 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:40:37.223557 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:41:07.223218 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:41:37.223306 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:42:07.223250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:42:37.223258 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:43:07.223276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:43:37.223365 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:44:07.223398 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:44:37.223357 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:44:47.402435 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log
2022/03/10 03:44:52.367004 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:52.367091 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:53.371580 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:53.371617 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:55.377397 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:55.377449 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:59.384816 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:59.384863 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:07.223387 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:45:07.393335 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:07.393511 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:23.411832 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:23.411891 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:37.223371 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:45:55.427506 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:55.427551 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:07.223352 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:46:37.223718 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:46:55.434159 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:55.434204 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:07.223339 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:47:37.223376 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:47:55.437675 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:55.437744 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:07.223277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:48:37.223345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:48:55.442602 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:55.442640 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:07.223275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:49:37.223560 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:49:52.417372 log.go:116: INFO File is inactive: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log. Closing because close_inactive of 5m0s reached.
2022/03/10 03:49:55.446800 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:55.446934 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:07.223469 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:37.223373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:50:55.450369 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:55.450498 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:07.223410 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:51:37.223350 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:51:55.454583 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:55.454746 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:07.223404 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:52:37.223318 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:52:55.459823 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:55.459863 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:07.223265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:53:37.223361 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:53:55.464025 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:55.464068 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:07.223274 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:54:37.223890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:54:55.468427 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:55.468460 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:07.223282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:55:37.223651 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:55:55.473659 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:55.473708 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:07.223291 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:56:37.223345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:56:55.477685 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:55.477732 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:07.223329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:57:37.223355 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:57:55.482237 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:55.482285 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:07.223368 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:58:37.223369 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:58:55.486547 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:55.486592 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:07.223383 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:59:37.223415 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:59:55.491418 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:55.491457 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:07.223303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:00:37.223312 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:00:55.494951 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:55.495017 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:07.223381 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:01:37.223724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:01:55.499308 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:55.499545 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:07.223273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:02:37.223358 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:02:55.504547 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:55.504590 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:07.223341 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:03:37.223325 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:03:55.510643 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:55.511000 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:07.223247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:04:37.223285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:04:55.516036 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:55.516082 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:07.223267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:05:37.223392 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:05:55.521656 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:55.521690 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:07.223260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:06:37.223332 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:06:55.525851 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:55.525885 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:07.223288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:07:37.223354 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:07:55.532019 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:55.532074 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:07.223443 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:08:37.223285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:08:55.536477 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:55.536545 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:07.223263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:09:37.223353 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:09:55.540402 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:55.540438 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:07.223281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:10:37.223337 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:10:55.544888 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:55.544921 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:07.223329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:11:37.223319 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:11:55.548783 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:55.548829 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:07.223533 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:12:37.223292 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:12:55.552024 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:55.552062 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:07.223261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:13:37.223361 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:13:55.555544 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:55.555573 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:07.223301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:14:37.223238 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:14:55.559325 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:55.559381 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:07.223208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:15:37.223321 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:15:55.563438 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:55.563474 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:07.223337 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:16:37.223220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:16:55.568899 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:55.568935 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:07.223308 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:17:37.225710 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:17:55.572840 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:55.572911 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:07.223376 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:18:37.224535 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:18:55.578312 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:55.578370 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:07.223303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:19:37.223295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:19:55.583003 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:55.583173 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:07.223270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:20:37.223384 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:20:55.587482 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:55.587530 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:07.223251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:21:37.223518 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:21:55.591558 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:55.591590 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:07.223331 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:22:37.223309 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:22:55.595952 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:55.595992 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:07.223340 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:23:37.223244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:23:55.600090 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:55.600150 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:07.223338 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:24:37.223274 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:24:55.604483 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:55.604951 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:07.223282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:25:37.223565 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:25:55.610292 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:55.610363 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:07.223263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:26:37.223263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:26:55.614053 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:55.614088 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:07.223320 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:27:37.223790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:27:55.617998 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:55.618040 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:07.223270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:28:37.223317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:28:55.621365 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:55.621407 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:07.223447 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:29:37.223331 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:29:55.624732 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:55.624767 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:07.223439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:30:37.223430 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:30:55.628907 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:55.628945 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:07.223325 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:31:37.223343 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:31:55.632826 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:55.632866 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:07.223267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:32:37.223249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:32:55.637009 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:55.637208 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:07.223458 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:33:37.223383 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:33:55.641356 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:55.641432 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:07.223365 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:34:37.223255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:34:55.645247 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:55.645292 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:07.223359 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:35:37.223337 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:35:55.649423 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:55.649467 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:07.223299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:36:37.223277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:36:55.653734 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:55.653766 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:07.223309 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:37:37.223729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:37:55.656975 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:55.657021 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:07.223305 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:38:37.223304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:38:55.661975 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:55.662034 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:39:07.223537 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 04:39:37.223334 metrics.go:34: INFO No non-zero metrics in the last 30s