By type
2022/04/11 03:04:01.899365 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/04/11 03:04:01.899447 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/04/11 03:04:01.899624 logstash.go:90: INFO Max Retries set to: 3
2022/04/11 03:04:01.899755 outputs.go:108: INFO Activated logstash as output plugin.
2022/04/11 03:04:01.899935 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-fzxqk
2022/04/11 03:04:01.900421 metrics.go:23: INFO Metrics logging every 30s
2022/04/11 03:04:01.900427 async.go:63: INFO Flush Interval set to: 1s
2022/04/11 03:04:01.900492 async.go:64: INFO Max Bulk Size set to: 2048
2022/04/11 03:04:01.901263 beat.go:221: INFO filebeat start running.
2022/04/11 03:04:01.901425 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/04/11 03:04:01.909351 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/04/11 03:04:01.909441 registrar.go:123: INFO States Loaded from registrar: 0
2022/04/11 03:04:01.909480 crawler.go:38: INFO Loading Prospectors: 1
2022/04/11 03:04:01.909689 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/04/11 03:04:01.909777 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/04/11 03:04:01.909799 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/04/11 03:04:01.909820 registrar.go:236: INFO Starting Registrar
2022/04/11 03:04:01.909863 sync.go:41: INFO Start sending events to output
2022/04/11 03:04:01.909913 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/04/11 03:04:21.914590 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/04/11 03:04:21.914717 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/04/11 03:04:21.914982 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/04/11 03:04:21.915070 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/04/11 03:04:21.915147 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/04/11 03:04:26.934125 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:04:26.934185 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:04:27.938720 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:04:27.938855 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:04:29.947070 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:04:29.947107 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:04:31.901589 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=76 registrar.writes=1
2022/04/11 03:04:33.953912 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:04:33.953975 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:04:41.966445 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:04:41.966478 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:04:57.986681 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:04:57.986723 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:05:01.900694 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:05:30.006396 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:05:30.006510 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:05:31.900791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:06:01.900833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:06:30.022490 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:06:30.022534 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:06:31.900737 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:07:01.900715 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:07:30.041145 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:07:30.041193 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:07:31.900778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:08:01.900859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:08:30.056713 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:08:30.057030 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:08:31.900742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:09:01.900710 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:09:26.936529 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/04/11 03:09:30.075366 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:09:30.075410 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:09:31.900823 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/04/11 03:10:01.900725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:10:30.092925 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:10:30.092957 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:10:31.900752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:11:01.900729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:11:30.110661 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:11:30.110805 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:11:31.900808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:12:01.900776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:12:30.128168 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:12:30.128237 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:12:31.900771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:13:01.900808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:13:30.145521 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:13:30.145559 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:13:31.900780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:14:01.900713 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:14:30.161472 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:14:30.161608 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:14:31.900836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:15:01.900688 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:15:30.180989 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:15:30.181034 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:15:31.901422 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:16:01.900732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:16:30.197720 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:16:30.197769 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:16:31.900738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:17:01.900714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:17:30.213996 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:17:30.214048 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:17:31.900786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:18:01.900926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:18:30.231608 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:18:30.231659 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:18:31.900766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:19:01.900716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:19:30.249512 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:19:30.249567 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:19:31.900786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:20:01.900775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:20:30.267126 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:20:30.267253 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:20:31.900744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:21:01.900827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:21:30.284657 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:21:30.284699 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:21:31.900821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:22:01.900813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:22:30.305226 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:22:30.305265 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:22:31.900741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:23:01.900785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:23:30.325004 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:23:30.325041 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:23:31.900948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:24:01.900755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:24:30.342150 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:24:30.342184 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:24:31.900858 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:25:01.900797 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:25:30.360056 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:25:30.360232 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:25:31.900733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:26:01.900782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:26:30.378747 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:26:30.378801 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:26:31.900841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:27:01.900744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:27:30.396059 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:27:30.396097 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:27:31.900804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:28:01.900814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:28:30.414396 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:28:30.414434 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:28:31.900697 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:29:01.900890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:29:30.431404 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:29:30.431435 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:29:31.900817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:30:01.900751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:30:30.450742 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:30:30.450828 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:30:31.900749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:31:01.900726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:31:30.466823 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:31:30.466857 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:31:31.900781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:32:01.900800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:32:30.483193 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:32:30.483247 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:32:31.900817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:33:01.900728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:33:30.500284 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:33:30.500323 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:33:31.900771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:34:01.900755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:34:30.517650 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:34:30.517701 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:34:31.900751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:35:01.900954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:35:30.536169 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:35:30.536274 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:35:31.900709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:36:01.900887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:36:30.554845 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:36:30.554879 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:36:31.900801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:37:01.900798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:37:30.571843 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:37:30.571881 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:37:31.900825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:38:01.900783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:38:30.590218 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:38:30.590252 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:38:31.900843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:39:01.900881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:39:30.607551 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:39:30.607592 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:39:31.900794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:40:01.900843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:40:30.625773 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:40:30.625823 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:40:31.900819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:41:01.900779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:41:30.644197 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:41:30.644232 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:41:31.900743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:42:01.900710 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:42:30.662117 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:42:30.662152 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:42:31.901622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:43:01.900744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:43:30.683275 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:43:30.683323 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:43:31.900795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:44:01.900779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:44:30.701669 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:44:30.701718 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:44:31.900811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:45:01.900709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:45:30.718925 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:45:30.718970 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:45:31.900778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:46:01.900717 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:46:30.736151 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:46:30.736182 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:46:31.900786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:47:01.900890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:47:30.753125 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:47:30.753169 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:47:31.900779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:48:01.900763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:48:30.771280 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:48:30.771315 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:48:31.900760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:49:01.900735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:49:30.787067 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:49:30.787127 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:49:31.900740 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:50:01.900803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:50:30.806188 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:50:30.806225 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:50:31.900786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:51:01.900774 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:51:30.823503 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:51:30.823623 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:51:31.900777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:52:01.900732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:52:30.841259 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:52:30.841297 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:52:31.900790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:53:01.900762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:53:30.859478 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:53:30.859519 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:53:31.900757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:54:01.900801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:54:30.878366 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:54:30.878470 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:54:31.900847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:55:01.900767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:55:30.884434 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:55:30.884465 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:55:31.901927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:56:01.900796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:56:30.889938 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:56:30.890109 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:56:31.900802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:57:01.900795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:57:30.900529 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:57:30.900565 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:57:31.900837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:58:01.900955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:58:30.906930 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:58:30.906972 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:58:31.900743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:59:01.900731 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:59:30.912536 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:59:30.912570 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:59:31.900732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:00:01.900723 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:00:30.918985 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:00:30.919015 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:00:31.900772 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:01:01.900751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:01:30.924731 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:01:30.924763 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:01:31.900743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:02:01.900827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:02:30.930565 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:02:30.930600 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:02:31.900872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:03:01.900740 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:03:30.939580 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:03:30.939623 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:03:31.900759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:04:01.900818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:04:30.945193 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:04:30.945519 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:04:31.900959 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:05:01.900898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:05:30.951122 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:05:30.951174 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:05:31.900833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:06:01.900721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:06:30.956973 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:06:30.957021 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:06:31.900733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:07:01.900799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:07:30.971865 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:07:30.971906 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:07:31.900756 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:08:01.900757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:08:30.977188 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:08:30.977314 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:08:31.900757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:09:01.900780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:09:30.983341 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:09:30.983754 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:09:31.900836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:10:01.900726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:10:30.989734 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:10:30.989774 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:10:31.900812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:11:01.900825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:11:30.995500 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:11:30.995533 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:11:31.900758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:12:01.900724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:12:31.001793 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:12:31.001826 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:12:31.900790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:13:01.900759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:13:31.007356 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:13:31.007417 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:13:31.900705 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:14:01.901405 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:14:31.012981 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:14:31.013021 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:14:31.900755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:15:01.901123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:15:31.018130 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:15:31.018163 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:15:31.900824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:16:01.900816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:16:31.024144 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:16:31.024422 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:16:31.900773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:17:01.900728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:17:31.030444 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:17:31.030481 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:17:31.900724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:18:01.900842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:18:31.036309 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:18:31.036483 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:18:31.900857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:19:01.900715 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:19:31.043132 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:19:31.043481 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:19:31.900757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:20:01.900755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:20:31.049586 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:20:31.049621 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:20:31.900767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:21:01.900775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:21:31.055815 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:21:31.055850 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:21:31.900762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:22:01.900788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:22:31.061318 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:22:31.061361 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:22:31.900733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:23:01.900706 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:23:31.067019 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:23:31.067052 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:23:31.900694 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:24:01.900710 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:24:31.072346 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:24:31.072380 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:24:31.900776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:25:01.900719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:25:31.078084 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:25:31.078119 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:25:31.900738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:26:01.900800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:26:31.084454 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:26:31.084488 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:26:31.900772 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:27:01.900777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:27:31.089827 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:27:31.089901 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:27:31.900779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:28:01.900897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:28:31.096358 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:28:31.096402 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:28:31.900730 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:29:01.900829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:29:31.101449 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:29:31.101481 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:29:31.900766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:30:01.900928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:30:31.107265 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:30:31.107297 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:30:31.900740 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:31:01.900751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:31:31.114192 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:31:31.114323 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:31:31.900772 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:32:01.900751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:32:31.120704 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:32:31.120847 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:32:31.900759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:33:01.900756 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:33:31.127381 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:33:31.127422 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:33:31.900757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:34:01.900719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:34:31.133417 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:34:31.133469 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:34:31.900808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:35:01.900792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:35:31.139030 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:35:31.139094 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:35:31.900770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:36:01.900739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:36:31.144158 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:36:31.144196 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:36:31.900876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:37:01.900827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:37:31.149829 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:37:31.149873 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:37:31.900972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:38:01.900886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:38:31.155080 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:38:31.155118 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:38:31.900947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:39:01.900895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:39:31.160940 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:39:31.160978 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:39:31.900816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:40:01.900695 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:40:31.166758 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:40:31.166813 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 04:40:31.900796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 04:41:01.900806 metrics.go:34: INFO No non-zero metrics in the last 30s