By type
2022/03/27 03:04:54.362666 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/27 03:04:54.362715 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/27 03:04:54.362930 logstash.go:90: INFO Max Retries set to: 3
2022/03/27 03:04:54.363107 metrics.go:23: INFO Metrics logging every 30s
2022/03/27 03:04:54.363307 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/27 03:04:54.363553 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-6tdmt
2022/03/27 03:04:54.363926 async.go:63: INFO Flush Interval set to: 1s
2022/03/27 03:04:54.363973 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/27 03:04:54.364805 beat.go:221: INFO filebeat start running.
2022/03/27 03:04:54.365089 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/27 03:04:54.370724 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/27 03:04:54.370808 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/27 03:04:54.370851 crawler.go:38: INFO Loading Prospectors: 1
2022/03/27 03:04:54.370915 registrar.go:236: INFO Starting Registrar
2022/03/27 03:04:54.371026 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/27 03:04:54.371069 sync.go:41: INFO Start sending events to output
2022/03/27 03:04:54.371177 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/27 03:04:54.371336 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/27 03:04:54.371371 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/27 03:05:14.380430 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/27 03:05:14.380786 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/27 03:05:14.381103 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/27 03:05:14.381418 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/27 03:05:14.381727 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/27 03:05:19.401958 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:05:19.402021 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:05:20.412006 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:05:20.412089 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:05:22.418044 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:05:22.418085 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:05:24.364520 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=72 registrar.writes=1
2022/03/27 03:05:26.433139 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:05:26.433230 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:05:34.452366 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:05:34.452490 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:05:50.478181 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:05:50.478276 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:05:54.363799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:06:22.507478 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:06:22.507566 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:06:24.363616 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:06:54.363608 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:07:22.532586 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:07:22.532631 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:07:24.363668 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:07:54.363570 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:08:22.554972 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:08:22.555025 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:08:24.363949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:08:54.368427 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:09:22.575467 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:09:22.575535 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:09:24.363696 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:09:54.363516 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:10:19.400976 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/27 03:10:22.597166 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:10:22.597212 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:10:24.363753 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/27 03:10:54.363465 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:11:22.622307 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:11:22.622367 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:11:24.363584 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:11:54.363577 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:12:22.641076 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:12:22.641129 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:12:24.363590 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:12:54.364609 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:13:22.658551 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:13:22.658630 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:13:24.363654 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:13:54.363675 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:14:22.682726 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:14:22.682836 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:14:24.363568 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:14:54.363548 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:15:22.706346 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:15:22.706408 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:15:24.363817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:15:54.363601 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:16:22.725962 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:16:22.726006 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:16:24.363559 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:16:54.363601 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:17:22.745209 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:17:22.745251 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:17:24.363621 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:17:54.363532 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:18:22.764995 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:18:22.765057 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:18:24.363645 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:18:54.363596 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:19:22.784639 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:19:22.784888 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:19:24.363614 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:19:54.363754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:20:22.803349 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:20:22.803402 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:20:24.363624 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:20:54.363530 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:21:22.839900 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:21:22.839946 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:21:24.363543 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:21:54.363611 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:22:22.859694 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:22:22.859751 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:22:24.365857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:22:54.363518 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:23:22.879050 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:23:22.879096 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:23:24.363597 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:23:54.364328 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:24:22.897803 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:24:22.897846 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:24:24.363545 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:24:54.363822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:25:22.916778 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:25:22.916840 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:25:24.363604 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:25:54.363705 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:26:22.935652 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:26:22.935704 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:26:24.363673 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:26:54.363574 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:27:22.954654 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:27:22.954701 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:27:24.363624 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:27:54.363531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:28:22.974489 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:28:22.974585 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:28:24.363612 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:28:54.363617 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:29:22.993494 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:29:22.993556 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:29:24.363762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:29:54.363662 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:30:23.012514 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:30:23.012597 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:30:24.363615 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:30:54.363591 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:31:23.037100 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:31:23.037268 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:31:24.363688 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:31:54.363874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:32:23.058668 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:32:23.058713 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:32:24.363579 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:32:54.363596 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:33:23.076677 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:33:23.076740 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:33:24.363694 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:33:54.363714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:34:23.111771 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:34:23.111837 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:34:24.363601 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:34:54.363637 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:35:23.132072 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:35:23.132130 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:35:24.363684 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:35:54.363673 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:36:23.156891 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:36:23.156950 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:36:24.363609 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:36:54.363582 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:37:23.176172 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:37:23.176243 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:37:24.363609 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:37:54.363610 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:38:23.196794 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:38:23.197047 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:38:24.363640 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:38:54.363586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:39:23.216469 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:39:23.218953 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:39:24.363726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:39:54.363675 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:40:23.238672 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:40:23.238719 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:40:24.363549 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:40:54.363574 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:41:23.259079 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:41:23.259147 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:41:24.363547 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:41:54.363572 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:42:23.277055 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:42:23.277109 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:42:24.363577 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:42:54.363612 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:43:23.294930 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:43:23.294989 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:43:24.363646 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:43:54.363603 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:44:23.316291 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:44:23.316613 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:44:24.363667 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:44:54.363719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:45:23.339957 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:45:23.340004 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:45:24.363642 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:45:54.363542 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:46:23.360513 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:46:23.360554 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:46:24.363901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:46:54.363622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:47:23.399552 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:47:23.399644 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:47:24.363716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:47:54.363689 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:48:23.427972 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:48:23.428031 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:48:24.363721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:48:54.363580 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:49:23.446512 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:49:23.446564 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:49:24.363687 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:49:54.363602 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:50:23.475091 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:50:23.475236 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:50:24.363652 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:50:54.363678 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:51:23.497322 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:51:23.497368 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:51:24.363679 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:51:54.363692 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:52:23.521456 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:52:23.521532 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:52:24.363636 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:52:54.363585 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:53:23.543254 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:53:23.543302 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:53:24.363786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:53:54.363658 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:54:23.567978 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:54:23.568035 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:54:24.363597 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:54:54.363603 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:55:23.589487 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:55:23.589557 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:55:24.363627 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:55:54.363583 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:56:23.615069 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:56:23.615121 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:56:24.363703 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:56:54.363575 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:57:23.634176 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:57:23.634228 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:57:24.363723 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:57:54.363645 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:58:23.655078 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:58:23.655143 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:58:24.363739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:58:54.363614 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:59:23.676630 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:59:23.676730 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 03:59:24.363606 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 03:59:54.363643 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:00:23.699077 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:00:23.699137 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:00:24.363605 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:00:54.363562 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:01:23.718663 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:01:23.718717 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:01:24.363901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:01:54.363610 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:02:23.737817 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:02:23.737856 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:02:24.363603 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:02:54.363650 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:03:23.755810 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:03:23.755873 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:03:24.363617 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:03:54.363651 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:04:23.773826 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:04:23.773871 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:04:24.363555 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:04:54.363741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:05:23.792054 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:05:23.792234 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:05:24.363617 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:05:54.363633 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:06:23.825396 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:06:23.825437 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:06:24.363653 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:06:54.363631 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:07:23.844113 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:07:23.844178 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:07:24.363604 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:07:54.363550 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:08:23.868677 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:08:23.868727 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:08:24.363563 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:08:54.363631 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:09:23.887262 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:09:23.887321 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:09:24.363689 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:09:54.363605 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:10:23.906165 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:10:23.906218 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:10:24.363620 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:10:54.363664 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:11:23.931244 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:11:23.931364 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:11:24.363672 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:11:54.363636 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:12:23.947609 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:12:23.947668 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:12:24.363676 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:12:54.363551 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:13:23.968167 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:13:23.968252 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:13:24.363604 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:13:54.363536 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:14:23.995055 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:14:23.995100 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:14:24.363597 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:14:54.363613 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:15:24.016968 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:15:24.017022 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:15:24.363645 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:15:54.363579 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:16:24.037045 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:16:24.037088 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:16:24.363642 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:16:54.363640 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:17:24.058111 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:17:24.058268 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:17:24.363625 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:17:54.363677 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:18:24.077259 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:18:24.077330 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:18:24.363655 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:18:54.364525 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:19:24.098173 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:19:24.098222 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:19:24.363642 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:19:54.363607 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:20:24.121471 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:20:24.121530 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:20:24.363704 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:20:54.363724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:21:24.145577 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:21:24.145712 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:21:24.363547 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:21:54.363648 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:22:24.168118 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:22:24.168174 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:22:24.363712 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:22:54.363605 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:23:24.187803 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:23:24.187906 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:23:24.363529 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:23:54.363542 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:24:24.206710 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:24:24.206772 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:24:24.363695 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:24:54.363637 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:25:24.236926 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:25:24.236971 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:25:24.363614 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:25:54.363606 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:26:24.257520 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:26:24.257592 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:26:24.363613 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:26:54.363837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:27:24.278832 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:27:24.278894 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:27:24.363651 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:27:54.363615 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:28:24.301587 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:28:24.301690 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:28:24.363593 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:28:54.363863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:29:24.320517 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:29:24.320741 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:29:24.363582 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:29:54.363599 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:30:24.340882 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:30:24.340931 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:30:24.363594 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:30:54.363652 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:31:24.358979 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:31:24.359043 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:31:24.363627 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:31:54.363576 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:32:24.363627 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:32:24.378296 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:32:24.378324 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:32:54.363587 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:33:24.363628 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:33:24.396642 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:33:24.396682 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:33:54.363636 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:34:24.364018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:34:24.414983 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:34:24.415059 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:34:54.363767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:35:24.363670 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:35:24.443241 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:35:24.443450 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:35:54.363647 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:36:24.363634 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:36:24.467120 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:36:24.467163 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:36:54.363663 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:37:24.363785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:37:24.483862 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:37:24.483911 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:37:54.363589 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:38:24.363546 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:38:24.503581 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:38:24.503643 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:38:54.363586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:39:24.363615 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:39:24.526563 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:39:24.526620 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:39:54.363570 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:40:24.363600 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:40:24.560924 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:40:24.560983 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:40:54.363646 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:41:24.363611 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/27 04:41:24.581936 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:41:24.581986 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/27 04:41:54.363601 metrics.go:34: INFO No non-zero metrics in the last 30s