2022/03/13 03:18:46.807988 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/13 03:18:46.808060 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/13 03:18:46.808195 metrics.go:23: INFO Metrics logging every 30s
2022/03/13 03:18:46.808188 logstash.go:90: INFO Max Retries set to: 3
2022/03/13 03:18:46.808418 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/13 03:18:46.808950 publish.go:295: INFO Publisher name: onap-vfc-generic-vnfm-driver-757795dcf7-5pgg9
2022/03/13 03:18:46.809442 async.go:63: INFO Flush Interval set to: 1s
2022/03/13 03:18:46.809495 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/13 03:18:46.811756 beat.go:221: INFO filebeat start running.
2022/03/13 03:18:46.811901 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/13 03:18:46.818950 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/13 03:18:46.819751 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/13 03:18:46.819829 crawler.go:38: INFO Loading Prospectors: 1
2022/03/13 03:18:46.819883 registrar.go:236: INFO Starting Registrar
2022/03/13 03:18:46.820017 sync.go:41: INFO Start sending events to output
2022/03/13 03:18:46.820247 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/13 03:18:46.820452 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/13 03:18:46.820500 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/13 03:18:46.820547 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/13 03:18:46.821908 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfmdriver/runtime_gvnfmdriver.log
2022/03/13 03:19:16.808743 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/13 03:19:46.808698 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:20:16.808959 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:20:46.808618 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:21:16.808592 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:21:46.808628 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:22:16.808723 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:22:46.808634 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:23:16.808649 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:23:46.808631 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:23:51.831837 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfmdriver/runtime_gvnfmdriver.log. Closing because close_inactive of 5m0s reached.
2022/03/13 03:24:16.808640 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/13 03:24:46.808606 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:25:16.808609 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:25:46.808612 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:26:16.808615 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:26:46.808562 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:27:16.808838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:27:46.808501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:28:16.809485 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:28:46.808566 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:29:16.808661 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:29:46.808590 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:30:16.808563 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:30:46.808728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:31:16.808601 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:31:46.808565 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:32:16.808611 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:32:46.808697 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:33:16.808678 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:33:46.808549 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:34:16.808737 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:34:46.808662 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:35:16.808675 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:35:46.808536 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:36:16.809105 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:36:46.808537 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:37:16.808656 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:37:46.808554 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:38:16.808618 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:38:46.808578 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:39:16.808560 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:39:46.808613 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:40:16.808751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:40:46.808578 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:41:16.808685 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:41:46.808621 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:42:16.808539 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:42:46.808598 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:43:16.808592 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:43:46.808616 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:44:16.808497 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:44:46.808524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:45:16.808556 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:45:46.808576 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:46:16.808784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:46:46.808686 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:47:16.808590 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:47:46.808600 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:48:06.991620 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfmdriver/runtime_gvnfmdriver.log
2022/03/13 03:48:11.939041 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:11.939084 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:12.942182 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:12.942212 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:14.945454 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:14.945505 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:16.808622 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/13 03:48:18.952632 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:18.952679 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:26.961463 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:26.961531 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:42.980252 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:42.980302 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:46.808649 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:49:15.001259 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:49:15.001323 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:49:16.808585 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:49:46.808566 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:50:15.020041 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:50:15.020104 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:50:16.808537 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:50:46.808599 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:51:15.039710 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:51:15.039759 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:51:16.808604 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:51:46.808536 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:52:15.058760 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:52:15.058813 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:52:16.808526 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:52:46.808532 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:53:12.007910 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfmdriver/runtime_gvnfmdriver.log. Closing because close_inactive of 5m0s reached.
2022/03/13 03:53:15.080194 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:53:15.080266 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:53:16.808670 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/13 03:53:46.808628 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:54:15.097939 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:54:15.097983 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:54:16.808637 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:54:46.808596 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:55:15.115348 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:55:15.115403 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:55:16.809041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:55:46.808515 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:56:15.135377 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:56:15.135429 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:56:16.808541 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:56:46.808560 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:57:15.157089 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:57:15.157136 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:57:16.809184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:57:46.808571 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:58:15.177989 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:58:15.178037 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:58:16.808650 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:58:46.808574 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:59:15.201464 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:59:15.201534 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:59:16.808695 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:59:46.808630 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:00:15.221699 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:00:15.221743 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:00:16.808587 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:00:46.808577 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:01:15.244756 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:01:15.244956 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:01:16.808629 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:01:46.808592 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:02:15.271237 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:02:15.271310 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:02:16.808615 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:02:46.808595 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:03:15.291761 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:03:15.291991 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:03:16.808597 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:03:46.808565 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:04:15.311387 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:04:15.311605 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:04:16.808563 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:04:46.808711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:05:15.333486 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:05:15.333549 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:05:16.808636 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:05:46.808559 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:06:15.353998 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:06:15.354064 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:06:16.808656 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:06:46.808899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:07:15.384021 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:07:15.384063 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:07:16.808588 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:07:46.808666 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:08:15.414549 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:08:15.414613 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:08:16.808553 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:08:46.808646 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:09:15.434715 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:09:15.434804 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:09:16.808572 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:09:46.808562 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:10:15.453846 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:10:15.453896 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:10:16.808593 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:10:46.808620 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:11:15.477437 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:11:15.477482 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:11:16.808548 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:11:46.808531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:12:15.507919 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:12:15.507963 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:12:16.808644 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:12:46.809913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:13:15.527914 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:13:15.528027 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:13:16.808584 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:13:46.808728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:14:15.549673 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:14:15.549723 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:14:16.808598 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:14:46.808827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:15:15.570820 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:15:15.570873 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:15:16.808596 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:15:46.808545 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:16:15.590510 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:16:15.590571 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:16:16.808595 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:16:46.808605 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:17:15.610669 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:17:15.610858 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:17:16.808562 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:17:46.808862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:18:15.631777 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:18:15.631834 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:18:16.808664 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:18:46.808618 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:19:15.650935 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:19:15.650994 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:19:16.808610 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:19:46.808712 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:20:15.669626 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:20:15.669666 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:20:16.808674 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:20:46.808588 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:21:15.688494 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:21:15.688535 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:21:16.808675 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:21:46.808685 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:22:15.707475 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:22:15.707571 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:22:16.808609 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:22:46.808670 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:23:15.726784 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:23:15.726832 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:23:16.808553 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:23:46.808614 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:24:15.746950 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:24:15.746988 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:24:16.808690 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:24:46.808665 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:25:15.767228 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:25:15.767272 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:25:16.808591 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:25:46.808613 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:26:15.788617 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:26:15.788682 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:26:16.808755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:26:46.808794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:27:15.808278 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:27:15.808334 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:27:16.808642 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:27:46.808595 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:28:15.829826 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:28:15.829884 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:28:16.808662 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:28:46.808585 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:29:15.849023 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:29:15.849067 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:29:16.808622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:29:46.808524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:30:15.874666 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:30:15.874710 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:30:16.808625 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:30:46.808518 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:31:15.895227 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:31:15.895275 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:31:16.808554 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:31:46.808538 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:32:15.915187 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:32:15.915233 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:32:16.808580 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:32:46.808612 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:33:15.934011 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:33:15.934057 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:33:16.808773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:33:46.808496 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:34:15.953760 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:34:15.953810 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:34:16.808572 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:34:46.808600 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:35:15.974546 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:35:15.974586 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:35:16.808563 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:35:46.808545 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:36:15.993084 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:36:15.993135 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:36:16.808650 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:36:46.808622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:37:16.014207 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:37:16.014384 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:37:16.808589 metrics.go:34: INFO No non-zero metrics in the last 30s