By type
2022/02/18 02:47:24.438717 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/02/18 02:47:24.438756 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/02/18 02:47:24.438845 logstash.go:90: INFO Max Retries set to: 3
2022/02/18 02:47:24.438924 outputs.go:108: INFO Activated logstash as output plugin.
2022/02/18 02:47:24.439023 publish.go:295: INFO Publisher name: onap-portal-sdk-856bc9b5d4-4c5lf
2022/02/18 02:47:24.439227 async.go:63: INFO Flush Interval set to: 1s
2022/02/18 02:47:24.439256 async.go:64: INFO Max Bulk Size set to: 2048
2022/02/18 02:47:24.439379 metrics.go:23: INFO Metrics logging every 30s
2022/02/18 02:47:24.439695 beat.go:221: INFO filebeat start running.
2022/02/18 02:47:24.439812 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/02/18 02:47:24.653428 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/02/18 02:47:24.653529 registrar.go:123: INFO States Loaded from registrar: 0
2022/02/18 02:47:24.653647 crawler.go:38: INFO Loading Prospectors: 1
2022/02/18 02:47:24.653712 registrar.go:236: INFO Starting Registrar
2022/02/18 02:47:24.653823 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/02/18 02:47:24.653748 sync.go:41: INFO Start sending events to output
2022/02/18 02:47:24.653970 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/02/18 02:47:24.654117 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/02/18 02:47:24.654167 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/02/18 02:47:54.439927 metrics.go:39: INFO Non-zero metrics in the last 30s: registrar.writes=1
2022/02/18 02:48:04.656866 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/02/18 02:48:04.657143 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/02/18 02:48:04.657249 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/02/18 02:48:04.657304 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/02/18 02:48:04.657367 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/02/18 02:48:09.667927 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:48:09.667955 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:48:10.671116 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:48:10.671161 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:48:12.676198 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:48:12.676245 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:48:16.685238 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:48:16.685297 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:48:24.442145 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=5 filebeat.harvester.running=5 filebeat.harvester.started=5 libbeat.publisher.published_events=55
2022/02/18 02:48:24.693560 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:48:24.693607 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:48:40.703031 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:48:40.703075 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:48:54.439712 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 02:49:12.712017 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:49:12.712061 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:49:24.439724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 02:49:54.439880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 02:50:12.750075 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:50:12.750131 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:50:24.439725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 02:50:54.439792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 02:51:12.762455 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:51:12.762490 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:51:24.439690 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 02:51:54.439761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 02:52:12.769726 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:52:12.769755 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:52:24.439700 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 02:52:54.439734 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 02:53:09.668297 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/02/18 02:53:12.780854 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:53:12.780906 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:53:24.439788 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/02/18 02:53:24.668626 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/02/18 02:53:24.668680 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/02/18 02:53:24.668624 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/02/18 02:53:54.439675 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-3
2022/02/18 02:54:12.819977 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:54:12.820016 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:54:24.439635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 02:54:54.439912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 02:55:12.831128 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:55:12.831175 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:55:24.439795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 02:55:54.439687 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 02:56:12.841346 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:56:12.841394 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:56:24.439794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 02:56:54.439753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 02:57:12.851400 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:57:12.851427 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:57:24.439780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 02:57:54.439657 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 02:58:12.861477 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:58:12.861515 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:58:24.439655 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 02:58:54.439754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 02:59:12.872925 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:59:12.872962 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:59:24.439612 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 02:59:54.439708 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:00:12.880912 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:00:12.880955 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:00:24.439682 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:00:54.439800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:01:12.890019 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:01:12.890064 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:01:24.439757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:01:54.439778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:02:12.900432 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:02:12.900484 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:02:24.439705 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:02:54.439690 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:03:12.909912 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:03:12.909953 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:03:24.439798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:03:54.440154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:04:12.918799 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:04:12.918841 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:04:24.439773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:04:54.439699 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:05:12.927841 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:05:12.927893 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:05:24.439712 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:05:54.439692 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:06:12.938603 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:06:12.938642 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:06:24.439760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:06:54.439775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:07:12.968830 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:07:12.968854 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:07:24.439745 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:07:54.439759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:08:12.976589 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:08:12.976718 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:08:24.439677 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:08:54.439734 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:09:12.986029 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:09:12.986077 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:09:24.439736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:09:54.439753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:10:12.995841 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:10:12.995874 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:10:24.439841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:10:54.439792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:11:13.004082 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:11:13.004115 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:11:24.439686 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:11:54.439681 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:12:13.014535 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:12:13.014572 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:12:24.439858 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:12:54.439874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:13:13.023727 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:13:13.023778 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:13:24.439806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:13:54.439732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:14:13.033653 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:14:13.033681 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:14:24.439746 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:14:54.439684 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:15:13.043310 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:15:13.043373 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:15:24.439654 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:15:54.439708 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:16:13.052026 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:16:13.052066 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:16:24.439719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:16:54.439670 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:17:13.060714 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:17:13.060749 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:17:24.439785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:17:54.439776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:18:13.069967 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:18:13.070008 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:18:24.439757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:18:54.439789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:19:13.079679 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:19:13.079729 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:19:24.439680 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:19:54.439650 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:20:13.088702 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:20:13.088750 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:20:24.439710 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:20:54.439726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:21:13.097260 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:21:13.097287 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:21:24.439582 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:21:54.439779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:22:13.106624 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:22:13.106665 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:22:24.439652 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:22:54.439640 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:23:13.116798 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:23:13.116838 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:23:24.439746 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:23:54.439733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:24:13.126376 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:24:13.126415 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:24:24.439791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:24:54.439824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:25:13.137537 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:25:13.137579 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:25:24.439777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:25:54.439756 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:26:13.147731 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:26:13.147784 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:26:24.439855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:26:54.439749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:27:13.156200 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:27:13.156221 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:27:24.439784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:27:54.439726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:28:13.166629 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:28:13.166685 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:28:24.439744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:28:54.439659 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:29:13.176091 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:29:13.176134 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:29:24.439721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:29:54.439807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:30:13.185480 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:30:13.185513 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:30:24.439749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:30:54.439807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:31:13.197349 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:31:13.197411 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:31:24.439691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:31:54.439730 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:32:13.207396 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:32:13.207425 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:32:24.439621 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:32:54.439713 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:33:13.217036 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:33:13.217074 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:33:24.439713 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:33:54.439765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:34:13.226352 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:34:13.226407 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:34:24.439722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:34:54.439716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:35:13.236062 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:35:13.236090 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:35:24.439807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:35:54.439711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:36:13.245842 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:36:13.245879 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:36:24.439854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:36:54.439755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:37:13.257685 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:37:13.257728 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:37:24.439739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:37:54.439736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:38:13.267348 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:38:13.267384 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:38:24.439745 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:38:54.439806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:39:13.277572 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:39:13.277621 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:39:24.439764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:39:54.439811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:40:13.289199 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:40:13.289232 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:40:24.439707 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:40:54.439766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:41:13.297412 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:41:13.297443 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:41:24.439740 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:41:54.439830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:42:13.306779 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:42:13.306823 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:42:24.439707 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:42:54.439739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:43:13.316999 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:43:13.317038 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:43:24.439792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:43:54.439732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:44:13.327212 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:44:13.327264 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:44:24.439853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:44:54.439607 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:45:13.335943 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:45:13.335991 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:45:24.439682 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:45:54.439655 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:46:13.347405 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:46:13.347437 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:46:24.439785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:46:54.439777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:47:13.357193 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:47:13.357235 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:47:24.439792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:47:54.439833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:48:13.368114 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:48:13.368161 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:48:24.439813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:48:54.439685 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:49:13.378557 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:49:13.378593 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:49:24.441017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:49:54.439839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:50:13.387679 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:50:13.387717 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:50:24.439667 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:50:54.439705 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:51:13.397431 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:51:13.397478 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:51:24.439816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:51:54.439644 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:52:13.407952 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:52:13.407989 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:52:24.439686 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:52:54.439707 metrics.go:34: INFO No non-zero metrics in the last 30s