By type
2022/02/04 14:06:59.720638 beat.go:285: INFO Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs]
2022/02/04 14:06:59.720670 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/02/04 14:06:59.720721 logstash.go:90: INFO Max Retries set to: 3
2022/02/04 14:06:59.720765 outputs.go:108: INFO Activated logstash as output plugin.
2022/02/04 14:06:59.720849 publish.go:295: INFO Publisher name: onap-portal-sdk-856bc9b5d4-t5vgn
2022/02/04 14:06:59.720974 async.go:63: INFO Flush Interval set to: 1s
2022/02/04 14:06:59.720990 async.go:64: INFO Max Bulk Size set to: 2048
2022/02/04 14:06:59.721216 metrics.go:23: INFO Metrics logging every 30s
2022/02/04 14:06:59.721399 beat.go:221: INFO filebeat start running.
2022/02/04 14:06:59.721488 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/02/04 14:06:59.740566 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/02/04 14:06:59.740775 registrar.go:123: INFO States Loaded from registrar: 0
2022/02/04 14:06:59.740983 crawler.go:38: INFO Loading Prospectors: 1
2022/02/04 14:06:59.741114 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/02/04 14:06:59.741021 registrar.go:236: INFO Starting Registrar
2022/02/04 14:06:59.741027 sync.go:41: INFO Start sending events to output
2022/02/04 14:06:59.741411 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/02/04 14:06:59.741649 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/02/04 14:06:59.741759 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/02/04 14:07:29.721664 metrics.go:39: INFO Non-zero metrics in the last 30s: registrar.writes=1
2022/02/04 14:07:39.744421 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/02/04 14:07:39.744552 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/02/04 14:07:39.744654 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/02/04 14:07:39.744732 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/02/04 14:07:39.744888 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/02/04 14:07:44.755394 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:07:44.755438 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:07:45.760181 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:07:45.760207 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:07:47.764590 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:07:47.764615 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:07:51.773445 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:07:51.773492 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:07:59.721487 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=55
2022/02/04 14:07:59.813830 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:07:59.813866 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:08:15.823812 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:08:15.823857 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:08:29.721509 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:08:47.833578 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:08:47.833623 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:08:59.721534 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:09:29.721477 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:09:47.842472 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:09:47.842512 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:09:59.721527 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:10:29.721626 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:10:47.852411 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:10:47.852452 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:10:59.721522 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:11:29.721621 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:11:47.861436 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:11:47.861493 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:11:59.721452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:12:29.721596 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:12:44.757140 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/02/04 14:12:47.888530 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:12:47.888588 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:12:59.721562 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/02/04 14:12:59.754821 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/02/04 14:12:59.754877 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/02/04 14:12:59.754910 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/02/04 14:13:29.721528 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-3
2022/02/04 14:13:47.898561 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:13:47.898613 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:13:59.721512 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:14:29.721513 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:14:47.908684 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:14:47.908729 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:14:59.721499 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:15:29.721546 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:15:47.917510 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:15:47.917546 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:15:59.721537 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:16:29.721599 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:16:47.927949 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:16:47.927992 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:16:59.721523 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:17:29.721519 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:17:47.940719 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:17:47.940756 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:17:59.721470 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:18:29.721513 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:18:47.951315 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:18:47.951343 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:18:59.722179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:19:29.721534 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:19:47.960943 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:19:47.960986 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:19:59.721570 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:20:29.721511 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:20:47.972513 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:20:47.972807 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:20:59.721453 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:21:29.721689 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:21:47.983313 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:21:47.983354 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:21:59.721532 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:22:29.721586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:22:47.992436 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:22:47.992490 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:22:59.721621 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:23:29.721647 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:23:48.001745 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:23:48.001800 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:23:59.721611 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:24:29.721393 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:24:48.012513 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:24:48.012557 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:24:59.721429 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:25:29.721629 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:25:48.021488 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:25:48.021534 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:25:59.721445 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:26:29.721493 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:26:48.031136 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:26:48.031185 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:26:59.721518 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:27:29.721592 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:27:48.041535 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:27:48.041574 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:27:59.721512 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:28:29.721541 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:28:48.052130 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:28:48.052174 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:28:59.721513 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:29:29.721503 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:29:48.062111 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:29:48.062153 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:29:59.721477 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:30:29.721738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:30:48.072862 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:30:48.072899 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:30:59.721529 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:31:29.721450 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:31:48.086135 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:31:48.086182 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:31:59.721609 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:32:29.721455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:32:48.096058 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:32:48.096128 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:32:59.721492 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:33:29.721441 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:33:48.106802 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:33:48.106829 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:33:59.721507 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:34:29.721470 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:34:48.120542 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:34:48.120589 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:34:59.721549 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:35:29.721460 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:35:48.130086 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:35:48.130129 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:35:59.721457 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:36:29.721455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:36:48.139464 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:36:48.139509 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:36:59.721442 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:37:29.721554 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:37:48.150511 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:37:48.150534 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:37:59.721525 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:38:29.721527 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:38:48.161373 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:38:48.161417 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:38:59.721498 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:39:29.721472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:39:48.170495 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:39:48.170536 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:39:59.721515 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:40:29.721562 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:40:48.181169 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:40:48.181204 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:40:59.721512 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:41:29.721487 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:41:48.193375 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:41:48.193439 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:41:59.721488 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:42:29.721528 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:42:48.203038 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:42:48.203076 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:42:59.721552 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:43:29.721482 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:43:48.213575 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:43:48.213635 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:43:59.721507 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:44:29.721551 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:44:48.224454 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:44:48.224492 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:44:59.721547 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:45:29.721513 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:45:48.236259 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:45:48.236288 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:45:59.721483 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:46:29.721530 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:46:48.245686 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:46:48.245720 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:46:59.721487 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:47:29.721501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:47:48.255467 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:47:48.255504 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:47:59.721491 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:48:29.721600 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:48:48.266951 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:48:48.267017 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:48:59.721518 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:49:29.721499 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:49:48.277360 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:49:48.277402 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:49:59.721499 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:50:29.721571 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:50:48.287748 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:50:48.287785 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:50:59.721498 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:51:29.721596 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:51:48.298264 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:51:48.298315 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:51:59.721513 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:52:29.721530 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:52:48.308581 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:52:48.308640 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:52:59.721504 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:53:29.721448 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:53:48.320032 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:53:48.320068 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:53:59.721462 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:54:29.721464 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:54:48.331077 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:54:48.331124 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:54:59.721566 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:55:29.721521 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:55:48.342533 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:55:48.342591 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:55:59.721558 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:56:29.721514 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:56:48.352584 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:56:48.352621 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:56:59.721535 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:57:29.721483 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:57:48.363321 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:57:48.363392 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:57:59.721528 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:58:29.721527 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:58:48.374004 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:58:48.374053 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:58:59.721664 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:59:29.721535 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 14:59:48.384660 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:59:48.384705 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 14:59:59.721480 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:00:29.721539 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:00:48.395284 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:00:48.395342 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:00:59.721506 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:01:29.721601 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:01:48.404024 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:01:48.404065 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:01:59.721519 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:02:29.721634 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:02:48.414589 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:02:48.414638 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:02:59.721547 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:03:29.721534 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:03:48.424500 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:03:48.424550 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:03:59.721520 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:04:29.721554 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:04:48.435099 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:04:48.435155 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:04:59.721531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:05:29.721504 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:05:48.444458 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:05:48.444482 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:05:59.721431 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:06:29.721488 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:06:48.454370 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:06:48.454417 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:06:59.721525 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:07:29.721519 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:07:48.464047 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:07:48.464098 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:07:59.721488 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:08:29.721523 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:08:48.473959 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:08:48.474013 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:08:59.721479 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:09:29.721497 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:09:48.482819 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:09:48.482857 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:09:59.721392 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:10:29.721533 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:10:48.492731 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:10:48.492778 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:10:59.721650 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:11:29.721513 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:11:48.508448 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:11:48.508486 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:11:59.721549 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:12:29.721515 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:12:48.518635 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:12:48.518673 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:12:59.721501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:13:29.721558 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:13:48.528239 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:13:48.528269 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:13:59.721730 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:14:29.721679 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:14:48.537816 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:14:48.537849 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:14:59.721493 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:15:29.721446 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:15:48.548177 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:15:48.548222 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:15:59.721473 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:16:29.721527 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:16:48.559940 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:16:48.559977 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:16:59.721549 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:17:29.721585 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:17:48.569339 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:17:48.569375 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:17:59.721540 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:18:29.721454 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:18:48.578115 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:18:48.578167 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:18:59.721486 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:19:29.721543 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:19:48.588109 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:19:48.588140 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:19:59.721477 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:20:29.721563 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:20:48.598124 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:20:48.598160 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:20:59.721521 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:21:29.721651 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:21:48.633343 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:21:48.633437 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:21:59.721545 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:22:29.721562 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:22:48.642010 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:22:48.642057 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:22:59.721439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:23:29.721476 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:23:48.652086 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:23:48.652123 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:23:59.721470 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:24:29.721534 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:24:48.661035 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:24:48.661057 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:24:59.721565 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:25:29.721668 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:25:48.670967 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:25:48.671021 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:25:59.721435 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:26:29.721486 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:26:48.680465 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:26:48.680510 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:26:59.721455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:27:29.721499 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:27:48.689524 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:27:48.689599 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:27:59.721506 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:28:29.721503 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:28:48.700702 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:28:48.700765 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:28:59.721495 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:29:29.721543 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:29:48.710037 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:29:48.710079 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:29:59.721543 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:30:29.721507 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:30:48.720460 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:30:48.720506 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:30:59.721541 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:31:29.721468 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:31:48.730861 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:31:48.730905 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:31:59.721460 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:32:29.721489 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:32:48.741961 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:32:48.742003 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:32:59.721585 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:33:29.721492 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:33:48.754554 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:33:48.754595 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:33:59.721520 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:34:29.721525 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:34:48.763358 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:34:48.763410 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:34:59.721525 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:35:29.721533 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:35:48.772614 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:35:48.772671 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:35:59.721539 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:36:29.721540 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:36:48.784403 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:36:48.784470 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:36:59.721431 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:37:29.721512 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:37:48.793845 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:37:48.793871 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:37:59.721658 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:38:29.721487 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:38:48.804025 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:38:48.804087 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:38:59.721500 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:39:29.721522 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:39:48.834375 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:39:48.834425 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:39:59.721503 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:40:29.721516 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:40:48.846581 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:40:48.846634 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:40:59.721469 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:41:29.721508 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:41:48.856763 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:41:48.856802 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:41:59.721483 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:42:29.721537 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:42:48.866124 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:42:48.866165 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:42:59.721494 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:43:29.721575 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:43:48.875538 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:43:48.875582 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:43:59.721506 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:44:29.721483 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:44:48.884226 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:44:48.884274 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:44:59.721562 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:45:29.721496 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:45:48.894490 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:45:48.894535 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:45:59.721529 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:46:29.721579 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:46:48.905448 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:46:48.905492 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:46:59.721424 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:47:29.725339 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:47:48.914754 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:47:48.914799 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:47:59.721414 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:48:29.721473 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:48:48.924153 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:48:48.924196 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:48:59.721576 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:49:29.721477 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:49:48.935449 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:49:48.935510 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:49:59.721638 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:50:29.721543 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:50:48.946153 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:50:48.946190 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:50:59.721491 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:51:29.721495 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:51:48.955184 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:51:48.955228 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:51:59.721455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:52:29.721423 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:52:48.964386 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:52:48.964430 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:52:59.721531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:53:29.721458 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:53:48.974156 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:53:48.974184 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:53:59.721502 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:54:29.721474 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:54:48.983412 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:54:48.983466 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:54:59.721516 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:55:29.721479 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:55:48.992829 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:55:48.992872 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:55:59.721541 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:56:29.721546 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:56:49.000741 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:56:49.000774 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:56:59.721432 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:57:29.721537 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:57:49.008757 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:57:49.008790 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:57:59.721512 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:58:29.721676 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:58:49.022172 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:58:49.022210 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:58:59.721496 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:59:29.721580 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 15:59:49.032107 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:59:49.032150 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 15:59:59.721561 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 16:00:29.721624 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 16:00:49.041803 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 16:00:49.041824 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 16:00:59.721509 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 16:01:29.721554 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 16:01:49.050991 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 16:01:49.051032 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 16:01:59.721583 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 16:02:29.721539 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/04 16:02:49.061935 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 16:02:49.061971 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/04 16:02:59.721533 metrics.go:34: INFO No non-zero metrics in the last 30s