By type
2022/03/24 02:59:38.011867 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/24 02:59:38.011919 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/24 02:59:38.012025 logstash.go:90: INFO Max Retries set to: 3
2022/03/24 02:59:38.012092 metrics.go:23: INFO Metrics logging every 30s
2022/03/24 02:59:38.012134 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/24 02:59:38.012250 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-vxfcz
2022/03/24 02:59:38.012457 async.go:63: INFO Flush Interval set to: 1s
2022/03/24 02:59:38.012479 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/24 02:59:38.012934 beat.go:221: INFO filebeat start running.
2022/03/24 02:59:38.013016 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/24 02:59:38.016540 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/24 02:59:38.016601 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/24 02:59:38.016635 crawler.go:38: INFO Loading Prospectors: 1
2022/03/24 02:59:38.016809 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/24 02:59:38.016831 registrar.go:236: INFO Starting Registrar
2022/03/24 02:59:38.016898 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/24 02:59:38.016916 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/24 02:59:38.016858 sync.go:41: INFO Start sending events to output
2022/03/24 02:59:38.016969 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/24 02:59:58.019839 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/24 02:59:58.020165 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/24 02:59:58.020260 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/24 02:59:58.020404 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/24 02:59:58.020534 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/24 02:59:58.051318 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:59:58.051359 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:59:59.055477 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 02:59:59.055521 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:00:01.064964 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:00:01.064999 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:00:05.075984 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:00:05.076031 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:00:08.015583 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=5 filebeat.harvester.running=5 filebeat.harvester.started=5 libbeat.publisher.published_events=76 registrar.writes=1
2022/03/24 03:00:13.085732 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:00:13.085801 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:00:29.104440 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:00:29.104487 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:00:38.012384 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:01:01.127470 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:01:01.127536 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:01:08.012335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:01:38.013368 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:02:01.147535 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:02:01.147606 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:02:08.012433 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:02:38.012378 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:03:01.165469 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:03:01.165542 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:03:08.012434 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:03:38.012429 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:04:01.185125 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:04:01.185178 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:04:08.012394 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:04:38.012500 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:05:01.203771 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:05:01.203816 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:05:03.038376 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/24 03:05:08.012414 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/24 03:05:38.012459 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:06:01.222603 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:06:01.222982 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:06:08.012387 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:06:38.012526 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:07:01.241221 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:07:01.241358 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:07:08.012343 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:07:38.012587 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:08:01.260949 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:08:01.260986 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:08:08.012320 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:08:38.012755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:09:01.279026 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:09:01.279084 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:09:08.012439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:09:38.012614 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:10:01.296927 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:10:01.296975 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:10:08.012493 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:10:38.012442 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:11:01.315469 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:11:01.315510 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:11:08.012544 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:11:38.012353 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:12:01.333685 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:12:01.333734 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:12:08.012388 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:12:38.012361 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:13:01.351781 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:13:01.351822 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:13:08.012450 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:13:38.012485 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:14:01.373156 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:14:01.373200 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:14:08.012375 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:14:38.012384 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:15:01.392477 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:15:01.392529 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:15:08.012336 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:15:38.012404 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:16:01.410326 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:16:01.410370 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:16:08.012395 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:16:38.012507 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:17:01.428246 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:17:01.428302 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:17:08.012418 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:17:38.012495 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:18:01.445610 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:18:01.445648 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:18:08.012391 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:18:38.012552 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:19:01.464605 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:19:01.464655 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:19:08.012383 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:19:38.012516 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:20:01.486950 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:20:01.486991 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:20:08.012490 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:20:38.012379 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:21:01.504575 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:21:01.504628 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:21:08.012397 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:21:38.012424 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:22:01.523598 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:22:01.523659 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:22:08.012436 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:22:38.012408 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:23:01.541005 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:23:01.541047 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:23:08.012401 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:23:38.012495 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:24:01.561424 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:24:01.561469 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:24:08.012510 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:24:38.012440 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:25:01.578498 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:25:01.578536 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:25:08.012425 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:25:38.012348 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:26:01.597233 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:26:01.597279 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:26:08.012354 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:26:38.012489 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:27:01.615538 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:27:01.615588 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:27:08.012456 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:27:38.012412 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:28:01.633257 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:28:01.633305 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:28:08.012397 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:28:38.012354 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:29:01.653623 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:29:01.653660 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:29:08.012352 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:29:38.012395 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:30:01.680927 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:30:01.680972 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:30:08.012434 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:30:38.012410 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:31:01.699752 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:31:01.699803 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:31:08.012497 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:31:38.012570 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:32:01.720489 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:32:01.720549 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:32:08.012367 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:32:38.012371 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:33:01.738768 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:33:01.738800 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:33:08.012384 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:33:38.012565 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:34:01.757129 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:34:01.757169 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:34:08.012438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:34:38.012434 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:35:01.774017 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:35:01.774164 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:35:08.012407 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:35:38.012453 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:36:01.792869 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:36:01.792908 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:36:08.012420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:36:38.012445 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:37:01.811364 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:37:01.811464 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:37:08.012710 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:37:38.012419 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:38:01.829692 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:38:01.829727 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:38:08.012403 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:38:38.012346 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:39:01.849865 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:39:01.849899 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:39:08.012445 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:39:38.012920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:40:01.875796 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:01.875835 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:40:08.013369 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:40:38.012378 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:41:01.882456 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:41:01.882508 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:41:08.012453 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:41:38.012429 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:42:01.900644 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:42:01.900678 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:42:08.012430 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:42:38.012438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:43:01.918477 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:43:01.918518 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:43:08.012492 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:43:38.012452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:44:01.937850 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:44:01.937887 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:44:08.012364 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:44:38.012399 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:45:01.955981 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:45:01.956017 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:45:08.014845 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:45:38.012795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:46:01.973821 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:46:01.973892 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:46:08.012446 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:46:38.012379 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:47:01.993581 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:47:01.993625 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:47:08.012382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:47:38.012390 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:48:02.011522 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:48:02.011566 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:48:08.012476 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:48:38.012486 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:49:02.032662 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:49:02.032695 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:49:08.012392 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:49:38.012312 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:50:02.048674 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:50:02.048706 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:50:08.012405 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:50:38.012438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:51:02.071582 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:51:02.071627 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:51:08.012383 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:51:38.012421 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:52:02.097967 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:52:02.098063 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:52:08.012435 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:52:38.012377 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:53:02.117570 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:53:02.117615 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:53:08.012511 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:53:38.012452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:54:02.139911 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:54:02.139957 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:54:08.012432 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:54:38.012401 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:55:02.158159 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:55:02.158203 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:55:08.012387 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:55:38.012819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:56:02.176196 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:56:02.176271 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:56:08.012516 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:56:38.012491 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:57:02.195796 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:57:02.195835 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:57:08.012459 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:57:38.012526 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:58:02.217948 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:58:02.217991 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:58:08.012402 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:58:38.012511 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:59:02.235925 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:59:02.235969 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:59:08.012418 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:59:38.012418 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:00:02.258331 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:00:02.258375 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:00:08.012513 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:00:38.012469 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:01:02.278493 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:01:02.278578 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:01:08.012688 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:01:38.012467 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:02:02.300111 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:02:02.300148 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:02:08.012513 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:02:38.012529 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:03:02.318191 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:03:02.318548 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:03:08.012435 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:03:38.012369 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:04:02.335589 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:04:02.335642 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:04:08.012378 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:04:38.012278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:05:02.352569 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:05:02.352604 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:05:08.012456 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:05:38.012429 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:06:02.371323 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:06:02.371366 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:06:08.012402 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:06:38.012395 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:07:02.388562 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:07:02.388597 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:07:08.012404 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:07:38.017705 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:08:02.407523 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:08:02.407633 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:08:08.012666 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:08:38.012407 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:09:02.425056 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:09:02.425097 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:09:08.012375 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:09:38.012411 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:10:02.442823 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:10:02.442877 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:10:08.012437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:10:38.012350 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:11:02.461371 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:11:02.461406 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:11:08.012365 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:11:38.012374 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:12:02.480072 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:12:02.480116 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:12:08.012483 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:12:38.012371 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:13:02.499229 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:13:02.499266 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:13:08.012420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:13:38.012364 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:14:02.523935 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:14:02.524107 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:14:08.012403 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:14:38.012401 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:15:02.541868 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:15:02.541948 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:15:08.012383 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:15:38.012582 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:16:02.558533 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:16:02.558578 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:16:08.012554 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:16:38.012416 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:17:02.586510 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:17:02.586572 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:17:08.012408 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:17:38.012484 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:18:02.610504 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:18:02.610557 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:18:08.012396 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:18:38.012727 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:19:02.627514 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:19:02.627552 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:19:08.012448 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:19:38.012444 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:20:02.645935 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:20:02.646121 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:20:08.012407 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:20:38.012334 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:21:02.665018 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:21:02.665066 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:21:08.012412 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:21:38.012472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:22:02.681491 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:22:02.681531 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:22:08.012375 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:22:38.012594 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:23:02.699092 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:23:02.699134 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:23:08.012495 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:23:38.012436 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:24:02.718752 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:24:02.718801 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:24:08.016195 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:24:38.012451 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:25:02.734651 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:25:02.734703 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:25:08.012490 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:25:38.012428 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:26:02.756861 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:26:02.756902 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:26:08.012510 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:26:38.012432 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:27:02.775157 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:27:02.775195 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:27:08.012389 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:27:38.012419 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:28:02.796188 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:28:02.796237 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:28:08.012455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:28:38.012375 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:29:02.813506 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:29:02.813543 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:29:08.012332 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:29:38.012577 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:30:02.832375 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:30:02.832421 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:30:08.012445 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:30:38.012802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:31:02.854188 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:31:02.854226 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:31:08.012416 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:31:38.012440 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:32:02.879983 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:32:02.880024 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:32:08.012501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:32:38.012487 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:33:02.898194 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:33:02.898251 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:33:08.012403 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:33:38.013294 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:34:02.918287 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:34:02.918325 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:34:08.012414 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:34:38.012452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 04:35:02.938351 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:35:02.938392 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 04:35:08.012473 metrics.go:34: INFO No non-zero metrics in the last 30s