By type
2022/03/22 10:51:12.055124 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/22 10:51:12.055225 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/22 10:51:12.055472 logstash.go:90: INFO Max Retries set to: 3
2022/03/22 10:51:12.055667 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/22 10:51:12.055884 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-6cdm5
2022/03/22 10:51:12.056229 async.go:63: INFO Flush Interval set to: 1s
2022/03/22 10:51:12.056260 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/22 10:51:12.058031 metrics.go:23: INFO Metrics logging every 30s
2022/03/22 10:51:12.058396 beat.go:221: INFO filebeat start running.
2022/03/22 10:51:12.058676 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/22 10:51:12.064726 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/22 10:51:12.064874 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/22 10:51:12.064994 crawler.go:38: INFO Loading Prospectors: 1
2022/03/22 10:51:12.065378 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/22 10:51:12.065591 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/22 10:51:12.065618 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/22 10:51:12.065642 registrar.go:236: INFO Starting Registrar
2022/03/22 10:51:12.065705 sync.go:41: INFO Start sending events to output
2022/03/22 10:51:12.065828 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/22 10:51:42.058755 metrics.go:39: INFO Non-zero metrics in the last 30s: registrar.writes=1
2022/03/22 10:51:42.118685 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/22 10:51:42.118977 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/22 10:51:42.119542 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/22 10:51:42.119906 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/22 10:51:42.120316 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/22 10:51:42.147542 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:51:42.147586 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:51:43.191735 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:51:43.191830 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:51:45.208825 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:51:45.208966 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:51:49.228082 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:51:49.228137 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:51:57.300929 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:51:57.300979 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:52:12.058520 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=36
2022/03/22 10:52:13.366679 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:52:13.367812 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:52:42.059489 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 10:52:45.414131 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:52:45.414202 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:53:12.059912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 10:53:42.058635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 10:53:45.443253 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:53:45.443304 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:54:12.058757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 10:54:42.058454 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 10:54:45.526408 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:54:45.526449 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:55:12.059447 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 10:55:42.058473 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 10:55:45.547691 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:55:45.547772 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:56:12.058493 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 10:56:42.058559 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 10:56:45.582372 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:56:45.582750 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:56:47.180924 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/22 10:57:12.058495 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/22 10:57:42.059549 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 10:57:45.604166 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:57:45.604218 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:58:12.063786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 10:58:42.059139 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 10:58:45.630055 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:58:45.630103 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:59:12.058474 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 10:59:42.058778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 10:59:45.651811 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 10:59:45.651913 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:00:12.058423 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:00:42.061843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:00:45.685746 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:00:45.685790 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:01:12.058412 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:01:42.058484 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:01:45.720375 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:01:45.720437 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:02:12.058488 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:02:42.059287 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:02:45.743969 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:02:45.744049 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:03:12.059303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:03:42.062151 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:03:45.781449 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:03:45.781517 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:04:12.058602 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:04:42.058594 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:04:45.821605 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:04:45.821651 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:05:12.063389 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:05:42.061422 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:05:45.843318 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:05:45.843379 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:06:12.058645 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:06:42.058727 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:06:45.887144 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:06:45.887215 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:07:12.058513 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:07:42.059243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:07:45.924195 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:07:45.924268 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:08:12.058785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:08:42.058470 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:08:45.945950 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:08:45.946004 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:09:12.063919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:09:42.058431 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:09:46.001452 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:09:46.001549 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:10:12.059047 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:10:42.059076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:10:46.054724 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:10:46.054784 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:11:12.059284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:11:42.058647 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:11:46.099698 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:11:46.099747 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:12:12.061615 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:12:42.058699 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:12:46.129595 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:12:46.129671 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:13:12.058579 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:13:42.059188 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:13:46.157425 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:13:46.157489 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:14:12.063543 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:14:42.058551 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:14:46.230281 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:14:46.230342 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:15:12.058527 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:15:42.059791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:15:46.293217 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:15:46.293284 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:16:12.058732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:16:42.058522 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:16:46.345958 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:16:46.346024 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:17:12.065424 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:17:42.059126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:17:46.389213 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:17:46.389262 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:18:12.059411 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:18:42.058492 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:18:46.419878 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:18:46.419931 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:19:12.058669 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:19:42.058648 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:19:46.446575 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:19:46.446643 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:20:12.059521 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:20:42.058452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:20:46.469878 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:20:46.469941 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:21:12.058534 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:21:42.063300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:21:46.507669 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:21:46.507731 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:22:12.058486 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:22:42.058532 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:22:46.525190 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:22:46.525232 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:23:12.058485 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:23:42.058432 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:23:46.544533 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:23:46.544586 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:24:12.058632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:24:42.058464 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:24:46.564331 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:24:46.564599 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:25:12.058463 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:25:42.058654 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:25:46.590474 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:25:46.590534 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:26:12.058625 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:26:42.058603 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:26:46.608252 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:26:46.608508 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:27:12.058354 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:27:42.058401 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:27:46.636159 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:27:46.636223 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:28:12.058643 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:28:42.059314 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:28:46.654649 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:28:46.654708 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:29:12.058787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:29:42.059883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:29:46.689434 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:29:46.689501 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:30:12.058439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:30:42.058580 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:30:46.708614 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:30:46.708669 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:31:12.063458 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:31:42.058646 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:31:46.731511 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:31:46.731571 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:32:12.058485 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:32:42.058498 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:32:46.753812 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:32:46.753862 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:33:12.058627 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:33:42.058465 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:33:46.782018 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:33:46.782078 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:34:12.060237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:34:42.058395 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:34:46.799831 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:34:46.799889 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:35:12.058427 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:35:42.058820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:35:46.818274 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:35:46.818327 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:36:12.059737 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:36:42.058451 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:36:46.838065 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:36:46.838106 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:37:12.058436 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:37:42.058533 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:37:46.859455 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:37:46.859509 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:38:12.058637 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:38:42.058524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:38:46.889923 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:38:46.890178 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:39:12.068462 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:39:42.058570 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:39:46.913344 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:39:46.913400 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:40:12.058401 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:40:42.058481 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:40:46.936116 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:40:46.936178 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:41:12.058502 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:41:42.058382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:41:46.956658 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:41:46.956743 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:42:12.058597 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:42:42.058504 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:42:46.987221 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:42:46.987312 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:43:12.060007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:43:42.058417 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:43:47.012066 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:43:47.012117 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:44:12.058489 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:44:42.058475 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:44:47.042908 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:44:47.042960 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:45:12.058479 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:45:42.058518 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:45:47.084788 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:45:47.084863 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:46:12.058517 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:46:42.058400 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:46:47.113323 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:46:47.113855 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:47:12.058528 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:47:42.058413 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:47:47.139209 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:47:47.139281 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:48:12.070217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:48:42.058691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:48:47.175250 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:48:47.175322 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:49:12.058462 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:49:42.058393 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:49:47.207862 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:49:47.207936 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:50:12.058488 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:50:42.058605 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:50:47.228496 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:50:47.228584 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:51:12.058546 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:51:42.058717 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:51:47.258690 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:51:47.258744 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:52:12.058916 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:52:42.058517 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:52:47.347129 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:52:47.347171 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:53:12.058524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:53:42.058762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:53:47.375209 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:53:47.375264 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:54:12.058426 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:54:42.058548 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:54:47.401365 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:54:47.401484 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:55:12.058453 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:55:42.058586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:55:47.435709 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:55:47.435766 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:56:12.058438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:56:42.058414 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:56:47.453258 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:56:47.453441 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:57:12.058468 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:57:42.062837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:57:47.490548 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:57:47.490590 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:58:12.058591 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:58:42.058448 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:58:47.514790 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:58:47.514905 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:59:12.058503 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:59:42.058539 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 11:59:47.533474 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 11:59:47.533524 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:00:12.059488 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:00:42.059695 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:00:47.551160 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:00:47.551236 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:01:12.058523 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:01:42.058401 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:01:47.588752 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:01:47.588811 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:02:12.058492 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:02:42.058384 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:02:47.608616 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:02:47.608678 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:03:12.058455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:03:42.058449 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:03:47.647873 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:03:47.647914 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:04:12.058604 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:04:42.058515 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:04:47.695021 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:04:47.695076 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:05:12.058491 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:05:42.058454 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:05:47.715871 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:05:47.715915 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:06:12.058454 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:06:42.059222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:06:47.739248 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:06:47.739316 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:07:12.058489 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:07:42.058941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:07:47.767182 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:07:47.767229 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:08:12.058577 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:08:42.058442 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:08:47.800899 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:08:47.801106 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:09:12.058419 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:09:42.059063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:09:47.829773 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:09:47.829864 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:10:12.058538 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:10:42.060176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:10:47.850938 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:10:47.851014 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:11:12.058688 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:11:42.058694 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:11:47.879980 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:11:47.880028 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:12:12.058630 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:12:42.058440 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:12:47.900022 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:12:47.900122 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:13:12.058464 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:13:42.058486 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:13:47.919151 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:13:47.919232 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:14:12.058363 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:14:42.059075 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:14:47.945533 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:14:47.945580 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:15:12.058403 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:15:42.059148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:15:47.992563 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:15:47.992723 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:16:12.058440 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:16:42.058491 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:16:48.013017 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:16:48.013113 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:17:12.059972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:17:42.060060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:17:48.035545 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:17:48.035924 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:18:12.058422 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:18:42.058504 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:18:48.067299 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:18:48.067514 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:19:12.058386 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:19:42.059189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:19:48.093978 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:19:48.094029 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:20:12.058360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:20:42.058573 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:20:48.112437 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:20:48.112504 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:21:12.058533 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:21:42.058514 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:21:48.137101 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:21:48.137144 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:22:12.058435 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:22:42.058512 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:22:48.161873 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:22:48.161943 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:23:12.058415 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:23:42.058475 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:23:48.188214 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:23:48.188276 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:24:12.058444 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:24:42.058662 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:24:48.210721 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:24:48.210770 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:25:12.058547 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:25:42.058506 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:25:48.229590 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:25:48.229634 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:26:12.058453 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:26:42.058535 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:26:48.249197 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:26:48.249241 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:27:12.059075 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:27:42.058483 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:27:48.296730 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:27:48.296781 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:28:12.058571 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:28:42.059119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:28:48.316434 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:28:48.316477 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:29:12.058746 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:29:42.058513 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:29:48.335120 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:29:48.335182 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:30:12.063094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:30:42.058461 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:30:48.358172 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:30:48.358230 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:31:12.058411 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:31:42.058466 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:31:48.399570 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:31:48.399621 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:32:12.058487 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:32:42.058444 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:32:48.419010 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:32:48.419063 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:33:12.058427 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:33:42.058615 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:33:48.438297 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:33:48.438412 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:34:12.058569 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:34:42.058791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:34:48.459280 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:34:48.459337 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:35:12.058745 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:35:42.058750 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:35:48.511413 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:35:48.511486 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:36:12.058437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:36:42.058507 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:36:48.530363 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:36:48.530420 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:37:12.058434 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:37:42.058491 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:37:48.548858 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:37:48.548900 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:38:12.058506 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:38:42.058674 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:38:48.574045 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:38:48.574090 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:39:12.058401 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:39:42.058425 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:39:48.599245 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:39:48.599317 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:40:12.058526 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:40:42.058459 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:40:48.618721 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:40:48.618760 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:41:12.058743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:41:42.058459 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:41:48.643267 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:41:48.644192 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:42:12.058395 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:42:42.059276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:42:48.664525 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:42:48.664581 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:43:12.058507 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:43:42.058523 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:43:48.691283 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:43:48.691332 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:44:12.058788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:44:42.058541 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:44:48.709496 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:44:48.709536 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:45:12.058386 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:45:42.058434 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:45:48.729170 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:45:48.729222 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:46:12.058411 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:46:42.058642 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:46:48.751101 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:46:48.751157 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:47:12.058578 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:47:42.058684 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:47:48.775178 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:47:48.775238 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:48:12.058469 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:48:42.058477 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:48:48.798125 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:48:48.798185 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:49:12.058439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:49:42.058374 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 12:49:48.817886 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:49:48.818073 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 12:50:12.058609 metrics.go:34: INFO No non-zero metrics in the last 30s