2022/01/04 03:11:09.116460 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/01/04 03:11:09.116513 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/01/04 03:11:09.116679 metrics.go:23: INFO Metrics logging every 30s
2022/01/04 03:11:09.116593 logstash.go:90: INFO Max Retries set to: 3
2022/01/04 03:11:09.116866 outputs.go:108: INFO Activated logstash as output plugin.
2022/01/04 03:11:09.116975 publish.go:295: INFO Publisher name: onap-portal-sdk-856bc9b5d4-6bbtm
2022/01/04 03:11:09.117156 async.go:63: INFO Flush Interval set to: 1s
2022/01/04 03:11:09.117178 async.go:64: INFO Max Bulk Size set to: 2048
2022/01/04 03:11:09.117636 beat.go:221: INFO filebeat start running.
2022/01/04 03:11:09.117752 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/01/04 03:11:09.224628 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/01/04 03:11:09.224724 registrar.go:123: INFO States Loaded from registrar: 0
2022/01/04 03:11:09.224788 crawler.go:38: INFO Loading Prospectors: 1
2022/01/04 03:11:09.224870 registrar.go:236: INFO Starting Registrar
2022/01/04 03:11:09.225011 sync.go:41: INFO Start sending events to output
2022/01/04 03:11:09.225055 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/01/04 03:11:09.225115 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/01/04 03:11:09.225318 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/01/04 03:11:09.225363 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/01/04 03:11:09.226392 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/01/04 03:11:09.226475 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/01/04 03:11:09.226614 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/01/04 03:11:09.226977 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/01/04 03:11:09.227028 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/01/04 03:11:14.238381 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:11:14.238425 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:11:15.243261 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:11:15.243307 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:11:17.248798 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:11:17.248846 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:11:21.259248 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:11:21.259293 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:11:29.266315 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:11:29.266347 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:11:39.117096 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=356 registrar.writes=1
2022/01/04 03:11:45.276218 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:11:45.276276 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:12:09.117050 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:12:17.286195 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:12:17.286240 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:12:39.117180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:13:09.117154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:13:17.294955 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:13:17.294983 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:13:39.117013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:14:09.117143 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:14:17.304687 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:14:17.304739 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:14:39.117040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:15:09.116980 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:15:17.315763 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:15:17.315803 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:15:39.117169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:16:09.116988 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:16:14.237795 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/01/04 03:16:14.237894 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/01/04 03:16:14.237903 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/01/04 03:16:14.237967 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/01/04 03:16:14.240988 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/01/04 03:16:17.329783 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:16:17.329815 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:16:39.117195 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=5 filebeat.harvester.open_files=-5 filebeat.harvester.running=-5
2022/01/04 03:17:09.117168 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:17:17.339850 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:17:17.339899 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:17:39.117125 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:18:09.117167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:18:17.351558 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:18:17.351616 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:18:39.117317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:19:09.117130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:19:17.363811 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:19:17.363871 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:19:39.117107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:20:09.117144 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:20:17.373772 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:20:17.373818 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:20:39.117152 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:21:09.117215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:21:17.381974 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:21:17.382004 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:21:39.117178 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:22:09.117108 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:22:17.391169 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:22:17.391210 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:22:39.117158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:23:09.117159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:23:17.399345 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:23:17.399372 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:23:39.117373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:24:09.117162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:24:17.411400 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:24:17.411451 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:24:39.117099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:25:09.117161 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:25:17.423010 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:25:17.423052 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:25:39.117190 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:26:09.117164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:26:17.432643 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:26:17.432693 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:26:39.117293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:27:09.117224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:27:17.443367 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:27:17.443422 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:27:39.117204 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:28:09.117225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:28:17.453732 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:28:17.453793 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:28:39.117175 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:29:09.117107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:29:17.464041 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:29:17.464075 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:29:39.117125 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:30:09.117224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:30:17.474130 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:30:17.474173 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:30:39.117169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:31:09.117050 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:31:17.484357 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:31:17.484410 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:31:39.117194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:32:09.117166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:32:17.494820 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:32:17.494862 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:32:39.117113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:33:09.117080 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:33:17.504590 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:33:17.504629 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:33:39.117150 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:34:09.117204 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:34:17.514938 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:34:17.515027 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:34:39.117120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:35:09.117039 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:35:17.523729 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:35:17.523778 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:35:39.117117 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:36:09.117248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:36:17.534523 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:36:17.534565 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:36:39.117146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:37:09.117180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:37:17.544343 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:37:17.544382 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:37:39.117200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:38:09.117207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:38:17.555863 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:38:17.555912 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:38:39.117173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:39:09.117073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:39:17.564770 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:39:17.564810 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:39:39.117175 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:40:09.117110 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:40:17.574935 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:40:17.574975 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:40:39.117111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:41:09.117240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:41:17.584807 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:41:17.584860 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:41:39.117041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:42:09.117054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:42:17.595880 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:42:17.595910 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:42:39.117134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:43:09.117152 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:43:17.606971 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:43:17.607017 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:43:39.117170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:44:09.117049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:44:17.615608 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:44:17.615644 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:44:39.117121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:45:09.116961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:45:17.629960 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:45:17.629985 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:45:39.117162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:46:09.117149 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:46:17.639169 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:46:17.639203 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:46:39.117060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:47:09.117049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:47:17.648308 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:47:17.648374 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:47:39.117495 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:48:09.117103 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:48:17.660040 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:48:17.660093 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:48:39.117141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:49:09.117052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:49:17.668209 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:49:17.668243 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:49:39.117105 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:50:09.117081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:50:17.677784 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:50:17.677827 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:50:39.117064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:51:09.117077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:51:17.687436 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:51:17.687476 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:51:39.117255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:52:09.117128 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:52:17.698342 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:52:17.698376 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:52:39.117399 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:53:09.117177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:53:17.708195 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:53:17.708238 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:53:39.117080 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:54:09.117216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:54:17.717102 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:54:17.717137 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:54:39.117128 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:55:09.117073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:55:17.731930 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:55:17.731959 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:55:39.117102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:56:09.117038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:56:17.742315 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:56:17.742363 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:56:39.117134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:57:09.117057 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:57:17.753028 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:57:17.753058 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:57:39.117208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:58:09.117195 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:58:17.762801 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:58:17.762849 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:58:39.117186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:59:09.117123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 03:59:17.772515 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:59:17.772573 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 03:59:39.117162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:00:09.117068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:00:17.782698 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:00:17.782740 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:00:39.117018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:01:09.117113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:01:17.792006 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:01:17.792050 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:01:39.117174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:02:09.117216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:02:17.801801 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:02:17.801846 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:02:39.117096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:03:09.117038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:03:17.811393 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:03:17.811438 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:03:39.117093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:04:09.117076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:04:17.821604 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:04:17.821681 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:04:39.117175 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:05:09.117068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:05:17.831989 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:05:17.832034 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:05:39.117140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:06:09.117188 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:06:17.842662 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:06:17.842708 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:06:39.117165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:07:09.117096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:07:17.852223 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:07:17.852262 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:07:39.117164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:08:09.117136 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:08:17.862828 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:08:17.862866 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:08:39.117166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:09:09.117149 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:09:17.873611 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:09:17.873666 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:09:39.117072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:10:09.116976 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:10:17.883500 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:10:17.883543 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:10:39.117073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:11:09.117025 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:11:17.893524 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:11:17.893567 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:11:39.117195 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:12:09.117073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:12:17.904734 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:12:17.904788 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:12:39.117002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:13:09.117078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:13:17.914032 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:13:17.914079 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:13:39.117170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:14:09.117140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:14:17.924629 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:14:17.924684 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:14:39.117052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:15:09.117119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:15:17.935531 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:15:17.935570 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:15:39.117178 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:16:09.117083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:16:17.946789 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:16:17.946831 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:16:39.117252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:17:09.117109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:17:17.957516 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:17:17.957580 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:17:39.117184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:18:09.117091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:18:17.968406 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:18:17.968566 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:18:39.117175 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:19:09.117248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:19:17.978557 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:19:17.978585 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:19:39.117050 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:20:09.117028 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:20:17.988652 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:20:17.988689 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:20:39.117081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:21:09.117079 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:21:17.998511 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:21:17.998546 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:21:39.117039 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:22:09.116922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:22:18.010183 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:22:18.010223 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:22:39.116932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:23:09.117058 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:23:18.020927 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:23:18.020970 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:23:39.117039 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:24:09.117104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:24:18.029729 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:24:18.029764 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:24:39.117129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:25:09.117145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:25:18.040410 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:25:18.040446 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:25:39.117142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:26:09.117178 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:26:18.051003 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:26:18.051052 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:26:39.117109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:27:09.117119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:27:18.062201 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:27:18.062241 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:27:39.117085 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:28:09.117123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:28:18.103602 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:28:18.103683 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:28:39.117062 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:29:09.117086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:29:18.114218 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:29:18.114263 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:29:39.117084 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:30:09.117055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:30:18.124721 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:30:18.124830 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:30:39.117134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:31:09.117130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:31:18.135801 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:31:18.135840 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:31:39.117168 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:32:09.117120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:32:18.146356 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:32:18.146409 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:32:39.117173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:33:09.116993 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:33:18.157199 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:33:18.157244 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:33:39.117133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:34:09.117111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:34:18.167932 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:34:18.167972 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:34:39.117055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:35:09.117012 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:35:18.177024 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:35:18.177068 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:35:39.117120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:36:09.117086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:36:18.188626 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:36:18.188666 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:36:39.117107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:37:09.117060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:37:18.202082 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:37:18.202129 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:37:39.117011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:38:09.117125 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:38:18.214670 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:38:18.214710 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:38:39.117066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:39:09.117100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:39:18.223987 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:39:18.224161 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:39:39.117145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:40:09.117077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:40:18.235775 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:40:18.235811 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:40:39.117046 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:41:09.117104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:41:18.245176 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:41:18.245214 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:41:39.117180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:42:09.117138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:42:18.255454 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:42:18.255601 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:42:39.117067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:43:09.117059 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:43:18.266083 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:43:18.266122 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:43:39.117118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:44:09.117050 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:44:18.277093 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:44:18.277130 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:44:39.117185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:45:09.117158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:45:18.286805 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:45:18.286847 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:45:39.117111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:46:09.117153 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:46:18.297615 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:46:18.297698 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:46:39.117065 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:47:09.117110 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:47:18.308458 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:47:18.308497 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:47:39.117114 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:48:09.117120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:48:18.318699 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:48:18.318744 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:48:39.117080 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:49:09.117113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:49:18.328934 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:49:18.328974 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:49:39.117087 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:50:09.117115 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:50:18.346654 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:50:18.346704 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:50:39.117115 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:51:09.117205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:51:18.357565 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:51:18.357630 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:51:39.117172 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:52:09.117024 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:52:18.366606 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:52:18.366634 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:52:39.117114 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:53:09.117041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:53:18.376490 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:53:18.376533 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:53:39.117153 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:54:09.117103 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:54:18.387761 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:54:18.387962 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:54:39.117187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:55:09.117138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:55:18.397280 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:55:18.397334 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:55:39.117168 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:56:09.116939 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:56:18.406802 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:56:18.406850 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:56:39.117056 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:57:09.117152 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:57:18.423910 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:57:18.423946 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:57:39.117136 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:58:09.117029 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:58:18.436706 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:58:18.436751 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:58:39.117090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:59:09.117119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 04:59:18.445685 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:59:18.445912 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 04:59:39.117142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:00:09.117093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:00:18.456398 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:00:18.456445 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:00:39.117068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:01:09.117064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:01:18.465032 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:01:18.465072 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:01:39.117195 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:02:09.117063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:02:18.475462 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:02:18.475534 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:02:39.117076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:03:09.117086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:03:18.485780 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:03:18.485813 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:03:39.117088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:04:09.117089 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:04:18.495231 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:04:18.495268 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:04:39.117117 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:05:09.117098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:05:18.506438 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:05:18.506486 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:05:39.117153 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:06:09.117040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:06:18.515921 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:06:18.515966 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:06:39.117087 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:07:09.116975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:07:18.525383 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:07:18.525428 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:07:39.117114 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:08:09.117032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:08:18.533681 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:08:18.533724 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:08:39.117054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:09:09.117054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:09:18.543056 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:09:18.543099 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:09:39.117018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:10:09.117099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:10:18.552438 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:10:18.552481 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:10:39.117075 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:11:09.117086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:11:18.561888 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:11:18.561943 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:11:39.117128 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:12:09.117093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:12:18.571879 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:12:18.571936 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:12:39.117138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:13:09.117154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:13:18.582344 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:13:18.582401 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:13:39.117095 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:14:09.117167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:14:18.591981 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:14:18.592016 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:14:39.117172 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:15:09.117127 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:15:18.601299 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:15:18.601344 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:15:39.117054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:16:09.117088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:16:18.611279 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:16:18.611330 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:16:39.117137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:17:09.117126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:17:18.621641 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:17:18.621729 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:17:39.117106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:18:09.117041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:18:18.626428 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:18:18.626473 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:18:39.117022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:19:09.117139 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:19:18.636236 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:19:18.636281 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:19:39.117143 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:20:09.117053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:20:18.644209 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:20:18.644252 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:20:39.117094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:21:09.117049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:21:18.652835 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:21:18.652884 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:21:39.117216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:22:09.117168 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:22:18.662350 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:22:18.662391 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:22:39.117335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:23:09.117053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:23:18.672059 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:23:18.672120 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:23:39.117090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:24:09.117110 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:24:18.683189 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:24:18.683232 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:24:39.117129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:25:09.117145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:25:18.692646 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:25:18.692685 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:25:39.117207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:26:09.117051 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:26:18.701819 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:26:18.701877 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:26:39.117149 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:27:09.117049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:27:18.709412 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:27:18.709477 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:27:39.117141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:28:09.117135 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:28:18.718005 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:28:18.718051 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:28:39.117111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:29:09.117155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:29:18.728105 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:29:18.728164 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:29:39.117115 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:30:09.117138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:30:18.738454 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:30:18.738498 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:30:39.117126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:31:09.117060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:31:18.747280 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:31:18.747429 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:31:39.117131 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:32:09.117192 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:32:18.757348 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:32:18.757396 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:32:39.117082 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:33:09.117032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:33:18.767502 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:33:18.767543 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:33:39.117053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:34:09.117098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:34:18.777052 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:34:18.777085 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:34:39.117162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:35:09.117141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:35:18.786658 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:35:18.786701 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:35:39.117080 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:36:09.117103 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:36:18.795425 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:36:18.795453 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:36:39.117081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:37:09.117059 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:37:18.804642 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:37:18.804688 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:37:39.117208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:38:09.117052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:38:18.813841 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:38:18.813871 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:38:39.117064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:39:09.117138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:39:18.823432 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:39:18.823487 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:39:39.117119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:40:09.117057 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:40:18.834061 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:40:18.834159 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:40:39.117083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:41:09.117066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:41:18.843848 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:41:18.843909 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:41:39.117145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:42:09.117040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:42:18.853308 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:42:18.853343 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:42:39.117142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:43:09.117162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:43:18.863086 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:43:18.863114 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:43:39.117018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:44:09.117106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:44:18.872938 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:44:18.872967 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:44:39.117129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:45:09.117101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:45:18.882614 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:45:18.882748 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:45:39.117050 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:46:09.117135 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:46:18.900034 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:46:18.900064 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:46:39.117098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:47:09.117117 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:47:18.909433 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:47:18.909787 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:47:39.117143 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:48:09.117068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:48:18.919652 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:48:18.919690 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:48:39.117118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:49:09.117166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:49:18.928580 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:49:18.928624 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:49:39.117167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:50:09.117089 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:50:18.937072 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:50:18.937232 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:50:39.117075 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:51:09.117112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:51:18.945158 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:51:18.945204 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:51:39.117126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:52:09.117115 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:52:18.954944 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:52:18.954991 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:52:39.117022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:53:09.117002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:53:18.964200 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:53:18.964236 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:53:39.117082 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:54:09.117129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:54:18.973064 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:54:18.973108 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:54:39.117091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:55:09.117162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:55:18.982112 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:55:18.982159 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:55:39.117144 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:56:09.117065 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:56:18.991332 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:56:18.991369 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:56:39.117063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:57:09.117046 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:57:19.002195 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:57:19.002228 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:57:39.117132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:58:09.117135 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:58:19.011751 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:58:19.011790 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:58:39.117047 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:59:09.117192 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/04 05:59:19.022181 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/04 05:59:19.022275 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host