2022/02/15 02:55:47.795407 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/15 02:55:47.795450 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/02/15 02:55:47.795507 logstash.go:90: INFO Max Retries set to: 3
2022/02/15 02:55:47.795516 metrics.go:23: INFO Metrics logging every 30s
2022/02/15 02:55:47.795577 outputs.go:108: INFO Activated logstash as output plugin.
2022/02/15 02:55:47.795690 publish.go:295: INFO Publisher name: onap-portal-app-9c5c78dc6-xmdjq
2022/02/15 02:55:47.795849 async.go:63: INFO Flush Interval set to: 1s
2022/02/15 02:55:47.795869 async.go:64: INFO Max Bulk Size set to: 2048
2022/02/15 02:55:47.796299 beat.go:221: INFO filebeat start running.
2022/02/15 02:55:47.796391 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/02/15 02:55:47.906612 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/02/15 02:55:47.906661 registrar.go:123: INFO States Loaded from registrar: 0
2022/02/15 02:55:47.906706 registrar.go:236: INFO Starting Registrar
2022/02/15 02:55:47.906830 crawler.go:38: INFO Loading Prospectors: 1
2022/02/15 02:55:47.906823 sync.go:41: INFO Start sending events to output
2022/02/15 02:55:47.906940 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/02/15 02:55:47.907154 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/02/15 02:55:47.907319 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/02/15 02:55:47.907353 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/02/15 02:55:57.908273 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/02/15 02:55:57.908407 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/02/15 02:55:57.908412 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/02/15 02:55:57.908565 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/02/15 02:55:57.908668 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/02/15 02:56:02.911443 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 02:56:02.911482 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 02:56:03.917895 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 02:56:03.917924 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 02:56:05.920452 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 02:56:05.920480 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 02:56:09.926571 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 02:56:09.926600 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 02:56:17.795863 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=72 registrar.writes=1
2022/02/15 02:56:17.929140 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 02:56:17.929172 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 02:56:33.931940 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 02:56:33.931972 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 02:56:47.795875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 02:57:05.935705 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 02:57:05.935736 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 02:57:17.795871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 02:57:47.795848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 02:58:05.938512 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 02:58:05.938536 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 02:58:17.795832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 02:58:47.795773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 02:59:05.942055 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 02:59:05.942108 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 02:59:17.795817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 02:59:47.795859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:00:05.945828 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:00:05.945855 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:00:17.795853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:00:47.795836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:01:02.924153 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/02/15 03:01:05.948401 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:01:05.948431 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:01:17.795845 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/02/15 03:01:47.795875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:02:05.951007 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:02:05.951032 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:02:17.795843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:02:47.795816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:03:05.955273 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:03:05.955321 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:03:17.796122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:03:47.795806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:04:05.957829 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:04:05.957855 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:04:17.795794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:04:47.795818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:05:05.965838 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:05:05.965868 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:05:17.795815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:05:47.795810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:06:05.969394 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:06:05.969484 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:06:17.795850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:06:47.795966 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:07:05.973529 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:07:05.973564 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:07:17.795909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:07:47.795892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:08:05.977069 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:08:05.977105 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:08:17.795961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:08:47.795917 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:09:05.980775 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:09:05.980841 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:09:17.795804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:09:47.795799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:10:05.984606 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:10:05.984631 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:10:17.795932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:10:47.795824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:11:05.988462 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:11:05.988494 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:11:17.795844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:11:47.795768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:12:05.992647 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:12:05.992692 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:12:17.796169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:12:47.795823 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:13:05.996080 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:13:05.996116 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:13:17.795858 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:13:47.795776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:14:06.000091 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:14:06.000124 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:14:17.795851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:14:47.795808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:15:06.003694 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:15:06.003791 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:15:17.795788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:15:47.795791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:16:06.007675 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:16:06.007715 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:16:17.795799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:16:47.795821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:17:06.011172 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:17:06.011204 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:17:17.795793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:17:47.795797 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:18:06.014875 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:18:06.014945 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:18:17.795869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:18:47.795827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:19:06.018658 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:19:06.018690 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:19:17.795844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:19:47.795834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:20:06.022491 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:20:06.022520 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:20:17.795784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:20:47.795867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:21:06.026115 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:21:06.026143 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:21:17.795760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:21:47.795843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:22:06.028883 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:22:06.028904 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:22:17.795787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:22:47.795819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:23:06.032782 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:23:06.032813 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:23:17.795838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:23:47.795818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:24:06.038491 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:24:06.038514 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:24:17.795817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:24:47.795841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:25:06.044155 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:25:06.044198 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:25:17.795778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:25:47.795829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:26:06.050313 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:26:06.050336 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:26:17.795800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:26:47.795895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:27:06.056218 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:27:06.056253 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:27:17.795824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:27:47.795893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:28:06.062150 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:28:06.062175 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:28:17.795875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:28:47.795815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:29:06.069122 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:29:06.069160 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:29:17.795820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:29:47.795798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:30:06.074414 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:30:06.074455 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:30:17.795859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:30:47.795838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:31:06.079588 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:31:06.079617 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:31:17.795817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:31:47.795782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:32:06.085581 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:32:06.085615 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:32:17.795812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:32:47.795839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:33:06.091910 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:33:06.091940 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:33:17.795899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:33:47.795813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:34:06.096830 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:34:06.096855 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:34:17.795821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:34:47.795788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:35:06.102960 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:35:06.102990 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:35:17.795822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:35:47.795881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:36:06.108784 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:36:06.108822 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:36:17.795786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:36:47.795941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:37:06.114516 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:37:06.114546 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:37:17.795858 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:37:47.795832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:38:06.120839 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:38:06.120870 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:38:17.795831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:38:47.795818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:39:06.126133 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:39:06.126175 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:39:17.795853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:39:47.795792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:40:06.131642 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:40:06.131678 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:40:17.795867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:40:47.795838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:41:06.137708 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:41:06.137739 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:41:17.795854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:41:47.795794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:42:06.144391 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:42:06.144422 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:42:17.795897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:42:47.795790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:43:06.150520 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:43:06.150551 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:43:17.795814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:43:47.795829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:44:06.156826 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:44:06.156944 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:44:17.795807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:44:47.795912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:45:06.163238 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:45:06.163280 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:45:17.795810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:45:47.795859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:46:06.170089 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:46:06.170128 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:46:17.795822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:46:47.795857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:47:06.175616 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:47:06.175648 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:47:17.795822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:47:47.795849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:48:06.182575 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:48:06.182611 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:48:17.795865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:48:47.795848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:49:06.188305 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:49:06.188336 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 03:49:17.795835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:49:47.795828 metrics.go:34: INFO No non-zero metrics in the last 30s