By type
2022/04/02 03:09:55.934207 beat.go:285: INFO Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs]
2022/04/02 03:09:55.934334 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/04/02 03:09:55.934520 logstash.go:90: INFO Max Retries set to: 3
2022/04/02 03:09:55.934686 outputs.go:108: INFO Activated logstash as output plugin.
2022/04/02 03:09:55.934900 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-x7kf4
2022/04/02 03:09:55.935133 metrics.go:23: INFO Metrics logging every 30s
2022/04/02 03:09:55.935297 async.go:63: INFO Flush Interval set to: 1s
2022/04/02 03:09:55.935316 async.go:64: INFO Max Bulk Size set to: 2048
2022/04/02 03:09:55.936113 beat.go:221: INFO filebeat start running.
2022/04/02 03:09:55.936183 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/04/02 03:09:55.945357 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/04/02 03:09:55.945446 registrar.go:123: INFO States Loaded from registrar: 0
2022/04/02 03:09:55.945531 crawler.go:38: INFO Loading Prospectors: 1
2022/04/02 03:09:55.945827 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/04/02 03:09:55.945940 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/04/02 03:09:55.945961 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/04/02 03:09:55.945975 registrar.go:236: INFO Starting Registrar
2022/04/02 03:09:55.946046 sync.go:41: INFO Start sending events to output
2022/04/02 03:09:55.946088 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/04/02 03:10:15.948549 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/04/02 03:10:15.948702 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/04/02 03:10:15.949019 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/04/02 03:10:15.949183 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/04/02 03:10:15.949247 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/04/02 03:10:15.979195 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:10:15.979235 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:10:16.982617 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:10:16.982660 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:10:18.992807 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:10:18.992885 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:10:23.002577 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:10:23.002613 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:10:25.935485 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=5 filebeat.harvester.running=5 filebeat.harvester.started=5 libbeat.publisher.published_events=76 registrar.writes=1
2022/04/02 03:10:31.010783 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:10:31.010827 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:10:47.031681 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:10:47.031885 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:10:55.935452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:11:19.048642 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:11:19.048692 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:11:25.936653 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:11:55.935411 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:12:19.067767 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:12:19.067859 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:12:25.935494 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:12:55.935528 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:13:19.090596 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:13:19.090643 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:13:25.935472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:13:55.935420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:14:19.109401 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:14:19.109691 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:14:25.935559 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:14:55.935538 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:15:19.128212 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:15:19.128255 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:15:20.960973 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/04/02 03:15:25.935436 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/04/02 03:15:55.935499 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:16:19.145488 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:16:19.145538 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:16:25.935398 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:16:55.935589 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:17:19.165534 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:17:19.165567 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:17:25.935543 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:17:55.935538 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:18:19.185414 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:18:19.185477 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:18:25.935494 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:18:55.935422 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:19:19.203263 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:19:19.203296 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:19:25.935420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:19:55.935589 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:20:19.220109 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:20:19.220162 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:20:25.935484 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:20:55.935552 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:21:19.240048 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:21:19.240090 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:21:25.935565 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:21:55.935474 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:22:19.259052 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:22:19.259112 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:22:25.935615 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:22:55.935523 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:23:19.277346 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:23:19.277382 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:23:25.935557 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:23:55.935451 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:24:19.296760 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:24:19.296809 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:24:25.935552 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:24:55.935511 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:25:19.314079 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:25:19.314113 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:25:25.935527 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:25:55.935772 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:26:19.334678 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:26:19.334727 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:26:25.935459 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:26:55.935453 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:27:19.352602 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:27:19.352767 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:27:25.935490 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:27:55.935456 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:28:19.371327 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:28:19.371518 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:28:25.935507 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:28:55.935522 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:29:19.390755 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:29:19.390796 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:29:25.935549 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:29:55.935488 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:30:19.410262 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:30:19.410331 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:30:25.935532 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:30:55.935537 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:31:19.427824 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:31:19.427863 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:31:25.935536 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:31:55.935516 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:32:19.449346 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:32:19.449455 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:32:25.935509 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:32:55.935509 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:33:19.467950 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:33:19.468006 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:33:25.935516 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:33:55.935570 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:34:19.488336 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:34:19.488497 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:34:25.935687 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:34:55.935473 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:35:19.508153 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:35:19.508212 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:35:25.935517 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:35:55.935417 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:36:19.526673 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:36:19.526722 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:36:25.935452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:36:55.935474 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:37:19.545623 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:37:19.545685 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:37:25.935471 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:37:55.935565 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:38:19.575787 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:38:19.575832 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:38:25.935524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:38:55.935454 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:39:19.592627 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:39:19.592669 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:39:25.935608 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:39:55.935465 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:40:19.608485 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:40:19.608523 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:40:25.935480 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:40:55.935473 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:41:19.625503 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:41:19.625552 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:41:25.935502 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:41:55.935450 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:42:19.642343 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:42:19.642386 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:42:25.935615 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:42:55.935563 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:43:19.658221 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:43:19.658258 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:43:25.935470 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:43:55.935449 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:44:19.676805 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:44:19.676852 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:44:25.935509 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:44:55.935486 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:45:19.697290 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:45:19.697339 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:45:25.935496 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:45:55.935624 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:46:19.715580 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:46:19.715635 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:46:25.935465 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:46:55.936730 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:47:19.733725 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:47:19.733770 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:47:25.935519 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:47:55.935482 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:48:19.751252 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:48:19.751299 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:48:25.935473 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:48:55.935583 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:49:19.767747 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:49:19.767791 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:49:25.935484 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:49:55.935562 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:50:19.784548 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:50:19.784605 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:50:25.935496 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:50:55.935546 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:51:19.803269 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:51:19.803310 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:51:25.935470 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:51:55.935422 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:52:19.823739 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:52:19.823890 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:52:25.935458 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:52:55.935483 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:53:19.845892 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:53:19.845949 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:53:25.935510 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:53:55.935493 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:54:19.851236 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:19.851307 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:25.935514 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:54:55.935465 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:55:19.854392 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:55:19.854430 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:55:25.935484 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:55:55.935571 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:56:19.859165 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:56:19.859208 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:56:25.935623 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:56:55.935463 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:57:19.862382 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:57:19.862436 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:57:25.935526 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:57:55.935539 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:58:19.865869 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:58:19.865901 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:58:25.935439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:58:55.935877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:59:19.876362 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:59:19.876396 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:59:25.935600 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:59:55.935495 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:00:19.879815 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:00:19.879846 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:00:25.935590 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:00:55.935456 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:01:19.882866 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:01:19.882899 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:01:25.935475 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:01:55.936418 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:02:19.886319 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:02:19.886352 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:02:25.935490 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:02:55.935694 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:03:19.893559 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:03:19.893603 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:03:25.935470 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:03:55.935532 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:04:19.897359 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:04:19.897405 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:04:25.935497 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:04:55.935521 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:05:19.901451 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:05:19.901487 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:05:25.935566 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:05:55.935614 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:06:19.904610 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:06:19.904644 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:06:25.935456 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:06:55.935540 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:07:19.907861 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:07:19.907901 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:07:25.935469 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:07:55.935498 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:08:19.911044 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:08:19.911075 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:08:25.935435 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:08:55.935452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:09:19.914225 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:09:19.914264 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:09:25.935507 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:09:55.935472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:10:19.918204 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:10:19.918248 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:10:25.935452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:10:55.935514 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:11:19.922017 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:11:19.922075 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:11:25.935546 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:11:55.935526 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:12:19.925956 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:12:19.925990 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:12:25.935455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:12:55.935485 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:13:19.929768 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:13:19.929810 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:13:25.935390 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:13:55.935413 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:14:19.935025 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:14:19.935061 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:14:25.935437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:14:55.935421 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:15:19.938217 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:15:19.938336 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:15:25.935466 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:15:55.935428 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:16:19.942284 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:16:19.942339 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:16:25.935511 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:16:55.935464 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:17:19.946470 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:17:19.946503 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:17:25.935434 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:17:55.935468 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:18:19.949505 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:18:19.949545 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:18:25.935459 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:18:55.935541 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:19:19.952904 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:19:19.952932 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:19:25.935456 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:19:55.935523 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:20:19.956433 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:20:19.956479 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:20:25.935643 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:20:55.935485 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:21:19.960663 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:21:19.960703 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:21:25.935537 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:21:55.935491 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:22:19.965816 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:22:19.965866 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:22:25.935455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:22:55.935436 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:23:19.969558 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:23:19.969590 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:23:25.935490 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:23:55.935481 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:24:19.972709 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:24:19.972747 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:24:25.935478 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:24:55.935514 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:25:19.976480 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:25:19.976513 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:25:25.935522 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:25:55.935502 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:26:19.979865 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:26:19.979920 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:26:25.935525 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:26:55.935395 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:27:19.983146 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:27:19.983179 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:27:25.935575 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:27:55.935491 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:28:19.986357 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:28:19.986398 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:28:25.935433 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:28:55.935670 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:29:19.989611 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:29:19.989641 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:29:25.935475 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:29:55.935434 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:30:19.993258 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:30:19.993292 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:30:25.935819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:30:55.935472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:31:19.997458 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:31:19.997509 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:31:25.935526 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:31:55.935504 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:32:20.001162 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:32:20.001195 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:32:25.935475 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:32:55.935498 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:33:20.004187 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:33:20.004221 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:33:25.935514 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:33:55.935419 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:34:20.008294 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:34:20.008327 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:34:25.935418 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:34:55.935476 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:35:20.012089 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:35:20.012163 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:35:25.935392 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:35:55.935491 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:36:20.015517 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:36:20.015547 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:36:25.935464 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:36:55.935459 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:37:20.019893 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:37:20.019934 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:37:25.935453 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:37:55.935461 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:38:20.022642 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:38:20.022673 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:38:25.935733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:38:55.935459 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:39:20.025749 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:39:20.025781 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:39:25.935470 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:39:55.935506 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:40:20.029556 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:40:20.029596 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:40:25.935635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:40:55.935468 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:41:20.033263 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:41:20.033292 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:41:25.935521 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:41:55.935436 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:42:20.036327 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:42:20.036395 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:42:25.935447 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:42:55.935499 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:43:20.039272 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:43:20.039300 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:43:25.935396 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:43:55.935525 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:44:20.042730 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:44:20.042771 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:44:25.935424 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:44:55.935422 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:45:20.046570 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:45:20.046850 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:45:25.935487 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:45:55.935491 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:46:20.050922 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:46:20.050971 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:46:25.935475 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:46:55.935574 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:47:20.055238 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:47:20.055291 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:47:25.935439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:47:55.936241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:48:20.058336 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:48:20.058376 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:48:25.935435 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:48:55.935513 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:49:20.061370 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:49:20.061406 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:49:25.935513 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:49:55.935490 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:50:20.064980 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:50:20.065019 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:50:25.935559 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:50:55.935480 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:51:20.068929 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:51:20.068963 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:51:25.935632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:51:55.935455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:52:20.072151 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:52:20.072197 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:52:25.935518 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:52:55.935481 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:53:20.076085 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:53:20.076131 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:53:25.935615 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:53:55.935501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:54:20.079438 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:54:20.079474 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:54:25.935432 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:54:55.935502 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:55:20.082909 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:55:20.082961 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:55:25.935605 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:55:55.935593 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:56:20.087580 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:56:20.087726 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:56:25.935494 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:56:55.935568 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:57:20.091561 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:57:20.091598 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:57:25.935567 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:57:55.935573 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:58:20.094699 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:58:20.094731 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:58:25.935468 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:58:55.935477 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:59:20.098195 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:59:20.098224 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:59:25.935494 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:59:55.936289 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:00:20.104024 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:00:20.104060 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:00:25.935468 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:00:55.935543 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:01:20.109593 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:01:20.109707 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:01:25.935526 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:01:55.935518 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:02:20.117776 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:02:20.117991 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:02:25.935487 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:02:55.935482 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:03:20.120962 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:03:20.120999 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:03:25.935449 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:03:55.935506 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:04:20.127655 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:04:20.127715 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:04:25.935462 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:04:55.935545 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:05:20.136977 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:05:20.137015 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:05:25.935575 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:05:55.935487 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:06:20.140266 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:06:20.140317 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:06:25.935498 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:06:55.935512 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:07:20.143651 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:07:20.143688 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:07:25.935469 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:07:55.935569 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:08:20.147505 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:08:20.147561 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:08:25.935529 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:08:55.935457 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:09:20.152268 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:09:20.152323 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:09:25.935436 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:09:55.935482 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:10:20.156060 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:10:20.156099 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:10:25.935446 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:10:55.935511 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:11:20.159898 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:11:20.159935 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:11:25.935545 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:11:55.935537 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:12:20.167081 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:12:20.167143 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:12:25.935626 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:12:55.935564 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:13:20.170589 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:13:20.170621 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:13:25.935435 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:13:55.935461 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:14:20.188684 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:14:20.188712 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:14:25.935488 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:14:55.935714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:15:20.205857 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:15:20.205911 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:15:25.935457 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:15:55.935407 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:16:20.235304 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:16:20.235328 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:16:25.935435 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:16:55.935535 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:17:20.253676 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:17:20.253716 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:17:25.935442 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:17:55.935507 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:18:20.270934 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:18:20.271030 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:18:25.935527 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:18:55.935440 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:19:20.290453 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:19:20.290498 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:19:25.935490 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:19:55.935507 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:20:20.309037 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:20:20.309083 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:20:25.935576 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:20:55.935622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:21:20.328014 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:21:20.328051 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:21:25.935516 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:21:55.935484 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:22:20.347301 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:22:20.347403 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:22:25.935515 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:22:55.935599 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:23:20.375753 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:23:20.375811 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:23:25.935520 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:23:55.935549 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:24:20.393407 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:24:20.393456 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:24:25.935433 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:24:55.935413 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:25:20.410691 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:25:20.410729 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:25:25.935517 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:25:55.935554 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:26:20.428447 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:26:20.428591 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:26:25.935475 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:26:55.935442 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:27:20.446629 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:27:20.446670 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:27:25.935525 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:27:55.935448 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:28:20.465317 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:28:20.465381 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:28:25.935469 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:28:55.935434 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:29:20.484160 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:29:20.484197 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:29:25.935417 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:29:55.935687 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:30:20.503493 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:30:20.503534 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:30:25.935488 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:30:55.935518 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:31:20.521610 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:31:20.521680 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:31:25.935522 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:31:55.935502 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:32:20.541310 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:32:20.541338 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:32:25.935545 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:32:55.935472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:33:20.559164 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:33:20.559218 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:33:25.935614 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:33:55.935573 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:34:20.580406 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:34:20.580456 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:34:25.935503 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:34:55.935480 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:35:20.600885 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:35:20.600929 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:35:25.935592 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:35:55.935498 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:36:20.620652 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:36:20.620722 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:36:25.935452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:36:55.935546 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:37:20.637937 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:37:20.637986 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:37:25.935474 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:37:55.935524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:38:20.656374 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:38:20.656412 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:38:25.935464 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:38:55.935432 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:39:20.677300 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:39:20.677530 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:39:25.935652 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:39:55.935482 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:40:20.694076 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:40:20.694120 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:40:25.935484 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:40:55.935482 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:41:20.714416 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:41:20.714471 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:41:25.935528 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:41:55.935480 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:42:20.738049 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:42:20.738566 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:42:25.935479 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:42:55.935500 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:43:20.758788 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:43:20.758943 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:43:25.935411 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:43:55.935481 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:44:20.780276 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:44:20.780348 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:44:25.935595 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:44:55.935482 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:45:20.801407 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:45:20.801446 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:45:25.935471 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:45:55.935544 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:46:20.819964 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:46:20.820004 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:46:25.935467 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:46:55.935452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:47:20.840927 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:47:20.840993 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:47:25.935491 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:47:55.935463 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:48:20.862324 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:48:20.862483 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:48:25.935431 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:48:55.935428 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:49:20.880815 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:49:20.880854 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:49:25.935491 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:49:55.935599 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:50:20.900030 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:50:20.900104 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:50:25.935501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:50:55.935470 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:51:20.918403 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:51:20.918455 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:51:25.935437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:51:55.935499 metrics.go:34: INFO No non-zero metrics in the last 30s