By type
2022/03/14 03:03:29.742620 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/14 03:03:29.742707 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/14 03:03:29.742877 logstash.go:90: INFO Max Retries set to: 3
2022/03/14 03:03:29.743038 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/14 03:03:29.743193 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-44s5p
2022/03/14 03:03:29.743493 async.go:63: INFO Flush Interval set to: 1s
2022/03/14 03:03:29.743514 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/14 03:03:29.746266 beat.go:221: INFO filebeat start running.
2022/03/14 03:03:29.746415 metrics.go:23: INFO Metrics logging every 30s
2022/03/14 03:03:29.746519 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/14 03:03:29.753372 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/14 03:03:29.753738 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/14 03:03:29.754223 crawler.go:38: INFO Loading Prospectors: 1
2022/03/14 03:03:29.754549 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/14 03:03:29.754726 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/14 03:03:29.754758 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/14 03:03:29.754793 registrar.go:236: INFO Starting Registrar
2022/03/14 03:03:29.754847 sync.go:41: INFO Start sending events to output
2022/03/14 03:03:29.754975 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/14 03:03:49.759183 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/14 03:03:49.759699 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/14 03:03:49.759768 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/14 03:03:49.759857 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/14 03:03:49.759829 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/14 03:03:54.779183 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:03:54.779332 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:03:55.783624 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:03:55.783801 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:03:57.790937 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:03:57.791088 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:03:59.746863 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=64 publish.events=5 registrar.states.current=5 registrar.states.update=5 registrar.writes=2
2022/03/14 03:04:01.800286 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:04:01.800440 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:04:09.807967 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:04:09.808009 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:04:25.839274 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:04:25.839348 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:04:29.746899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:04:57.859377 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:04:57.859438 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:04:59.747212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:05:29.747364 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:05:57.880811 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:05:57.880856 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:05:59.746810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:06:29.746795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:06:57.904311 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:06:57.904379 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:06:59.746773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:07:29.746731 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:07:57.932078 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:07:57.932135 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:07:59.746800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:08:29.746755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:08:54.771767 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/14 03:08:54.771837 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/14 03:08:54.771778 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/14 03:08:54.771801 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/14 03:08:57.953605 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:08:57.953648 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:08:59.746848 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=4 filebeat.harvester.open_files=-4 filebeat.harvester.running=-4
2022/03/14 03:09:04.775603 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/03/14 03:09:29.747004 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=1 filebeat.harvester.open_files=-1 filebeat.harvester.running=-1
2022/03/14 03:09:57.974966 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:09:57.975159 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:09:59.747139 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:10:29.746763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:10:57.997347 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:10:57.997409 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:10:59.746789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:11:29.746746 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:11:58.017646 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:11:58.017720 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:11:59.746883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:12:29.746740 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:12:58.038943 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:12:58.038987 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:12:59.746872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:13:29.746920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:13:58.061109 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:13:58.061177 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:13:59.746791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:14:29.746777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:14:58.083159 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:14:58.083230 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:14:59.746742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:15:29.746700 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:15:58.104413 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:15:58.104472 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:15:59.746714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:16:29.746650 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:16:58.125092 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:16:58.125308 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:16:59.746714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:17:29.746903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:17:58.145001 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:17:58.145052 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:17:59.746833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:18:29.746833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:18:58.165216 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:18:58.165256 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:18:59.746947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:19:29.746771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:19:58.186776 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:19:58.186859 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:19:59.746749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:20:29.746803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:20:58.207169 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:20:58.207223 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:20:59.746825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:21:29.746745 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:21:58.225762 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:21:58.225799 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:21:59.747975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:22:29.746884 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:22:58.249148 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:22:58.249219 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:22:59.746789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:23:29.747068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:23:58.269493 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:23:58.269543 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:23:59.746791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:24:29.746823 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:24:58.289599 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:24:58.289656 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:24:59.746743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:25:29.746791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:25:58.310412 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:25:58.310453 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:25:59.746802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:26:29.746960 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:26:58.330305 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:26:58.330347 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:26:59.746812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:27:29.746905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:27:58.350784 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:27:58.350833 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:27:59.746728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:28:29.746714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:28:58.376003 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:28:58.376050 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:28:59.746745 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:29:29.746831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:29:58.394191 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:29:58.394252 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:29:59.746831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:30:29.746701 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:30:58.414036 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:30:58.414084 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:30:59.746758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:31:29.746745 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:31:58.434080 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:31:58.434190 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:31:59.746944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:32:29.746752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:32:58.455107 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:32:58.455169 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:32:59.746903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:33:29.746898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:33:58.476768 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:33:58.476879 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:33:59.746939 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:34:29.746754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:34:58.527554 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:34:58.527711 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:34:59.746763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:35:29.746805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:35:58.547416 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:35:58.547455 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:35:59.746806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:36:29.746730 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:36:58.567842 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:36:58.567884 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:36:59.746774 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:37:29.746829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:37:58.591800 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:37:58.591845 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:37:59.746788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:38:29.746735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:38:58.615667 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:38:58.615704 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:38:59.746781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:39:29.746717 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:39:58.635172 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:39:58.635216 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:39:59.746810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:40:29.746775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:40:58.661338 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:40:58.661387 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:40:59.746812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:41:29.746791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:41:59.746787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:42:00.682466 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:42:00.682598 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:42:29.746878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:42:59.746826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:43:00.706237 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:43:00.706281 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:43:29.746966 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:43:59.746869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:44:00.733041 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:44:00.733109 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:44:29.746910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:44:59.746877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:45:00.755518 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:45:00.755559 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:45:29.746905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:45:59.746832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:46:00.774175 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:46:00.774226 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:46:29.746763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:46:59.746717 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:47:00.796382 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:47:00.796452 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:47:29.746773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:47:59.746764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:48:00.802736 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:48:00.802789 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:48:29.746830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:48:59.746857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:49:00.807486 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:49:00.807707 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:49:29.746800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:49:59.746773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:50:00.811617 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:50:00.811657 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:50:29.746752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:50:59.746809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:51:00.815843 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:51:00.815902 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:51:29.747602 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:51:59.746763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:52:00.819778 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:52:00.819828 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:52:29.746792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:52:59.747139 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:53:00.823577 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:53:00.823637 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:53:29.746787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:53:59.746775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:54:00.828186 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:54:00.828247 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:54:29.746725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:54:59.746771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:55:00.832405 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:55:00.832442 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:55:29.747212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:55:59.746856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:56:00.837333 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:56:00.837400 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:56:29.746831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:56:59.746970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:57:00.843642 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:57:00.843694 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:57:29.746756 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:57:59.746730 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:58:00.848509 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:58:00.848583 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:58:29.746854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:58:59.746814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:59:00.852910 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:59:00.852969 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:59:29.746978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:59:59.746757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:00:00.857006 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:00:00.857061 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:00:29.746765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:00:59.746806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:01:00.870336 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:01:00.870363 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:01:29.746790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:01:59.746740 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:02:00.892113 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:02:00.892290 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:02:29.746767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:02:59.746769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:03:00.913871 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:03:00.913922 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:03:29.746941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:03:59.746784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:04:00.938313 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:04:00.938347 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:04:29.746821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:04:59.746873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:05:00.959715 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:05:00.960174 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:05:29.746873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:05:59.746704 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:06:00.980239 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:06:00.980297 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:06:29.747070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:06:59.746741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:07:01.000880 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:07:01.000937 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:07:29.746794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:07:59.746722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:08:01.022462 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:08:01.022509 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:08:29.746826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:08:59.746763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:09:01.042241 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:09:01.042324 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:09:29.746848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:09:59.746754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:10:01.060728 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:10:01.060774 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:10:29.747029 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:10:59.746742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:11:01.080792 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:11:01.080853 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:11:29.746927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:11:59.746709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:12:01.101511 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:12:01.101560 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:12:29.746763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:12:59.747040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:13:01.129384 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:13:01.129423 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:13:29.747247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:13:59.746873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:14:01.149401 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:14:01.149436 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:14:29.746810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:14:59.746761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:15:01.168156 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:15:01.168303 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:15:29.746864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:15:59.746809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:16:01.189754 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:16:01.189816 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:16:29.746786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:16:59.746946 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:17:01.211321 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:17:01.211345 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:17:29.746744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:17:59.746896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:18:01.231467 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:18:01.231508 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:18:29.746885 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:18:59.746888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:19:01.253505 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:19:01.253976 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:19:29.746757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:19:59.746752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:20:01.274621 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:20:01.274652 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:20:29.746761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:20:59.746850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:21:01.296371 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:21:01.296406 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:21:29.746778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:21:59.746821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:22:01.313097 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:22:01.313151 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:22:29.746822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:22:59.746760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:23:01.339146 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:23:01.339184 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:23:29.746782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:23:59.746828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:24:01.356959 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:24:01.357011 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:24:29.746997 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:24:59.746810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:25:01.376247 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:25:01.376278 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:25:29.746783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:25:59.746743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:26:01.394796 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:26:01.395467 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:26:29.746826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:26:59.746781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:27:01.416089 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:27:01.416157 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:27:29.746774 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:27:59.746762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:28:01.440066 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:28:01.440116 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:28:29.746846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:28:59.746956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:29:01.459015 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:29:01.459070 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:29:29.746749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:29:59.746788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:30:01.477874 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:30:01.478008 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:30:29.746853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:30:59.746829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:31:01.498247 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:31:01.498408 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:31:29.746763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:31:59.746816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:32:03.510307 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:32:03.510364 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:32:29.746753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:32:59.746821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:33:03.514509 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:33:03.514555 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:33:29.746777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:33:59.746776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:34:03.518993 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:34:03.519028 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:34:29.746848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:34:59.746969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:35:03.535051 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:35:03.535088 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:35:29.746902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:35:59.746758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:36:03.538936 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:36:03.538971 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host