By type
2022/03/09 03:06:18.706069 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/09 03:06:18.706172 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/09 03:06:18.706203 metrics.go:23: INFO Metrics logging every 30s
2022/03/09 03:06:18.706346 logstash.go:90: INFO Max Retries set to: 3
2022/03/09 03:06:18.706505 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/09 03:06:18.706711 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-w7rvv
2022/03/09 03:06:18.707061 async.go:63: INFO Flush Interval set to: 1s
2022/03/09 03:06:18.707178 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/09 03:06:18.707968 beat.go:221: INFO filebeat start running.
2022/03/09 03:06:18.708145 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/09 03:06:18.712935 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/09 03:06:18.713066 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/09 03:06:18.713128 crawler.go:38: INFO Loading Prospectors: 1
2022/03/09 03:06:18.713477 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/09 03:06:18.713659 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/09 03:06:18.713695 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/09 03:06:18.713727 registrar.go:236: INFO Starting Registrar
2022/03/09 03:06:18.713782 sync.go:41: INFO Start sending events to output
2022/03/09 03:06:18.713857 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/09 03:06:38.719682 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/09 03:06:38.719852 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/09 03:06:38.720279 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/09 03:06:38.720382 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/09 03:06:38.720500 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/09 03:06:43.755485 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:06:43.755522 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:06:44.759459 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:06:44.759498 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:06:46.765291 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:06:46.765327 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:06:48.706640 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=70 registrar.writes=1
2022/03/09 03:06:50.773738 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:06:50.773777 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:06:58.781480 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:06:58.781535 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:07:14.804351 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:07:14.804419 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:07:18.706741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:07:46.833818 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:07:46.833891 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:07:48.706684 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:08:18.706747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:08:46.854126 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:08:46.854195 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:08:48.706531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:09:18.706747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:09:46.871265 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:09:46.871317 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:09:48.706695 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:10:18.706734 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:10:46.891300 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:10:46.891372 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:10:48.706715 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:11:18.706616 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:11:43.744815 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/09 03:11:46.925265 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:11:46.925338 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:11:48.706682 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/09 03:12:18.706646 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:12:46.951205 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:12:46.951251 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:12:48.706764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:13:18.706602 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:13:46.971578 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:13:46.971642 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:13:48.706638 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:14:18.706606 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:14:46.995013 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:14:46.995073 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:14:48.706614 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:15:18.706601 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:15:47.014198 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:15:47.014242 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:15:48.706638 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:16:18.706574 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:16:47.049981 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:16:47.050036 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:16:48.706704 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:17:18.706629 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:17:47.069364 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:17:47.069440 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:17:48.706639 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:18:18.706620 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:18:47.087995 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:18:47.088052 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:18:48.706528 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:19:18.706649 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:19:47.110100 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:19:47.110167 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:19:48.706535 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:20:18.713157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:20:47.162313 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:20:47.162362 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:20:48.706574 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:21:18.706719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:21:47.190559 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:21:47.190615 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:21:48.706976 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:22:18.706650 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:22:47.215216 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:22:47.215293 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:22:48.706632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:23:18.706745 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:23:47.235682 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:23:47.236008 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:23:48.706721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:24:18.706681 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:24:47.261576 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:24:47.261655 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:24:48.706690 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:25:18.706595 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:25:47.286304 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:25:47.286369 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:25:48.706709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:26:18.706599 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:26:47.305523 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:26:47.305616 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:26:48.706602 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:27:18.706579 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:27:47.343479 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:27:47.343530 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:27:48.706651 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:28:18.706704 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:28:47.375368 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:28:47.375445 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:28:48.706772 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:29:18.707028 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:29:47.394876 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:29:47.394933 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:29:48.706585 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:30:18.706828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:30:47.415368 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:30:47.415434 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:30:48.706640 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:31:18.706684 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:31:47.439448 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:31:47.439520 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:31:48.706776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:32:18.706635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:32:47.463854 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:32:47.463905 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:32:48.706654 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:33:18.706809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:33:47.492395 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:33:47.492461 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:33:48.706591 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:34:18.706661 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:34:47.512721 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:34:47.512775 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:34:48.706691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:35:18.706588 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:35:47.560689 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:35:47.560753 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:35:48.706632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:36:18.706642 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:36:47.583375 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:36:47.583443 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:36:48.706572 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:37:18.706618 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:37:47.624067 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:37:47.624150 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:37:48.706964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:38:18.706768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:38:47.645518 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:38:47.645573 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:38:48.706586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:39:18.706670 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:39:47.664200 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:39:47.664260 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:39:48.706579 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:40:18.706635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:40:47.683456 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:40:47.683537 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:40:48.706676 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:41:18.706673 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:41:47.703248 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:41:47.703329 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:41:48.706522 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:42:18.706623 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:42:47.725093 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:42:47.725139 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:42:48.706584 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:43:18.706681 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:43:47.753435 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:43:47.753502 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:43:48.706734 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:44:18.706796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:44:47.775798 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:44:47.775872 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:44:48.707081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:45:18.707499 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:45:47.795609 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:45:47.795655 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:45:48.706541 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:46:18.706616 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:46:47.815668 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:46:47.815725 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:46:48.706677 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:47:18.713849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:47:47.842745 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:47:47.842812 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:47:48.706936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:48:18.706521 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:48:47.862350 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:48:47.862411 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:48:48.706607 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:49:18.706626 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:49:47.882903 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:49:47.883006 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:49:48.706669 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:50:18.706592 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:50:47.893638 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:50:47.893695 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:50:48.706760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:51:18.706772 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:51:47.903136 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:51:47.903180 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:51:48.706683 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:52:18.706637 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:52:47.907673 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:52:47.907750 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:52:48.714371 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:53:18.706528 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:53:47.912268 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:53:47.912310 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:53:48.706514 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:54:18.706649 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:54:47.916577 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:54:47.916630 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:54:48.706560 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:55:18.706616 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:55:47.921715 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:55:47.921785 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:55:48.706532 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:56:18.706553 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:56:47.926343 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:56:47.926395 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:56:48.706606 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:57:18.706673 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:57:47.932177 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:57:47.932221 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:57:48.706549 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:58:18.706746 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:58:47.938096 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:58:47.938177 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:58:48.706805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:59:18.706667 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:59:47.945003 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:59:47.945179 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:59:48.706551 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:00:18.706521 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:00:47.949427 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:00:47.949481 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:00:48.706593 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:01:18.706573 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:01:47.956353 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:01:47.956418 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:01:48.706549 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:02:18.706689 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:02:47.962027 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:02:47.962087 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:02:48.707195 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:03:18.706558 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:03:47.966860 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:03:47.966897 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:03:48.706591 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:04:18.706762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:04:47.972037 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:04:47.972092 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:04:48.706540 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:05:18.707028 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:05:47.992538 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:05:47.992595 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:05:48.706780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:06:18.706656 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:06:48.009308 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:06:48.009360 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:06:48.706625 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:07:18.706739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:07:48.028968 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:07:48.029167 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:07:48.706726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:08:18.706644 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:08:48.037493 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:08:48.037536 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:08:48.706763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:09:18.706617 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:09:48.047610 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:09:48.047663 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:09:48.706696 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:10:18.707455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:10:48.054680 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:10:48.054751 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:10:48.706662 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:11:18.706594 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:11:48.060625 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:11:48.060667 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:11:48.706651 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:12:18.706632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:12:48.066935 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:12:48.067080 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:12:48.706624 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:13:18.706550 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:13:48.072727 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:13:48.072773 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:13:48.706787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:14:18.707016 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:14:48.079398 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:14:48.079438 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:14:48.706671 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:15:18.706595 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:15:48.088160 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:15:48.088206 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:15:48.706588 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:16:18.706619 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:16:48.091976 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:16:48.092011 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:16:48.706618 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:17:18.706666 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:17:48.097331 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:17:48.097651 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:17:48.706795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:18:18.706818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:18:48.101786 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:18:48.101835 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:18:48.706597 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:19:18.706517 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:19:48.110738 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:19:48.110796 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:19:48.706673 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:20:18.706576 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:20:48.115650 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:20:48.115700 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:20:48.708759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:21:18.706594 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:21:48.130471 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:21:48.130528 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:21:48.706688 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:22:18.706585 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:22:48.136037 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:22:48.136102 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:22:48.706669 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:23:18.706589 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:23:48.142903 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:23:48.142952 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:23:48.706558 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:24:18.706743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:24:48.150010 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:24:48.150204 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:24:48.706788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:25:18.706752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:25:48.162873 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:25:48.162926 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:25:48.706554 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:26:18.706662 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:26:48.167274 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:26:48.167311 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:26:48.706686 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:27:18.706593 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:27:48.174191 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:27:48.174241 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:27:48.706584 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:28:18.706604 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:28:48.178797 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:28:48.178843 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:28:48.706834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:29:18.706818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:29:48.186447 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:29:48.186489 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:29:48.706834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:30:18.713269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:30:48.191219 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:30:48.191280 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:30:48.706598 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:31:18.706654 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:31:48.197949 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:31:48.198068 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:31:48.706663 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:32:18.706583 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:32:48.202879 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:32:48.203039 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:32:48.706892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:33:18.706793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:33:48.235666 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:33:48.235715 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:33:48.706584 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:34:18.706765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:34:48.245595 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:34:48.245673 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:34:48.706687 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:35:18.706551 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:35:48.252765 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:35:48.255795 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:35:48.706813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:36:18.706653 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:36:48.259342 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:36:48.259389 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:36:48.706611 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:37:18.706505 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:37:48.267145 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:37:48.267210 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:37:48.706647 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:38:18.706600 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:38:48.271137 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:38:48.271180 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:38:48.706757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:39:18.706638 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:39:48.277987 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:39:48.278044 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:39:48.707141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:40:18.706858 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:40:48.282656 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:40:48.282724 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:40:48.707822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:41:18.709904 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:41:48.308114 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:41:48.308178 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:41:48.706605 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:42:18.706747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:42:48.318971 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:42:48.319014 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:42:48.706715 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:43:18.706588 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:43:48.336515 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:43:48.336568 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:43:48.707036 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:44:18.706505 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:44:48.342200 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:44:48.342242 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 04:44:48.706685 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 04:45:18.706650 metrics.go:34: INFO No non-zero metrics in the last 30s