By type
2022/03/23 03:01:04.145729 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/23 03:01:04.145778 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/23 03:01:04.146067 metrics.go:23: INFO Metrics logging every 30s
2022/03/23 03:01:04.146727 logstash.go:90: INFO Max Retries set to: 3
2022/03/23 03:01:04.146807 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/23 03:01:04.147072 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-qqnmq
2022/03/23 03:01:04.147476 async.go:63: INFO Flush Interval set to: 1s
2022/03/23 03:01:04.147505 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/23 03:01:04.148147 beat.go:221: INFO filebeat start running.
2022/03/23 03:01:04.148232 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/23 03:01:04.154537 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/23 03:01:04.154650 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/23 03:01:04.154766 crawler.go:38: INFO Loading Prospectors: 1
2022/03/23 03:01:04.154835 registrar.go:236: INFO Starting Registrar
2022/03/23 03:01:04.154880 sync.go:41: INFO Start sending events to output
2022/03/23 03:01:04.155000 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/23 03:01:04.155054 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/23 03:01:04.155226 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/23 03:01:04.155268 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/23 03:01:24.158514 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/23 03:01:24.158650 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/23 03:01:24.158911 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/23 03:01:24.159026 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/23 03:01:24.159093 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/23 03:01:29.179713 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:01:29.180546 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:01:30.187072 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:01:30.187120 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:01:32.191911 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:01:32.192049 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:01:34.146513 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/23 03:01:36.201259 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:01:36.201318 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:01:44.211668 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:01:44.211726 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:02:00.239252 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:02:00.239302 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:02:04.146506 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:02:32.260386 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:02:32.260429 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:02:34.146420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:03:04.146403 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:03:32.281914 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:03:32.281985 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:03:34.146434 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:04:04.148224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:04:32.305670 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:04:32.305733 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:04:34.146476 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:05:04.146423 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:05:32.327095 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:05:32.327165 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:05:34.146400 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:06:04.146365 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:06:29.169620 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/23 03:06:32.346998 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:06:32.347045 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:06:34.146589 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/23 03:07:04.146376 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:07:32.365631 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:07:32.365690 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:07:34.146438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:08:04.146467 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:08:32.385094 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:08:32.385132 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:08:34.146361 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:09:04.146355 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:09:32.402194 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:09:32.402245 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:09:34.146324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:10:04.146493 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:10:32.419613 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:10:32.419651 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:10:34.146536 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:11:04.146388 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:11:32.436914 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:11:32.436962 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:11:34.146377 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:12:04.146424 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:12:32.455629 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:12:32.455772 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:12:34.146455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:13:04.147370 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:13:32.478132 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:13:32.478197 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:13:34.146346 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:14:04.146497 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:14:32.498899 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:14:32.499007 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:14:34.146548 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:15:04.146458 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:15:32.528638 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:15:32.528690 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:15:34.147043 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:16:04.147569 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:16:32.547541 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:16:32.547591 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:16:34.146376 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:17:04.146352 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:17:32.566077 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:17:32.566146 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:17:34.146378 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:18:04.146473 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:18:32.585714 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:18:32.585754 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:18:34.146353 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:19:04.146384 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:19:32.603740 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:19:32.603793 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:19:34.146431 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:20:04.146340 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:20:32.621754 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:20:32.621800 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:20:34.146438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:21:04.146409 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:21:32.649673 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:21:32.649708 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:21:34.146367 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:22:04.146408 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:22:32.666890 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:22:32.667048 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:22:34.146847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:23:04.146476 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:23:32.687365 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:23:32.687426 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:23:34.146394 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:24:04.146389 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:24:32.706118 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:24:32.706160 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:24:34.146477 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:25:04.146386 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:25:32.726236 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:25:32.726275 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:25:34.146353 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:26:04.146382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:26:32.745852 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:26:32.745902 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:26:34.146391 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:27:04.146410 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:27:32.764113 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:27:32.764155 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:27:34.146411 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:28:04.146369 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:28:32.783043 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:28:32.783090 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:28:34.146436 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:29:04.146345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:29:32.800511 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:29:32.800549 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:29:34.146332 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:30:04.146473 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:30:32.819969 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:30:32.820026 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:30:34.146434 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:31:04.146447 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:31:32.838755 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:31:32.838797 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:31:34.146398 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:32:04.146384 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:32:32.857331 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:32:32.857786 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:32:34.146351 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:33:04.146382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:33:32.878583 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:33:32.878615 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:33:34.146389 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:34:04.146425 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:34:32.898522 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:34:32.898557 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:34:34.146437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:35:04.146335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:35:32.916175 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:35:32.916296 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:35:34.146331 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:36:04.146450 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:36:32.934801 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:36:32.934841 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:36:34.146463 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:37:04.146416 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:37:32.954143 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:37:32.954179 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:37:34.146422 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:38:04.146353 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:38:32.972531 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:38:32.972622 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:38:34.146402 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:39:04.146409 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:39:32.991635 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:39:32.991688 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:39:34.147178 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:40:04.146378 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:40:33.012940 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:40:33.013004 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:40:34.146443 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:41:04.146401 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:41:33.032832 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:41:33.032893 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:41:34.146379 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:42:04.146989 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:42:33.036255 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:42:33.036289 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:42:34.146390 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:43:04.146624 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:43:33.043905 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:43:33.043936 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:43:34.146442 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:44:04.146341 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:44:33.054176 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:44:33.054225 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:44:34.146513 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:45:04.146345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:45:33.071778 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:45:33.072106 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:45:34.146575 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:46:04.146453 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:46:33.079385 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:46:33.079415 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:46:34.146382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:47:04.146478 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:47:33.086233 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:47:33.086282 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:47:34.146410 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:48:04.146452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:48:33.092541 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:48:33.092583 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:48:34.146381 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:49:04.146412 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:49:33.099393 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:49:33.099443 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:49:34.146426 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:50:04.146505 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:50:33.106871 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:50:33.106925 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:50:34.146484 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:51:04.146509 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:51:33.113708 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:51:33.113753 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:51:34.146325 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:52:04.146639 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:52:33.120736 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:52:33.120767 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:52:34.146348 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:53:04.146385 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:53:33.126816 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:53:33.127570 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:53:34.146338 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:54:04.146421 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:54:33.135084 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:54:33.135126 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:54:34.146317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:55:04.146399 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:55:33.140901 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:55:33.140938 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:55:34.146395 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:56:04.146440 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:56:33.147930 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:56:33.147960 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:56:34.146339 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:57:04.146642 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:57:33.155050 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:57:33.155095 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:57:34.146648 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:58:04.149227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:58:33.161926 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:58:33.162106 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:58:34.148309 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:59:04.146359 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:59:33.168594 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:59:33.168626 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:59:34.146398 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:00:04.146351 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:00:33.176516 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:00:33.176567 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:00:34.148227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:01:04.146417 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:01:33.183504 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:01:33.183542 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:01:34.146354 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:02:04.146409 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:02:33.191657 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:02:33.191689 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:02:34.146468 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:03:04.146512 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:03:33.198687 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:03:33.198762 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:03:34.146389 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:04:04.146449 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:04:33.205430 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:04:33.205478 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:04:34.146395 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:05:04.146343 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:05:33.212749 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:05:33.212797 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:05:34.146340 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:06:04.146393 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:06:33.221263 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:06:33.221302 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:06:34.146339 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:07:04.146410 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:07:33.228577 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:07:33.228829 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:07:34.146345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:08:04.146380 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:08:33.236225 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:08:33.236287 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:08:34.146396 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:09:04.146695 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:09:33.243843 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:09:33.243921 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:09:34.146478 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:10:04.146391 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:10:33.251461 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:10:33.251517 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:10:34.146475 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:11:04.146390 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:11:33.258151 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:11:33.258204 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:11:34.146399 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:12:04.146394 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:12:33.275020 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:12:33.275069 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:12:34.146469 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:13:04.146368 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:13:33.282031 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:13:33.282072 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:13:34.146537 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:14:04.146345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:14:33.290136 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:14:33.290604 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:14:34.146349 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:15:04.146551 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:15:33.297708 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:15:33.297746 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:15:34.146582 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:16:04.146393 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:16:33.306497 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:16:33.306821 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:16:34.146386 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:17:04.146360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:17:33.313715 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:17:33.313750 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:17:34.146318 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:18:04.146441 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:18:33.320831 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:18:33.320868 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:18:34.146418 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:19:04.146356 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:19:33.328196 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:19:33.328240 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:19:34.146472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:20:04.146503 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:20:33.335775 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:20:33.335814 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:20:34.146347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:21:04.146386 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:21:33.341863 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:21:33.341895 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:21:34.146343 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:22:04.146499 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:22:33.350930 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:22:33.350969 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:22:34.146448 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:23:04.146584 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:23:33.358280 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:23:33.358404 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:23:34.146691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:24:04.146965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:24:33.365769 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:24:33.365805 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:24:34.146392 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:25:04.146342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:25:33.372234 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:25:33.372290 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:25:34.146351 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:26:04.146399 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:26:33.379906 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:26:33.379952 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:26:34.146487 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:27:04.146329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:27:33.385863 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:27:33.385905 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:27:34.146379 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:28:04.146358 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:28:33.392963 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:28:33.392995 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:28:34.146380 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:29:04.146421 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:29:33.399619 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:29:33.399674 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:29:34.146444 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:30:04.146363 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:30:33.407899 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:30:33.407933 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:30:34.146381 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:31:04.146361 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:31:33.416022 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:31:33.416061 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:31:34.146382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:32:04.146384 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:32:33.422561 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:32:33.422593 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:32:34.146353 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:33:04.146393 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:33:33.428944 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:33:33.428976 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:33:34.146420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:34:04.146387 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:34:33.438131 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:34:33.438167 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:34:34.146324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:35:04.146351 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:35:33.446323 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:35:33.446367 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:35:34.146447 metrics.go:34: INFO No non-zero metrics in the last 30s