Results

          2022/03/08 10:37:54.003620 beat.go:285: INFO Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs]
2022/03/08 10:37:54.003690 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/08 10:37:54.003906 logstash.go:90: INFO Max Retries set to: 3
2022/03/08 10:37:54.004008 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/08 10:37:54.004157 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-5k9bz
2022/03/08 10:37:54.004407 async.go:63: INFO Flush Interval set to: 1s
2022/03/08 10:37:54.004440 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/08 10:37:54.004423 metrics.go:23: INFO Metrics logging every 30s
2022/03/08 10:37:54.004946 beat.go:221: INFO filebeat start running.
2022/03/08 10:37:54.005109 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/08 10:37:54.009212 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/08 10:37:54.009288 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/08 10:37:54.009328 crawler.go:38: INFO Loading Prospectors: 1
2022/03/08 10:37:54.009390 registrar.go:236: INFO Starting Registrar
2022/03/08 10:37:54.009571 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/08 10:37:54.009568 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/08 10:37:54.009687 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/08 10:37:54.009730 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/08 10:37:54.009563 sync.go:41: INFO Start sending events to output
2022/03/08 10:38:14.011806 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/08 10:38:14.012205 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/08 10:38:14.012487 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/08 10:38:14.012918 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/08 10:38:14.013022 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/08 10:38:19.035805 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:38:19.036009 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:38:20.040065 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:38:20.040125 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:38:22.045063 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:38:22.045095 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:38:24.005283 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=5 filebeat.harvester.running=5 filebeat.harvester.started=5 libbeat.publisher.published_events=76 registrar.writes=1
2022/03/08 10:38:26.052068 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:38:26.052112 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:38:34.061262 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:38:34.061306 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:38:50.080068 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:38:50.080130 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:38:54.005399 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:39:22.098287 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:39:22.098320 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:39:24.005347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:39:54.005256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:40:22.120045 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:40:22.120084 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:40:24.005307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:40:54.005248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:41:22.140202 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:41:22.140307 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:41:24.005272 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:41:54.005233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:42:22.156670 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:42:22.156737 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:42:24.005209 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:42:54.005223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:43:19.027304 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/08 10:43:22.176056 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:43:22.176096 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:43:24.005263 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/08 10:43:54.005303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:44:22.195313 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:44:22.195382 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:44:24.005253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:44:54.007430 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:45:22.213657 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:45:22.213699 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:45:24.005344 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:45:54.011346 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:46:22.231569 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:46:22.231615 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:46:24.005226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:46:54.005201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:47:22.250272 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:47:22.250324 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:47:24.005225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:47:54.005226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:48:22.267761 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:48:22.267802 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:48:24.005309 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:48:54.005360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:49:22.284517 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:49:22.284560 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:49:24.005247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:49:54.005240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:50:22.303387 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:50:22.303435 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:50:24.005228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:50:54.005301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:51:22.322344 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:51:22.322388 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:51:24.005322 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:51:54.005225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:52:22.339715 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:52:22.339843 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:52:24.005305 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:52:54.005240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:53:22.357799 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:53:22.357846 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:53:24.005226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:53:54.005268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:54:22.375610 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:54:22.375645 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:54:24.005240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:54:54.005331 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:55:22.394100 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:55:22.394141 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:55:24.005308 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:55:54.005289 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:56:22.412061 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:56:22.412101 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:56:24.005265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:56:54.005281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:57:22.432344 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:57:22.432385 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:57:24.005248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:57:54.005250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:58:22.450530 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:58:22.450582 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:58:24.005220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:58:54.005289 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:59:22.467644 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:59:22.467680 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:59:24.005277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:59:54.005281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:00:22.485226 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:00:22.485260 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:00:24.005224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:00:54.005229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:01:22.502815 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:01:22.502864 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:01:24.005301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:01:54.005370 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:02:22.521413 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:02:22.521441 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:02:24.005238 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:02:54.005307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:03:22.537684 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:03:22.537735 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:03:24.005252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:03:54.005553 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:04:22.553381 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:04:22.553419 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:04:24.005316 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:04:54.005299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:05:22.573059 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:05:22.573096 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:05:24.005363 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:05:54.005219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:06:22.590772 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:06:22.590823 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:06:24.005273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:06:54.005309 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:07:22.611271 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:07:22.611324 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:07:24.005342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:07:54.005261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:08:22.629046 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:08:22.629094 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:08:24.005404 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:08:54.005224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:09:22.645751 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:09:22.645787 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:09:24.005235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:09:54.005227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:10:22.662618 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:10:22.662672 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:10:24.005315 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:10:54.005260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:11:22.682250 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:11:22.682292 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:11:24.005290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:11:54.005229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:12:22.700147 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:12:22.700180 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:12:24.005224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:12:54.005297 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:13:22.717810 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:13:22.717865 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:13:24.005323 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:13:54.005269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:14:22.734619 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:14:22.734653 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:14:24.005244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:14:54.005293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:15:22.753296 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:15:22.753330 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:15:24.005229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:15:54.005246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:16:22.769901 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:16:22.769958 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:16:24.005239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:16:54.005221 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:17:22.789500 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:17:22.789538 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:17:24.005218 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:17:54.005377 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:18:22.807061 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:18:22.807096 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:18:24.005246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:18:54.005295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:19:22.823275 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:19:22.823317 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:19:24.005241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:19:54.005249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:20:22.840238 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:20:22.840276 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:20:24.005299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:20:54.005197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:21:22.858121 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:21:22.858177 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:21:24.005204 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:21:54.005325 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:22:22.876974 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:22:22.877061 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:22:24.005353 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:22:54.005315 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:23:22.893188 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:23:22.893230 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:23:24.005196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:23:54.005250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:24:22.909816 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:24:22.909851 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:24:24.005279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:24:54.005423 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:25:22.927801 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:25:22.927846 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:25:24.005282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:25:54.005355 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:26:22.943669 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:26:22.943703 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:26:24.005231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:26:54.005281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:27:22.964834 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:27:22.964867 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:27:24.005309 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:27:54.005213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:28:22.983783 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:28:22.983834 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:28:24.005202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:28:54.005287 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:29:23.001735 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:29:23.001785 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:29:24.005206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:29:54.005408 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:30:23.019496 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:30:23.019532 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:30:24.005261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:30:54.005290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:31:23.035517 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:31:23.035549 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:31:24.005570 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:31:54.005270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:32:23.051772 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:32:23.051831 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:32:24.005304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:32:54.005263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:33:23.067643 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:33:23.067678 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:33:24.005186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:33:54.005181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:34:23.086355 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:34:23.086476 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:34:24.005329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:34:54.005273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:35:23.104203 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:35:23.104237 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:35:24.005219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:35:54.005254 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:36:23.121287 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:36:23.121328 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:36:24.005200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:36:54.005409 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:37:23.138898 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:37:23.138941 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:37:24.005237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:37:54.005378 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:38:23.158078 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:38:23.158116 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:38:24.005221 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:38:54.007229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:39:23.176053 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:39:23.176092 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:39:24.005196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:39:54.005261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:40:23.192914 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:40:23.192953 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:40:24.005242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:40:54.005259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:41:23.210944 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:41:23.210988 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:41:24.005153 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:41:54.005387 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:42:23.228965 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:42:23.228998 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:42:24.005206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:42:54.005263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:43:23.247438 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:43:23.247475 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:43:24.005300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:43:54.005236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:44:23.265283 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:44:23.265330 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:44:24.005228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:44:54.005253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:45:23.283226 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:45:23.283278 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:45:24.005267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:45:54.005240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:46:23.300616 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:46:23.300662 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:46:24.005298 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:46:54.005279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:47:23.318505 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:47:23.318542 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:47:24.005280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:47:54.005224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:48:23.336454 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:48:23.336493 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:48:24.005261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:48:54.005328 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:49:23.354614 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:49:23.354666 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:49:24.005225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:49:54.005344 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:50:23.372391 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:50:23.372431 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:50:24.005234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:50:54.005413 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:51:23.391038 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:51:23.391092 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:51:24.005219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:51:54.005295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:52:23.408062 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:52:23.408107 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:52:24.009238 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:52:54.005234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:53:23.425412 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:53:23.425461 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:53:24.005238 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:53:54.005262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:54:23.444464 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:54:23.444496 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:54:24.006327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:54:54.005236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:55:23.460337 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:55:23.460367 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:55:24.005233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:55:54.005205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:56:23.476932 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:56:23.477147 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:56:24.005214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:56:54.005282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:57:23.493292 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:57:23.493330 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:57:24.005243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:57:54.005289 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:58:23.515452 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:58:23.515496 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:58:24.005213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:58:54.005265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:59:23.532710 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:59:23.532747 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:59:24.005327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:59:54.005230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:00:23.549596 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:00:23.549651 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:00:24.005280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:00:54.005335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:01:23.569658 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:01:23.569690 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:01:24.005228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:01:54.005333 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:02:23.587257 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:02:23.587295 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:02:24.005264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:02:54.005253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:03:23.607307 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:03:23.607362 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:03:24.005310 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:03:54.005255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:04:23.626024 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:04:23.626194 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:04:24.005269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:04:54.005276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:05:23.644186 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:05:23.644218 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:05:24.005262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:05:54.005258 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:06:23.659844 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:06:23.659885 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:06:24.005264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:06:54.005290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:07:23.677153 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:07:23.677192 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:07:24.005365 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:07:54.005362 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:08:23.694667 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:08:23.694790 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:08:24.005222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:08:54.005354 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:09:23.715805 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:09:23.715835 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:09:24.005321 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:09:54.005441 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:10:23.732453 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:10:23.732497 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:10:24.005302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:10:54.005356 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:11:23.748993 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:11:23.749034 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:11:24.005300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:11:54.005272 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:12:23.764456 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:12:23.764495 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:12:24.005227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:12:54.005225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:13:23.781639 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:13:23.781672 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:13:24.005234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:13:54.005277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:14:23.799211 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:14:23.799247 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:14:24.005414 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:14:54.005347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:15:23.817706 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:15:23.817744 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:15:24.005221 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:15:54.005190 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:16:23.822295 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:16:23.822340 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:16:24.005221 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:16:54.005220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:17:23.828316 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:17:23.828355 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:17:24.005378 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:17:54.005293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:18:23.833807 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:18:23.833854 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:18:24.005280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:18:54.005221 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:19:23.840046 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:19:23.840087 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:19:24.005244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:19:54.005225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:20:23.846426 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:20:23.846713 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:20:24.005316 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:20:54.005598 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:21:23.852407 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:21:23.852448 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:21:24.005285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:21:54.005288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:22:23.858946 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:22:23.858980 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:22:24.005277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:22:54.005218 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:23:23.865177 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:23:23.865459 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:23:24.005219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:23:54.005312 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:24:23.871117 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:24:23.871147 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:24:24.005244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:24:54.005248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:25:23.876891 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:25:23.877032 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:25:24.005224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:25:54.005182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:26:23.883531 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:26:23.883576 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:26:24.005180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:26:54.005345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:27:23.889037 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:27:23.889117 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:27:24.005375 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:27:54.005311 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:28:23.894625 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:28:23.894656 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:28:24.005241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:28:54.005258 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:29:23.900603 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:29:23.900638 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:29:24.005499 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:29:54.005312 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:30:23.905934 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:30:23.905966 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:30:24.005301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:30:54.005223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:31:23.911825 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:31:23.911870 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:31:24.005243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:31:54.005241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:32:23.917072 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:32:23.917105 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:32:24.005282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:32:54.005195 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:33:23.924591 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:33:23.924627 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:33:24.005260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:33:54.005206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:34:23.930493 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:34:23.930525 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:34:24.005216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:34:54.005290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:35:23.936822 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:35:23.936918 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:35:24.005213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:35:54.005297 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:36:23.945004 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:36:23.945039 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:36:24.005294 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:36:54.005246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:37:23.950686 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:37:23.950719 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:37:24.005253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:37:54.005272 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:38:23.957074 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:38:23.957105 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:38:24.005245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:38:54.005265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:39:23.962860 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:39:23.962894 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:39:24.005292 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:39:54.005308 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:40:23.969067 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:40:23.969106 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:40:24.005234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:40:54.005255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:41:23.974530 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:41:23.974574 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:41:24.005236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:41:54.005254 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:42:23.980972 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:42:23.981014 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:42:24.005212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:42:54.005297 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:43:23.989150 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:43:23.989198 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:43:24.005253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:43:54.005325 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:44:24.003226 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:44:24.003327 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:44:24.005227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:44:54.005399 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:45:24.005388 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:45:24.008904 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:45:24.008935 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:45:54.005331 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:46:24.005290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:46:24.015320 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:46:24.015359 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:46:54.005356 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:47:24.005269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:47:24.020707 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:47:24.020754 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:47:54.005250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:48:24.005268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:48:24.027426 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:48:24.027452 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:48:54.005255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:49:24.005284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:49:24.033420 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:49:24.033444 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:49:54.005369 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:50:24.005221 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:50:24.042048 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:50:24.042096 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:50:54.005283 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:51:24.005200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:51:24.047762 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:51:24.047791 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:51:54.005184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:52:24.005224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:52:24.052903 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:52:24.052952 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:52:54.005275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:53:24.005257 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:53:24.060208 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:53:24.060249 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:53:54.005226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:54:24.006209 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:54:24.066497 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:54:24.066670 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:54:54.005220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:55:24.005270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:55:24.073106 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:55:24.073152 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:55:54.005235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:56:24.005220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:56:24.078559 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:56:24.078598 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:56:54.005414 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:57:24.005248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:57:24.084463 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:57:24.084500 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:57:54.005277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:58:24.005286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:58:24.090351 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:58:24.090383 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:58:54.005386 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:59:24.005318 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:59:24.095920 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:59:24.095957 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:59:54.005223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:00:24.005215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:00:24.101487 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:00:24.101519 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:00:54.005257 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:01:24.005248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:01:24.107795 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:01:24.107831 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:01:54.005201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:02:24.005223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:02:24.113176 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:02:24.113297 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:02:54.005275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:03:24.005305 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:03:24.119010 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:03:24.119046 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:03:54.005233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:04:24.005368 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:04:24.125164 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:04:24.125195 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:04:54.005306 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:05:24.005234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:05:24.131225 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:05:24.131257 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:05:54.005244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:06:24.005205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:06:24.137278 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:06:24.137305 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:06:54.005286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:07:24.005237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:07:24.142855 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:07:24.142892 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:07:54.005288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:08:24.005233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:08:24.148922 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:08:24.148965 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:08:54.005228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:09:24.005298 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:09:24.155756 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:09:24.155787 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:09:54.005203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:10:24.005236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:10:24.162168 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:10:24.162214 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:10:54.005210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:11:24.005217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:11:24.168278 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:11:24.168312 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:11:54.005233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:12:24.005239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:12:24.175322 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:12:24.175372 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:12:54.005295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:13:24.005381 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:13:24.181370 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:13:24.181411 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:13:54.005293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:14:24.005635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:14:24.190283 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:14:24.190325 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:14:54.005419 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:15:24.005275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:15:24.201504 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:15:24.201558 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:15:54.005244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:16:24.005202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:16:24.207113 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:16:24.207143 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:16:54.005367 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:17:24.005182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:17:24.212719 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:17:24.212975 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:17:54.005249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:18:24.005217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:18:24.222900 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:18:24.222941 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:18:54.005402 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:19:24.005260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:19:24.230634 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:19:24.230685 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:19:54.005246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:20:24.005291 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:20:24.240728 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:20:24.240777 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:20:54.005284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:21:24.005326 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:21:24.248111 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:21:24.248144 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:21:54.005207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:22:24.005378 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:22:24.253485 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:22:24.253520 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:22:54.005299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:23:24.005273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:23:24.258978 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:23:24.259012 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:23:54.005323 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:24:24.005338 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:24:24.265557 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:24:24.265598 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:24:54.005302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:25:24.005244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:25:24.271668 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:25:24.271706 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:25:54.005245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:26:24.005222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:26:24.276924 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:26:24.276963 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:26:54.005314 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:27:24.005269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:27:24.283868 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:27:24.283912 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:27:54.005218 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:28:24.005269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:28:24.289138 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:28:24.289172 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:28:54.005207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:29:24.005203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:29:24.294189 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:29:24.294221 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:29:54.005223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:30:24.005278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:30:24.300064 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:30:24.300117 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:30:54.005391 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:31:24.005231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:31:24.305541 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:31:24.305589 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:31:54.005317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:32:24.005206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:32:24.312139 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:32:24.312682 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:32:54.005323 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:33:24.005460 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:33:24.318551 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:33:24.318585 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:33:54.005180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:34:24.005170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:34:24.323969 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:34:24.324005 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:34:54.005337 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:35:24.005291 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:35:24.330142 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:35:24.330183 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:35:54.005209 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:36:24.005197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:36:24.335790 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:36:24.335829 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:36:54.005216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:37:24.005227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:37:24.342192 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:37:24.342253 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:37:54.005247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:38:24.005225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:38:24.348676 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:38:24.348706 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:38:54.005204 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:39:24.005241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:39:24.353842 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:39:24.353873 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:39:54.005243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:40:24.005232 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:40:24.359006 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:40:24.359037 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:40:54.005311 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:41:24.005246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:41:24.364448 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:41:24.364639 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:41:54.005303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:42:24.005255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:42:24.370472 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:42:24.370645 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:42:54.005249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:43:24.005205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:43:24.375687 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:43:24.375720 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:43:54.005219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:44:24.005210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:44:24.382702 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:44:24.382735 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:44:54.005279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:45:24.005264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:45:24.390095 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:45:24.390144 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:45:54.005470 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:46:24.005232 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:46:24.396088 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:46:24.396118 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:46:54.005263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:47:24.005278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:47:24.402377 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:47:24.402412 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:47:54.005247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:48:24.005292 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:48:24.408351 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:48:24.408403 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:48:54.005219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:49:24.005282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:49:24.413928 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:49:24.414093 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:49:54.005224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:50:24.005383 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:50:24.419867 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:50:24.419907 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:50:54.005216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:51:24.005226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:51:24.425556 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:51:24.425595 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:51:54.005278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:52:24.005290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:52:24.433155 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:52:24.433189 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:52:54.005240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:53:24.005282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:53:24.438612 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:53:24.438643 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:53:54.005264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:54:24.005250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:54:24.445175 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:54:24.445210 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:54:54.005241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:55:24.005275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:55:24.451027 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:55:24.451076 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:55:54.005230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:56:24.005498 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:56:24.458658 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:56:24.458688 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:56:54.005268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:57:24.005220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:57:24.464287 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:57:24.464319 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:57:54.005268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:58:24.005201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:58:24.469196 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:58:24.469309 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:58:54.005215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:59:24.005206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 13:59:24.474450 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:59:24.474498 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 13:59:54.005216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 14:00:24.005269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 14:00:24.480890 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 14:00:24.480924 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 14:00:54.005268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 14:01:24.005227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 14:01:24.487023 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 14:01:24.487194 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 14:01:54.005258 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 14:02:24.005292 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 14:02:24.492633 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 14:02:24.492796 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 14:02:54.005193 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 14:03:24.005312 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 14:03:24.498820 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 14:03:24.498856 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 14:03:54.005239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 14:04:24.005304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 14:04:24.505081 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 14:04:24.505131 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 14:04:54.005234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 14:05:24.005382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 14:05:24.513936 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 14:05:24.513976 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 14:05:54.005197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 14:06:24.005265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 14:06:24.519392 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 14:06:24.519521 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 14:06:54.005408 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 14:07:24.005360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 14:07:24.524873 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 14:07:24.524905 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 14:07:54.005265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 14:08:24.005300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 14:08:24.529632 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 14:08:24.529664 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 14:08:54.005316 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 14:09:24.005228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 14:09:24.538781 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 14:09:24.538824 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 14:09:54.005305 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 14:10:24.005176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 14:10:24.545162 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 14:10:24.545202 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 14:10:54.005202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 14:11:24.005224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 14:11:24.551206 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 14:11:24.551238 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 14:11:54.005252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 14:12:24.005191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 14:12:24.556942 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 14:12:24.556976 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 14:12:54.005224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 14:13:24.005231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 14:13:24.563524 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 14:13:24.563562 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 14:13:54.005279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 14:14:24.005192 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 14:14:24.569948 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 14:14:24.569987 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 14:14:54.005252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 14:15:24.005438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 14:15:24.575877 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 14:15:24.575911 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host