Results

          2022/03/24 03:13:22.666884 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:13:22.666936 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/24 03:13:22.667019 logstash.go:90: INFO Max Retries set to: 3
2022/03/24 03:13:22.667112 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/24 03:13:22.667256 metrics.go:23: INFO Metrics logging every 30s
2022/03/24 03:13:22.667272 publish.go:295: INFO Publisher name: onap-vfc-generic-vnfm-driver-757795dcf7-th8fr
2022/03/24 03:13:22.667852 async.go:63: INFO Flush Interval set to: 1s
2022/03/24 03:13:22.667889 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/24 03:13:22.668729 beat.go:221: INFO filebeat start running.
2022/03/24 03:13:22.668848 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/24 03:13:22.676432 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/24 03:13:22.676545 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/24 03:13:22.676613 crawler.go:38: INFO Loading Prospectors: 1
2022/03/24 03:13:22.676783 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/24 03:13:22.676881 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/24 03:13:22.676903 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/24 03:13:22.676920 registrar.go:236: INFO Starting Registrar
2022/03/24 03:13:22.676955 sync.go:41: INFO Start sending events to output
2022/03/24 03:13:22.677002 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/24 03:13:22.677716 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfmdriver/runtime_gvnfmdriver.log
2022/03/24 03:13:52.667707 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:14:22.667640 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:14:52.667700 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:15:22.667743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:15:52.667669 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:16:22.667703 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:16:52.667974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:17:22.667707 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:17:52.667675 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:18:22.667631 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:18:27.701560 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfmdriver/runtime_gvnfmdriver.log. Closing because close_inactive of 5m0s reached.
2022/03/24 03:18:52.668229 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:19:22.667747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:19:52.667797 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:20:22.667810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:20:52.667913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:21:22.667618 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:21:52.667701 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:22:22.667762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:22:52.667932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:23:22.668240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:23:52.667659 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:24:22.667831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:24:52.667611 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:25:22.667582 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:25:52.668020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:26:22.667648 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:26:52.667585 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:27:22.667671 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:27:52.667670 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:28:22.667830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:28:52.667683 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:29:22.667639 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:29:52.667599 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:30:22.667645 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:30:52.667673 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:31:22.667626 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:31:52.667709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:32:22.667607 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:32:52.667550 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:33:22.667741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:33:52.667703 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:34:22.667685 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:34:52.667583 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:35:22.667682 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:35:52.667605 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:36:22.667700 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:36:52.667688 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:37:22.667715 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:37:52.667703 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:38:22.667617 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:38:52.667690 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:39:22.667650 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:39:52.667617 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:40:12.841678 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfmdriver/runtime_gvnfmdriver.log
2022/03/24 03:40:17.818271 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:17.818626 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:18.822278 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:18.822311 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:20.825611 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:20.825643 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:22.667751 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:24.835393 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:24.835431 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:32.842332 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:32.842387 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:48.859929 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:48.860081 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:52.667601 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:41:20.879492 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:20.879530 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:22.667674 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:41:52.667782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:42:20.908391 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:20.908426 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:22.668234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:42:52.667617 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:43:20.926888 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:20.927030 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:22.667607 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:43:52.667721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:44:20.945224 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:20.945280 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:22.667663 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:44:52.667756 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:45:17.854920 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfmdriver/runtime_gvnfmdriver.log. Closing because close_inactive of 5m0s reached.
2022/03/24 03:45:20.964780 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:20.964813 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:22.667801 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:45:52.667754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:46:20.984752 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:20.984831 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:22.667754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:46:52.667606 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:47:21.004484 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:21.004525 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:22.667625 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:47:52.667725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:48:21.023023 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:21.023086 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:22.667656 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:48:52.667597 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:49:21.043253 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:21.043295 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:22.667677 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:49:52.667659 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:50:21.063239 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:21.063294 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:22.667714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:50:52.667694 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:51:21.084354 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:21.084415 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:22.667669 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:51:52.667732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:52:21.103849 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:21.103917 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:22.667715 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:52:52.667612 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:53:21.121667 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:21.121702 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:22.667640 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:53:52.667942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:54:21.140083 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:21.140149 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:22.667682 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:54:52.668605 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:55:21.158416 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:21.158460 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:22.667652 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:55:52.667604 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:56:21.177373 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:21.177432 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:22.667616 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:56:52.667582 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:57:21.196273 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:21.196432 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:22.667550 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:57:52.667592 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:58:21.216973 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:21.217011 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:22.667740 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:58:52.667753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:59:21.236998 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:21.237038 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:22.667647 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:59:52.667719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:00:21.255649 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:21.255962 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:22.667734 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:00:52.667896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:01:21.302428 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:21.302484 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:22.667725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:01:52.667746 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:02:21.319586 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:21.319621 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:22.667733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:02:52.668095 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:03:21.341423 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:21.341465 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:22.667639 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:03:52.667654 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:04:21.369890 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:21.370186 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:22.667650 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:04:52.667737 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:05:21.392222 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:21.392253 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:22.667636 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:05:52.667641 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:06:21.413544 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:21.413578 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:22.667707 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:06:52.667695 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:07:21.433601 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:21.433654 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:22.667578 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:07:52.667721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:08:21.460493 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:21.460531 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:22.667701 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:08:52.667627 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:09:21.479420 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:21.479465 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:22.669133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:09:52.667665 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:10:21.497687 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:21.497727 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:22.667589 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:10:52.667639 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:11:21.516732 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:21.516904 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:22.667702 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:11:52.667667 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:12:21.535192 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:21.535240 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:22.667686 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:12:52.667696 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:13:21.552415 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:21.552583 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:22.668986 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:13:52.667652 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:14:21.572183 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:21.572421 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:22.667811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:14:52.667612 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:15:21.591186 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:21.591219 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:22.667575 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:15:52.667615 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:16:21.614303 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:21.614338 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:22.667603 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:16:52.667691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:17:21.633057 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:21.633117 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:22.667683 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:17:52.667668 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:18:21.651096 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:21.651135 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:22.667720 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:18:52.667732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:19:21.668954 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:21.668997 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:22.667588 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:19:52.667695 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:20:21.687160 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:21.687196 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:22.667743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:20:52.667660 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:21:21.704325 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:21.704366 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:22.668636 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:21:52.667682 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:22:21.724050 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:21.724095 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:22.667804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:22:52.667629 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:23:21.748905 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:21.748978 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:22.667660 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:23:52.667703 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:24:21.770046 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:21.770106 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:22.667792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:24:52.667596 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:25:21.789059 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:21.789096 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:22.667684 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:25:52.667613 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:26:21.808522 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:21.808561 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:22.667619 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:26:52.667650 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:27:21.827138 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:21.827188 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:22.667694 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:27:52.667617 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:28:21.844972 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:21.845011 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:22.667721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:28:52.667670 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:29:21.863677 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:21.863722 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:22.667640 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:29:52.667785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:30:21.883491 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:21.883542 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:22.667684 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:30:52.667792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:31:21.904305 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:21.904340 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:22.667716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:31:52.667695 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:32:21.926200 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:21.926260 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:22.667622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:32:52.667604 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:33:21.946889 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:21.947029 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:22.667711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:33:52.667761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:34:21.964973 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:21.965109 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:22.667705 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:34:52.667586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:35:21.984569 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:21.984613 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:22.667628 metrics.go:34: INFO No non-zero metrics in the last 30s