By type
2022/03/13 03:18:50.770433 metrics.go:23: INFO Metrics logging every 30s
2022/03/13 03:18:50.770317 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:50.770502 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/13 03:18:50.770621 logstash.go:90: INFO Max Retries set to: 3
2022/03/13 03:18:50.770746 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/13 03:18:50.770993 publish.go:295: INFO Publisher name: onap-vfc-vnfmgr-8594ffd488-wjhxg
2022/03/13 03:18:50.771488 async.go:63: INFO Flush Interval set to: 1s
2022/03/13 03:18:50.771518 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/13 03:18:50.772089 beat.go:221: INFO filebeat start running.
2022/03/13 03:18:50.772151 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/13 03:18:50.776036 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/13 03:18:50.776104 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/13 03:18:50.776137 crawler.go:38: INFO Loading Prospectors: 1
2022/03/13 03:18:50.776158 registrar.go:236: INFO Starting Registrar
2022/03/13 03:18:50.776364 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/13 03:18:50.776460 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/13 03:18:50.776488 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/13 03:18:50.776516 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/13 03:18:50.776631 sync.go:41: INFO Start sending events to output
2022/03/13 03:18:50.778931 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnfmgr/runtime_mgr.log
2022/03/13 03:19:20.772033 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:50.770924 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:20:20.770783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:20:50.770772 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:21:20.770739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:21:50.771437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:22:20.770900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:22:50.770903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:23:20.770776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:23:50.770992 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:23:55.790089 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfm-vnfmgr/runtime_mgr.log. Closing because close_inactive of 5m0s reached.
2022/03/13 03:24:20.770872 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:50.770786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:25:20.770784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:25:50.770788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:26:20.770863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:26:50.770776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:27:20.770850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:27:50.770736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:28:20.770811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:28:50.770749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:29:20.770846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:29:50.770841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:30:20.770974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:30:50.770820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:31:20.770720 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:31:50.770736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:32:20.770816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:32:50.770786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:33:20.770789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:33:50.770718 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:34:20.771022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:34:50.774596 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:35:20.770800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:35:50.770795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:36:20.770794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:36:50.770721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:37:20.770786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:37:50.770766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:38:20.771024 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:38:50.770982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:39:20.770925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:39:50.770819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:40:20.770777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:40:50.770773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:41:20.770810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:41:50.770747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:42:20.770688 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:42:50.770789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:43:20.771038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:43:50.770798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:44:20.770915 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:44:50.770746 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:45:20.770718 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:45:50.770770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:46:20.770741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:46:50.770701 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:47:20.771381 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:47:50.770771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:48:10.929841 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnfmgr/runtime_mgr.log
2022/03/13 03:48:15.890605 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:15.890636 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.895759 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:16.895802 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:18.901916 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.901984 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:20.770819 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:22.906633 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:22.906664 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:30.910990 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:30.911027 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.926552 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:46.926591 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:50.770791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:49:18.940733 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:18.940766 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:20.776699 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:49:50.770733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:50:18.944468 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:18.944509 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:20.770772 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:50:50.770871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:51:18.948926 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:18.948963 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:20.770740 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:51:50.770849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:52:18.953064 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:18.953244 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:20.770979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:52:50.770840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:53:15.954154 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfm-vnfmgr/runtime_mgr.log. Closing because close_inactive of 5m0s reached.
2022/03/13 03:53:18.957234 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:18.957280 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:20.770829 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:50.770808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:54:18.960735 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:18.961073 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:20.770756 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:54:50.770896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:55:18.964220 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:18.964258 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:20.770709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:55:50.770965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:56:18.968644 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:18.968683 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:20.770944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:56:50.770744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:57:18.973058 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:18.973090 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:20.770914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:57:50.770781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:58:18.976594 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:18.976629 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:20.770783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:58:50.771073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:59:18.980807 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:18.980842 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:20.771118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:59:50.770755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:00:18.984790 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:18.984834 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:20.770808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:00:50.770822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:01:18.988880 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:18.988931 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:20.770953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:01:50.770744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:02:18.992802 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:18.993148 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:20.770803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:02:50.770751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:03:18.997788 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:18.997827 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:20.770786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:03:50.770892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:04:19.002836 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:19.002879 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:20.770964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:04:50.771121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:05:19.006440 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:19.006471 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:20.771170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:05:50.771850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:06:19.015158 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:19.015197 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:20.771177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:06:50.771238 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:07:19.019078 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:19.019115 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:20.770720 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:07:50.770758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:08:19.024597 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:19.024638 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:20.770825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:08:50.770731 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:09:19.028384 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:19.028692 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:20.770793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:09:50.770810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:10:19.032347 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:19.032389 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:20.770758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:10:50.770795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:11:19.035765 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:19.035795 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:20.771257 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:11:50.770981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:12:19.040537 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:19.040607 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:20.770831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:12:50.770896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:13:19.044816 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:19.044856 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:20.770791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:13:50.770747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:14:19.049932 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:19.049970 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:20.770768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:14:50.770816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:15:19.054333 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:19.054372 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:20.770783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:15:50.770732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:16:19.058149 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:19.058185 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:20.770844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:16:50.770766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:17:19.061314 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:19.061347 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:20.770849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:17:50.770776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:18:19.066755 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:19.066837 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:20.770865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:18:50.770926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:19:19.071846 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:19.072214 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:20.770901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:19:50.770746 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:20:19.077296 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:19.077332 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:20.770825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:20:50.770882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:21:19.081267 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:19.081303 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:20.770907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:21:50.770878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:22:19.087113 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:19.087181 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:20.770781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:22:50.770867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:23:19.091487 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:19.091526 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:20.770819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:23:50.771373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:24:19.095668 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:19.095724 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:20.770747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:24:50.770836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:25:19.101289 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:19.101321 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:20.774898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:25:50.770802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:26:19.105851 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:19.105927 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:20.770794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:26:50.770846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:27:19.109933 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:19.110057 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:20.770896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:27:50.770823 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:28:19.113856 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:19.113895 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:20.770765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:28:50.770881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:29:19.117553 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:19.117584 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:20.770783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:29:50.770773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:30:19.121783 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:19.121817 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:20.770743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:30:50.771157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:31:19.126122 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:19.126180 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:20.770800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:31:50.770833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:32:19.131527 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:19.131566 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:20.770781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:32:50.770770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:33:19.134830 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:19.134877 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:20.770975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:33:50.770717 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:34:19.138169 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:19.138216 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:20.770846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:34:50.770944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:35:19.144304 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:19.144359 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:20.771639 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:35:50.770942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:36:19.150744 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:19.150835 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:20.770790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:36:50.770732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:37:19.156930 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:19.156988 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:20.770897 metrics.go:34: INFO No non-zero metrics in the last 30s