By type
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
2022/02/15 03:50:06.194259 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:50:06.194292 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:50:17.795827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:50:47.795870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:51:06.200397 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:51:06.200443 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:51:17.795797 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:51:47.795862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:52:06.205968 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:52:06.206001 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:52:17.795822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:52:47.795833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:53:06.212286 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:53:06.212324 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:53:17.795929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:53:47.795882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:54:06.217153 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:54:06.217186 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:54:17.795817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:54:47.795820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:55:06.227003 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:55:06.227047 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:55:17.795835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:55:47.795820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:56:06.233205 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:56:06.233261 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:56:17.795843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:56:47.795843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:57:06.240152 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:57:06.240185 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:57:17.795822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:57:47.795804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:58:06.245798 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:58:06.245838 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:58:17.795775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:58:47.795824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:59:06.251999 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:59:06.252029 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:59:17.795813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 03:59:47.795868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:00:06.257807 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:00:06.257835 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:00:17.795832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:00:47.795831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:01:06.263561 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:01:06.263594 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:01:17.795814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:01:47.795812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:02:06.268751 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:02:06.268782 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:02:17.795793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:02:47.795927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:03:06.274184 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:03:06.274217 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:03:17.795811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:03:47.795782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:04:06.280393 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:04:06.280422 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:04:17.795827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:04:47.795835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:05:06.286600 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:05:06.286635 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:05:17.795795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:05:47.795788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:06:06.291942 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:06:06.291969 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:06:17.795828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:06:47.795898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:07:06.297572 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:07:06.297604 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:07:17.795783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:07:47.795858 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:08:06.302720 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:08:06.302752 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:08:17.795773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:08:47.795852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:09:06.308376 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:09:06.308402 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:09:17.795806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:09:47.795792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:10:06.314337 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:10:06.314376 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:10:17.795866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:10:47.795900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:11:06.320355 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:11:06.320390 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:11:17.795820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:11:47.795798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:12:06.325602 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:12:06.325715 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:12:17.795807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:12:47.795792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:13:06.331793 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:13:06.331836 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:13:17.795803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:13:47.795842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:14:06.337236 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:14:06.337264 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:14:17.795829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:14:47.795793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:15:06.343221 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:15:06.343251 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:15:17.795838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:15:47.795801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:16:06.348931 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:16:06.348959 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:16:17.795853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:16:47.795862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:17:06.354779 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:17:06.354809 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:17:17.795883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:17:47.795813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:18:06.360346 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:18:06.360390 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:18:17.795761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:18:47.795824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:19:06.366795 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:19:06.366840 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:19:17.795866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:19:47.795787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:20:06.372788 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:20:06.372840 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:20:17.795831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:20:47.796482 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:21:06.379532 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:21:06.379570 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:21:17.795837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:21:47.795835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:22:06.384662 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:22:06.384696 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:22:17.795831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:22:47.795801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:23:06.390269 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:23:06.390299 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:23:17.795795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:23:47.795889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:24:06.396389 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:24:06.396424 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:24:17.795809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:24:47.795895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:25:06.402120 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:25:06.402164 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:25:17.795941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:25:47.795906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:26:06.408509 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:26:06.408557 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:26:17.795853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:26:47.795818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:27:06.414499 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:27:06.414528 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:27:17.795836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:27:47.795817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:28:06.419750 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:28:06.419778 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:28:17.795786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:28:47.795863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:29:06.428479 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:29:06.428513 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:29:17.795837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:29:47.795809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:30:06.434304 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:30:06.434341 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:30:17.795767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:30:47.795819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:31:06.440478 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:31:06.440637 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:31:17.795886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:31:47.795832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:32:06.447624 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:32:06.447657 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:32:17.795864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:32:47.795850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:33:06.453743 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:33:06.453780 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:33:17.795871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:33:47.795832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:34:06.459646 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:34:06.459687 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:34:17.795925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:34:47.795863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:35:06.465693 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:35:06.465725 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:35:17.795770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:35:47.795853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:36:06.471563 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:36:06.471614 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:36:17.795839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:36:47.795819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:37:06.478573 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:37:06.478604 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:37:17.795873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:37:47.795805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:38:06.484234 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:38:06.484265 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:38:17.795882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:38:47.795924 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:39:06.490687 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:39:06.490719 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:39:17.795831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:39:47.795814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:40:06.497758 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:40:06.497787 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:40:17.795841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:40:47.795951 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:41:06.502887 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:41:06.502915 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:41:17.795815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:41:47.795800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:42:06.542527 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:42:06.542554 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:42:17.795837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:42:47.795820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:43:06.548944 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:43:06.548973 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:43:17.795790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:43:47.795816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:44:06.553776 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:44:06.553803 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:44:17.795817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:44:47.795855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:45:06.559799 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:45:06.559829 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:45:17.795883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:45:47.795792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:46:06.564789 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:46:06.564818 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:46:17.795801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:46:47.795833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:47:06.571423 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:47:06.571458 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:47:17.795851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:47:47.795847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:48:06.577128 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:48:06.577162 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:48:17.795848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:48:47.795818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:49:06.582744 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:49:06.582788 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:49:17.795839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:49:47.795835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:50:06.588530 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:50:06.588557 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:50:17.795805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:50:47.795821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:51:06.594222 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:51:06.594248 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:51:17.795801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:51:47.795777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:52:06.600111 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:52:06.600135 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:52:17.795892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:52:47.795791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:53:06.605511 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:53:06.605537 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:53:17.795820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:53:47.795864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:54:06.611158 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:54:06.611189 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:54:17.795825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:54:47.795869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:55:06.616611 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:55:06.616644 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:55:17.795812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:55:47.795828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:56:06.621932 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:56:06.621965 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:56:17.795932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:56:47.795843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:57:06.627820 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:57:06.627847 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:57:17.795824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:57:47.795776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:58:06.635485 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:58:06.635524 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:58:17.795832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:58:47.795855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:59:06.641486 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:59:06.641514 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 04:59:17.795833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 04:59:47.795780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 05:00:06.647045 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 05:00:06.647074 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 05:00:17.795812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 05:00:47.795859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 05:01:06.653298 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 05:01:06.653330 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 05:01:17.795858 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 05:01:47.795752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 05:02:06.659992 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 05:02:06.660095 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 05:02:17.795784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 05:02:47.795818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/15 05:03:06.665068 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 05:03:06.665095 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/15 05:03:17.795776 metrics.go:34: INFO No non-zero metrics in the last 30s