By type
2022/03/14 02:49:09.593178 beat.go:285: INFO Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs]
2022/03/14 02:49:09.593225 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/14 02:49:09.593299 logstash.go:90: INFO Max Retries set to: 3
2022/03/14 02:49:09.593361 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/14 02:49:09.593383 metrics.go:23: INFO Metrics logging every 30s
2022/03/14 02:49:09.593473 publish.go:295: INFO Publisher name: onap-portal-app-9c5c78dc6-99lsb
2022/03/14 02:49:09.593666 async.go:63: INFO Flush Interval set to: 1s
2022/03/14 02:49:09.593687 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/14 02:49:09.594175 beat.go:221: INFO filebeat start running.
2022/03/14 02:49:09.594288 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/14 02:49:09.858240 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/14 02:49:09.858303 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/14 02:49:09.858377 crawler.go:38: INFO Loading Prospectors: 1
2022/03/14 02:49:09.858567 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/14 02:49:09.858654 registrar.go:236: INFO Starting Registrar
2022/03/14 02:49:09.858672 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/14 02:49:09.858767 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/14 02:49:09.858714 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/14 02:49:09.858763 sync.go:41: INFO Start sending events to output
2022/03/14 02:49:19.860577 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/14 02:49:19.860671 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/14 02:49:19.860734 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/14 02:49:19.860765 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/14 02:49:19.860880 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/14 02:49:19.868907 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:49:19.868929 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:49:20.874302 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:49:20.874342 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:49:22.880406 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:49:22.880446 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:49:26.887056 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:49:26.887092 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:49:34.895832 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:49:34.895879 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:49:39.593851 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=61 registrar.writes=1
2022/03/14 02:49:50.905163 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:49:50.905205 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:50:09.593780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:50:22.915373 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:50:22.915404 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:50:39.593934 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:51:09.593871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:51:22.925476 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:51:22.925508 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:51:39.593806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:52:09.593957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:52:22.935700 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:52:22.935745 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:52:39.593837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:53:09.593685 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:53:22.946178 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:53:22.946229 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:53:39.593704 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:54:09.593759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:54:22.957242 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:54:22.957276 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:54:24.873906 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/14 02:54:39.593785 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/14 02:55:09.594387 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:55:22.967015 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:55:22.967050 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:55:39.593826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:56:09.593644 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:56:22.976813 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:56:22.976843 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:56:39.593801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:57:09.593705 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:57:22.983846 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:57:22.983882 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:57:39.593783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:58:09.593712 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:58:22.991821 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:58:22.991853 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:58:39.593726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:59:09.593837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:59:23.000367 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:59:23.000423 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:59:39.593793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:00:09.593843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:00:23.008474 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:00:23.008497 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:00:39.593753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:01:09.593834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:01:23.019202 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:01:23.019249 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:01:39.593648 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:02:09.593803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:02:23.030131 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:02:23.030176 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:02:39.593759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:03:09.593787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:03:23.039453 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:03:23.039483 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:03:39.593869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:04:09.593986 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:04:23.049602 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:04:23.049640 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:04:39.593797 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:05:09.593821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:05:23.058966 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:05:23.059002 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:05:39.593717 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:06:09.593823 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:06:23.069126 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:06:23.069174 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:06:39.593791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:07:09.593861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:07:23.077649 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:07:23.077693 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:07:39.593776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:08:09.593741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:08:23.088389 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:08:23.088420 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:08:39.593833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:09:09.593779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:09:23.097379 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:09:23.097409 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:09:39.593855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:10:09.593801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:10:23.106224 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:10:23.106261 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:10:39.593781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:11:09.593753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:11:23.120470 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:11:23.120503 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:11:39.593755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:12:09.593792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:12:23.130744 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:12:23.130804 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:12:39.593812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:13:09.593795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:13:23.140607 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:13:23.140661 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:13:39.593794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:14:09.593824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:14:23.151724 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:14:23.151773 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:14:39.593861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:15:09.593844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:15:23.160836 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:15:23.160876 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:15:39.593736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:16:09.593748 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:16:23.176840 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:16:23.176884 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:16:39.593738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:17:09.593834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:17:23.186883 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:17:23.186936 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:17:39.593798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:18:09.593881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:18:23.196861 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:18:23.196906 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:18:39.593847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:19:09.593786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:19:23.206213 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:19:23.206260 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:19:39.593757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:20:09.593842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:20:23.217494 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:20:23.217533 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:20:39.593750 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:21:09.593785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:21:23.228131 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:21:23.228191 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:21:39.593761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:22:09.593825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:22:23.238015 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:22:23.238052 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:22:39.593809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:23:09.593792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:23:23.246940 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:23:23.246976 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:23:39.593716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:24:09.593874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:24:23.256617 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:24:23.256676 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:24:39.593726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:25:09.593874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:25:23.266436 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:25:23.266467 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:25:39.593786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:26:09.593925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:26:23.275579 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:26:23.275632 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:26:39.593818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:27:09.593826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:27:23.285593 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:27:23.285628 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:27:39.593870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:28:09.594420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:28:23.293924 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:28:23.293970 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:28:39.593751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:29:09.593728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:29:23.302784 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:29:23.302836 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:29:39.593799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:30:09.593827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:30:23.313487 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:30:23.313537 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:30:39.593810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:31:09.593840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:31:23.325378 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:31:23.325417 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:31:39.593759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:32:09.593864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:32:23.335475 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:32:23.335540 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:32:39.593809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:33:09.593820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:33:23.346789 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:33:23.346843 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:33:39.593803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:34:09.593885 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:34:23.356661 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:34:23.356711 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:34:39.593823 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:35:09.593808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:35:23.368145 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:35:23.368208 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:35:39.593865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:36:09.593814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:36:23.379620 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:36:23.379678 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:36:39.593795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:37:09.593865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:37:23.389668 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:37:23.389707 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:37:39.593631 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:38:09.593743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:38:23.399865 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:38:23.399927 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:38:39.593746 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:39:09.593795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:39:23.410517 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:39:23.410562 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:39:39.593752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:40:09.593704 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:40:23.420281 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:40:23.420310 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:40:39.593796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:41:09.593785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:41:23.430209 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:41:23.430247 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:41:39.593858 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:42:09.593898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:42:23.439945 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:42:23.439984 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:42:39.593819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:43:09.593803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:43:23.449622 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:43:23.449669 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:43:39.593669 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:44:09.593808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:44:23.460221 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:44:23.460259 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:44:39.593831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:45:09.595012 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:45:23.469553 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:45:23.469584 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:45:39.593779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:46:09.593861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:46:23.479281 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:46:23.479330 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:46:39.593817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:47:09.593889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:47:23.491171 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:47:23.491213 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:47:39.593743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:48:09.593877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:48:23.502748 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:48:23.502785 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:48:39.593791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:49:09.593870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:49:23.511445 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:49:23.511587 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:49:39.593843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:50:09.593874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:50:23.523139 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:50:23.523187 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:50:39.593753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:51:09.593723 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:51:23.532964 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:51:23.533005 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:51:39.593833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:52:09.593768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:52:23.542138 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:52:23.542184 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:52:39.593775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:53:09.593857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:53:23.551214 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:53:23.551258 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:53:39.593838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:54:09.593853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:54:23.560584 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:54:23.560633 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:54:39.593792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:55:09.593816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:55:23.570357 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:55:23.570400 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:55:39.593721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:56:09.593692 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:56:23.579507 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:56:23.579555 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:56:39.593754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:57:09.593786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:57:23.587549 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:57:23.587580 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:57:39.593703 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:58:09.593820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:58:23.597387 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:58:23.597442 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:58:39.593748 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:59:09.593754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:59:23.608049 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:59:23.608100 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:59:39.593774 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:00:09.593707 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:00:23.617355 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:00:23.617397 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:00:39.593798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:01:09.593822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:01:23.627994 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:01:23.628039 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:01:39.593796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:02:09.593717 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:02:23.638698 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:02:23.638740 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:02:39.593759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:03:09.593837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:03:23.649068 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:03:23.649095 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:03:39.593859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:04:09.593829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:04:23.659948 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:04:23.660019 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:04:39.593842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:05:09.593784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:05:23.668985 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:05:23.669023 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:05:39.593812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:06:09.593847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:06:23.678715 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:06:23.678780 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:06:39.593952 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:07:09.593742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:07:23.689273 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:07:23.689323 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:07:39.593825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:08:09.593960 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:08:23.699832 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:08:23.699912 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:08:39.593722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:09:09.593947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:09:23.711499 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:09:23.711530 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:09:39.593765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:10:09.593664 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:10:23.721921 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:10:23.721959 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:10:39.593795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:11:09.593818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:11:23.730691 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:11:23.730746 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:11:39.593818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:12:09.593868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:12:23.741639 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:12:23.741691 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:12:39.593772 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:13:09.593735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:13:23.751879 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:13:23.751915 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:13:39.593808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:14:09.593892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:14:23.762797 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:14:23.762837 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:14:39.593722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:15:09.593700 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:15:23.773904 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:15:23.773939 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:15:39.593851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:16:09.593849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:16:23.782860 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:16:23.782892 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:16:39.593820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:17:09.593759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:17:23.793123 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:17:23.793170 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:17:39.593850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:18:09.593833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:18:23.806658 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:18:23.806704 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:18:39.593851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:19:09.593869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:19:23.815618 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:19:23.815672 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:19:39.593786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:20:09.593803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:20:23.824524 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:20:23.824580 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:20:39.593759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:21:09.593841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:21:23.833506 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:21:23.833559 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:21:39.593836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:22:09.593854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:22:23.844826 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:22:23.844868 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:22:39.593864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:23:09.593758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:23:23.854133 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:23:23.854223 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:23:39.593719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:24:09.593957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:24:23.863697 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:24:23.863739 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:24:39.593830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:25:09.593668 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:25:23.873663 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:25:23.873696 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:25:39.593810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:26:09.593772 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:26:23.883988 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:26:23.884031 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:26:39.593724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:27:09.593781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:27:23.893504 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:27:23.893540 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:27:39.593728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:28:09.593737 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:28:23.903608 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:28:23.903657 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:28:39.593741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:29:09.593956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:29:23.912603 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:29:23.912648 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:29:39.593711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:30:09.593831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:30:23.922526 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:30:23.922566 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:30:39.593621 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:31:09.593835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:31:23.933436 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:31:23.933493 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:31:39.593878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:32:09.593799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:32:23.942068 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:32:23.942115 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:32:39.593732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:33:09.593687 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:33:23.953348 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:33:23.953390 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:33:39.593852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:34:09.593782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:34:23.964504 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:34:23.964553 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:34:39.593770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:35:09.593851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:35:23.974673 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:35:23.974721 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:35:39.593768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:36:09.593849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:36:23.984773 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:36:23.984812 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:36:39.593787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:37:09.593751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:37:23.996121 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:37:23.996167 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:37:39.593759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:38:09.593860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:38:24.006065 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:38:24.006115 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:38:39.593796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:39:09.593813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:39:24.017083 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:39:24.017121 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:39:39.593806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:40:09.593835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:40:24.027983 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:40:24.028023 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:40:39.593659 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:41:09.593770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:41:24.037389 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:41:24.037455 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:41:39.593822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:42:09.593883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:42:24.049606 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:42:24.049651 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:42:39.593874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:43:09.593795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:43:24.059232 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:43:24.059276 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:43:39.593845 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:44:09.593810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:44:24.069718 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:44:24.069770 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:44:39.593837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:45:09.593735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:45:24.080657 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:45:24.080689 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:45:39.593823 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:46:09.593802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:46:24.089577 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:46:24.089608 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:46:39.593742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:47:09.593531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:47:24.102484 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:47:24.102539 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:47:39.594087 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:48:09.593774 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:48:24.114078 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:48:24.114127 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:48:39.593762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:49:09.593784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:49:24.124279 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:49:24.124343 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:49:39.593900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:50:09.593798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:50:24.136659 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:50:24.136702 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:50:39.593898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:51:09.593841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:51:24.147024 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:51:24.147050 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:51:39.594003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:52:09.593911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:52:24.157660 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:52:24.157706 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:52:39.593743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:53:09.593677 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:53:24.169965 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:53:24.170012 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:53:39.593801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:54:09.593804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:54:24.180857 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:54:24.180909 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:54:39.593758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:55:09.593820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:55:24.189591 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:55:24.189621 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:55:39.593819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:56:09.593862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:56:24.200328 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:56:24.200356 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:56:39.593763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:57:09.593874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:57:24.209120 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:57:24.209176 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:57:39.593862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:58:09.593814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:58:24.218451 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:58:24.218484 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:58:39.593762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:59:09.593779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:59:24.228312 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:59:24.228352 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:59:39.593859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 05:00:09.593816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 05:00:24.238557 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 05:00:24.238637 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 05:00:39.593802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 05:01:09.593872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 05:01:24.246609 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 05:01:24.246641 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 05:01:39.593755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 05:02:09.593812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 05:02:24.254068 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 05:02:24.254102 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 05:02:39.593770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 05:03:09.593762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 05:03:24.263101 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 05:03:24.263138 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 05:03:39.593629 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 05:04:09.593769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 05:04:24.272344 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 05:04:24.272389 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 05:04:39.593723 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 05:05:09.593801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 05:05:24.281722 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 05:05:24.281763 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 05:05:39.593711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 05:06:09.593684 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 05:06:24.290741 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 05:06:24.290781 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 05:06:39.593912 metrics.go:34: INFO No non-zero metrics in the last 30s