2022/02/04 14:07:09.238348 beat.go:285: INFO Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs]
2022/02/04 14:07:09.238388 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/02/04 14:07:09.238458 logstash.go:90: INFO Max Retries set to: 3
2022/02/04 14:07:09.238518 metrics.go:23: INFO Metrics logging every 30s
2022/02/04 14:07:09.238522 outputs.go:108: INFO Activated logstash as output plugin.
2022/02/04 14:07:09.238662 publish.go:295: INFO Publisher name: onap-portal-app-9c5c78dc6-jbwfq
2022/02/04 14:07:09.238828 async.go:63: INFO Flush Interval set to: 1s
2022/02/04 14:07:09.238847 async.go:64: INFO Max Bulk Size set to: 2048
2022/02/04 14:07:09.239217 beat.go:221: INFO filebeat start running.
2022/02/04 14:07:09.239293 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/02/04 14:07:09.451495 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/02/04 14:07:09.451592 registrar.go:123: INFO States Loaded from registrar: 0
2022/02/04 14:07:09.451640 crawler.go:38: INFO Loading Prospectors: 1
2022/02/04 14:07:09.451959 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/02/04 14:07:09.452140 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/02/04 14:07:09.452170 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/02/04 14:07:09.452191 sync.go:41: INFO Start sending events to output
2022/02/04 14:07:09.452199 registrar.go:236: INFO Starting Registrar
2022/02/04 14:07:09.452817 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/02/04 14:07:19.453730 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/02/04 14:07:19.453953 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/02/04 14:07:19.453977 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/02/04 14:07:19.454201 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/02/04 14:07:19.454380 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/02/04 14:07:24.464110 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:07:24.464144 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:07:25.471025 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:07:25.471069 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:07:27.476299 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:07:27.476342 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:07:31.485645 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:07:31.485686 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:07:39.239065 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=5 filebeat.harvester.running=5 filebeat.harvester.started=5 libbeat.publisher.published_events=72 publish.events=3 registrar.states.current=3 registrar.states.update=3 registrar.writes=2
2022/02/04 14:07:39.495579 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:07:39.495615 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:07:55.507163 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:07:55.507310 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:08:09.238949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:08:27.546105 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:08:27.546242 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:08:39.239000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:09:09.238953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:09:27.638641 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:09:27.638686 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:09:39.239004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:10:09.238978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:10:27.646103 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:10:27.646145 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:10:39.238946 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:11:09.238952 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:11:27.670152 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:11:27.670195 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:11:39.238980 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:12:09.238979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:12:24.465880 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/02/04 14:12:27.676193 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:12:27.676218 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:12:39.238903 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/02/04 14:13:09.239362 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:13:27.682239 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:13:27.682270 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:13:39.239042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:14:09.238997 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:14:27.707211 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:14:27.707257 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:14:39.238948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:15:09.238963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:15:27.714962 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:15:27.715000 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:15:39.239005 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:16:09.238931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:16:27.722960 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:16:27.723016 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:16:39.238972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:17:09.238868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:17:27.746779 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:17:27.746818 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:17:39.239033 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:18:09.238963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:18:27.755207 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:18:27.755282 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:18:39.238950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:19:09.238908 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:19:27.763339 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:19:27.763390 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:19:39.238995 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:20:09.238830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:20:27.771995 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:20:27.772032 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:20:39.239123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:21:09.238976 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:21:27.778953 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:21:27.778997 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:21:39.238989 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:22:09.238847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:22:27.786655 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:22:27.786686 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:22:39.238981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:23:09.238891 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:23:27.794547 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:23:27.794846 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:23:39.238852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:24:09.238892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:24:27.803548 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:24:27.803587 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:24:39.238986 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:25:09.238958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:25:27.811275 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:25:27.811336 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:25:39.239340 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:26:09.238888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:26:27.820684 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:26:27.820731 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:26:39.238963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:27:09.238955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:27:27.827885 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:27:27.827925 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:27:39.238928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:28:09.239002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:28:27.835808 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:28:27.835852 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:28:39.238964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:29:09.238913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:29:27.844163 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:29:27.844224 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:29:39.238820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:30:09.238900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:30:27.850796 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:30:27.850837 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:30:39.238885 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:31:09.238967 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:31:27.860432 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:31:27.860493 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:31:39.238957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:32:09.238971 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:32:27.869953 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:32:27.869973 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:32:39.238840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:33:09.238902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:33:27.877776 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:33:27.877825 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:33:39.238894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:34:09.238936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:34:27.886044 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:34:27.886092 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:34:39.238911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:35:09.238980 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:35:27.894426 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:35:27.894466 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:35:39.238899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:36:09.238896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:36:27.903537 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:36:27.903579 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:36:39.238889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:37:09.238801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:37:27.911784 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:37:27.911828 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:37:39.238967 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:38:09.238979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:38:27.919997 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:38:27.920041 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:38:39.238931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:39:09.238876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:39:27.927777 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:39:27.927820 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:39:39.238968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:40:09.239055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:40:27.935394 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:40:27.935435 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:40:39.238958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:41:09.238968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:41:27.944259 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:41:27.944320 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:41:39.238947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:42:09.239007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:42:27.952749 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:42:27.952792 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:42:39.238888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:43:09.239011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:43:27.961254 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:43:27.961296 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:43:39.238996 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:44:09.238916 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:44:28.006441 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:44:28.006481 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:44:39.238869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:45:09.238838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:45:28.013600 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:45:28.013635 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:45:39.238975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:46:09.238974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:46:28.021308 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:46:28.021346 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:46:39.238960 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:47:09.238923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:47:28.029897 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:47:28.030014 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:47:39.239050 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:48:09.238944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:48:28.038806 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:48:28.038849 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:48:39.238775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:49:09.239023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:49:28.047651 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:49:28.047837 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:49:39.238978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:50:09.239015 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:50:28.054629 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:50:28.054652 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:50:39.238905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:51:09.239040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:51:28.062119 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:51:28.062153 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:51:39.238952 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:52:09.238919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:52:28.070110 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:52:28.070150 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:52:39.238948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:53:09.238955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:53:28.077959 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:53:28.077994 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:53:39.238900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:54:09.239026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:54:28.087529 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:54:28.087576 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:54:39.238891 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:55:09.238984 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:55:28.095915 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:55:28.095962 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:55:39.239010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:56:09.239047 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:56:28.104145 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:56:28.104183 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:56:39.238872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:57:09.238910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:57:28.112261 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:57:28.112303 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:57:39.238918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:58:09.238938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:58:28.121220 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:58:28.121396 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:58:39.238986 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:59:09.238870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:59:28.130388 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:59:28.130426 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:59:39.238975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:00:09.238962 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:00:28.138962 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:00:28.138999 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:00:39.238967 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:01:09.238911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:01:28.147915 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:01:28.147959 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:01:39.239020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:02:09.239027 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:02:28.156068 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:02:28.156110 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:02:39.238857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:03:09.238943 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:03:28.164092 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:03:28.164129 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:03:39.238915 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:04:09.238951 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:04:28.172455 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:04:28.172490 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:04:39.238935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:05:09.238965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:05:28.179629 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:05:28.179655 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:05:39.239001 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:06:09.239026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:06:28.187528 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:06:28.187572 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:06:39.239013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:07:09.239004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:07:28.195836 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:07:28.195881 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:07:39.238975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:08:09.238945 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:08:28.203549 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:08:28.203601 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:08:39.238975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:09:09.238962 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:09:28.211403 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:09:28.211440 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:09:39.238933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:10:09.239056 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:10:28.219708 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:10:28.219747 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:10:39.238918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:11:09.238924 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:11:28.228150 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:11:28.228198 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:11:39.238961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:12:09.238969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:12:28.236609 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:12:28.236655 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:12:39.238963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:13:09.239006 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:13:28.245236 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:13:28.245295 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:13:39.238970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:14:09.239039 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:14:28.252159 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:14:28.252188 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:14:39.238926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:15:09.238969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:15:28.259833 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:15:28.259874 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:15:39.238940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:16:09.239005 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:16:28.268163 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:16:28.268315 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:16:39.238922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:17:09.238956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:17:28.276804 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:17:28.276842 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:17:39.238895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:18:09.238948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:18:28.284941 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:18:28.284985 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:18:39.239034 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:19:09.238999 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:19:28.294708 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:19:28.294747 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:19:39.239033 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:20:09.239149 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:20:28.302693 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:20:28.302738 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:20:39.238904 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:21:09.238926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:21:28.311185 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:21:28.311222 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:21:39.238988 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:22:09.238946 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:22:28.319726 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:22:28.319777 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:22:39.238895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:23:09.238977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:23:28.327827 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:23:28.327864 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:23:39.239014 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:24:09.238959 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:24:28.335773 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:24:28.335873 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:24:39.238961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:25:09.238950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:25:28.348361 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:25:28.348398 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:25:39.238959 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:26:09.238978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:26:28.356687 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:26:28.356722 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:26:39.238910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:27:09.238953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:27:28.365711 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:27:28.365755 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:27:39.238972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:28:09.238974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:28:28.373875 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:28:28.373907 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:28:39.238955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:29:09.238972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:29:28.381453 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:29:28.381479 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:29:39.238913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:30:09.238928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:30:28.389748 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:30:28.389781 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:30:39.238949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:31:09.238916 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:31:28.397837 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:31:28.397923 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:31:39.238968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:32:09.239030 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:32:28.405867 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:32:28.405929 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:32:39.238867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:33:09.239102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:33:28.417252 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:33:28.417300 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:33:39.238973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:34:09.238894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:34:28.426243 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:34:28.426305 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:34:39.238886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:35:09.238891 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:35:28.435025 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:35:28.435086 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:35:39.238986 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:36:09.238981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:36:28.443705 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:36:28.443746 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:36:39.238932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:37:09.238914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:37:28.451733 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:37:28.451780 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:37:39.238961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:38:09.238883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:38:28.459619 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:38:28.459676 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:38:39.238909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:39:09.238937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:39:28.467636 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:39:28.467665 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:39:39.238952 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:40:09.238920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:40:28.476364 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:40:28.476451 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:40:39.238949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:41:09.238833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:41:28.485252 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:41:28.485309 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:41:39.238993 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:42:09.238902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:42:28.493701 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:42:28.493746 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:42:39.238894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:43:09.238951 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:43:28.501372 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:43:28.501401 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:43:39.238979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:44:09.238997 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:44:28.509902 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:44:28.509941 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:44:39.238934 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:45:09.238935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:45:28.518041 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:45:28.518079 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:45:39.238988 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:46:09.238921 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:46:28.526262 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:46:28.526310 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:46:39.238972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:47:09.238955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:47:28.534290 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:47:28.534417 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:47:39.238896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:48:09.238980 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:48:28.542877 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:48:28.542916 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:48:39.238973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:49:09.238976 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:49:28.550616 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:49:28.550668 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:49:39.239059 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:50:09.238947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:50:28.558360 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:50:28.558396 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:50:39.238856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:51:09.238954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:51:28.567440 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:51:28.567484 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:51:39.238948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:52:09.238907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:52:28.574769 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:52:28.574797 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:52:39.238941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:53:09.238977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:53:28.583880 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:53:28.583925 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:53:39.238883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:54:09.238956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:54:28.592027 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:54:28.592176 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:54:39.238920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:55:09.238891 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:55:28.599815 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:55:28.599855 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:55:39.239053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:56:09.238944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:56:28.607643 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:56:28.607678 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:56:39.238969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:57:09.238871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:57:28.614993 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:57:28.615035 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:57:39.238989 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:58:09.238920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:58:28.623512 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:58:28.623555 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:58:39.238881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:59:09.238863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:59:28.631812 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:59:28.631949 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:59:39.238940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 16:00:09.239015 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 16:00:28.640369 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 16:00:28.640517 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 16:00:39.238969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 16:01:09.238999 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 16:01:28.650118 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 16:01:28.650192 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 16:01:39.238909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 16:02:09.239100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 16:02:28.658973 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 16:02:28.659009 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 16:02:39.238890 metrics.go:34: INFO No non-zero metrics in the last 30s