Results

          2022/03/13 03:04:41.522467 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/13 03:04:41.522590 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/13 03:04:41.522916 logstash.go:90: INFO Max Retries set to: 3
2022/03/13 03:04:41.523117 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/13 03:04:41.523316 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-mm4r4
2022/03/13 03:04:41.523748 async.go:63: INFO Flush Interval set to: 1s
2022/03/13 03:04:41.523795 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/13 03:04:41.524261 metrics.go:23: INFO Metrics logging every 30s
2022/03/13 03:04:41.531047 beat.go:221: INFO filebeat start running.
2022/03/13 03:04:41.531185 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/13 03:04:41.542442 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/13 03:04:41.542598 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/13 03:04:41.542663 crawler.go:38: INFO Loading Prospectors: 1
2022/03/13 03:04:41.543009 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/13 03:04:41.543159 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/13 03:04:41.543193 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/13 03:04:41.543216 registrar.go:236: INFO Starting Registrar
2022/03/13 03:04:41.543253 sync.go:41: INFO Start sending events to output
2022/03/13 03:04:41.543307 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/13 03:05:01.546085 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/13 03:05:01.547005 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/13 03:05:01.547183 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/13 03:05:01.547409 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/13 03:05:01.547478 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/13 03:05:06.582014 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:05:06.582093 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:05:07.587917 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:05:07.587952 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:05:09.596936 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:05:09.596985 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:05:11.526064 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=3 registrar.states.current=3 registrar.states.update=3 registrar.writes=2
2022/03/13 03:05:13.612290 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:05:13.612339 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:05:21.621193 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:05:21.621234 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:05:37.627559 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:05:37.627636 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:05:41.526095 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:06:09.635224 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:06:09.635262 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:06:11.525888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:06:41.525889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:07:09.639911 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:07:09.639960 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:07:11.525959 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:07:41.525997 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:08:09.646675 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:08:09.646901 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:08:11.526000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:08:41.530656 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:09:09.651278 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:09:09.651329 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:09:11.525892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:09:41.525927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:10:06.563180 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/13 03:10:06.563180 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/13 03:10:06.565565 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/13 03:10:06.565655 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/13 03:10:09.657570 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:10:09.657617 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:10:11.525960 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/13 03:10:22.573906 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/03/13 03:10:41.525968 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/13 03:11:09.661846 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:11:09.661884 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:11:11.525930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:11:41.526112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:12:09.667167 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:12:09.667306 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:12:11.525982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:12:41.525877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:13:09.671596 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:13:09.671660 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:13:11.525975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:13:41.525863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:14:09.677361 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:14:09.677418 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:14:11.531726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:14:41.528740 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:15:09.681973 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:15:09.682037 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:15:11.526092 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:15:41.525956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:16:09.686987 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:16:09.687039 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:16:11.528763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:16:41.526057 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:17:09.690428 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:17:09.690474 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:17:11.526122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:17:41.525891 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:18:09.696008 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:18:09.696050 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:18:11.525906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:18:41.526067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:19:09.703386 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:19:09.703445 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:19:11.532728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:19:41.526913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:20:09.709551 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:20:09.709634 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:20:11.525893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:20:41.526385 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:21:09.721933 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:21:09.722080 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:21:11.526008 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:21:41.525915 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:22:09.744373 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:22:09.744786 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:22:11.525910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:22:41.526126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:23:09.750845 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:23:09.750901 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:23:11.525919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:23:41.525932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:24:09.757554 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:24:09.757600 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:24:11.525894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:24:41.525986 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:25:09.761614 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:25:09.761665 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:25:11.525883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:25:41.525857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:26:09.767390 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:26:09.767437 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:26:11.525957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:26:41.526006 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:27:09.775027 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:27:09.775073 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:27:11.525969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:27:41.525930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:28:09.786796 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:28:09.787039 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:28:11.525988 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:28:41.525883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:29:09.793903 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:29:09.793953 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:29:11.525969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:29:41.525955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:30:09.800938 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:30:09.800985 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:30:11.525915 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:30:41.526123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:31:09.812740 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:31:09.812792 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:31:11.525997 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:31:41.525919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:32:09.827809 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:32:09.827864 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:32:11.525932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:32:41.525952 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:33:09.836891 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:33:09.836940 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:33:11.525863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:33:41.526025 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:34:09.844846 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:34:09.844893 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:34:11.526168 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:34:41.525940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:35:09.853072 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:35:09.853114 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:35:11.525887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:35:41.525937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:36:09.861561 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:36:09.861613 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:36:11.525955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:36:41.525886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:37:09.870316 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:37:09.870368 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:37:11.525903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:37:41.525974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:38:09.881540 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:38:09.881589 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:38:11.525913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:38:41.526534 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:39:09.890709 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:39:09.890753 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:39:11.525971 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:39:41.525968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:40:09.900255 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:40:09.900295 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:40:11.526013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:40:41.532785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:41:09.914888 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:41:09.914946 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:41:11.525876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:41:41.525933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:42:09.930415 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:42:09.930463 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:42:11.525881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:42:41.526767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:43:09.937865 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:43:09.937923 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:43:11.525869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:43:41.526009 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:44:09.948968 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:44:09.949011 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:44:11.525970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:44:41.525896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:45:09.959262 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:45:09.959310 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:45:11.526103 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:45:41.525973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:46:09.975757 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:46:09.975806 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:46:11.525932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:46:41.526043 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:47:09.986252 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:47:09.986329 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:47:11.526066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:47:41.525991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:48:09.999855 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:09.999905 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:11.526411 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:48:41.525963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:49:10.031001 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:49:10.031059 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:49:11.525888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:49:41.525926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:50:10.040682 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:50:10.040724 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:50:11.525953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:50:41.528706 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:51:10.056771 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:51:10.056829 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:51:11.526011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:51:41.525893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:52:10.066014 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:52:10.066058 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:52:11.526083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:52:41.526055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:53:10.073383 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:53:10.073439 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:53:11.526180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:53:41.525901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:54:10.082469 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:54:10.082525 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:54:11.525854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:54:41.526350 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:55:10.090366 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:55:10.090404 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:55:11.525933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:55:41.526091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:56:10.101737 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:56:10.101787 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:56:11.525988 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:56:41.525988 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:57:10.109986 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:57:10.110038 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:57:11.526026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:57:41.526331 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:58:10.121240 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:58:10.121289 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:58:11.525936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:58:41.526003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:59:10.127368 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:59:10.127403 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:59:11.525924 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:59:41.525865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:00:10.151405 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:00:10.151475 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:00:11.525974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:00:41.525891 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:01:10.165272 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:01:10.165321 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:01:11.526125 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:01:41.526032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:02:10.178005 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:02:10.178071 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:02:11.525962 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:02:41.525913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:03:10.185088 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:03:10.185123 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:03:11.525985 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:03:41.525862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:04:10.195173 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:04:10.195229 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:04:11.525970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:04:41.525975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:05:10.212670 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:05:10.212726 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:05:11.526019 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:05:41.525989 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:06:10.236812 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:06:10.236890 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:06:11.526770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:06:41.526629 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:07:10.246859 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:07:10.246906 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:07:11.526223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:07:41.528645 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:08:10.260823 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:08:10.261619 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:08:11.528920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:08:41.525966 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:09:10.268651 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:09:10.268692 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:09:11.526106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:09:41.525922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:10:10.281038 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:10:10.281078 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:10:11.526007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:10:41.525872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:11:10.302685 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:11:10.302741 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:11:11.525979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:11:41.525919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:12:10.332075 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:12:10.332132 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:12:11.525952 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:12:41.525905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:13:10.340701 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:13:10.340755 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:13:11.525970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:13:41.525834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:14:10.349884 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:14:10.349937 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:14:11.526036 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:14:41.526159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:15:10.360634 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:15:10.360705 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:15:11.525959 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:15:41.526009 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:16:10.370246 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:16:10.370289 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:16:11.528703 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:16:41.525924 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:17:10.377201 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:17:10.377267 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:17:11.525895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:17:41.526001 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:18:10.390894 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:18:10.390939 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:18:11.525962 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:18:41.525920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:19:10.398919 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:19:10.398962 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:19:11.525889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:19:41.525953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:20:10.407281 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:20:10.407327 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:20:11.525918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:20:41.525986 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:21:10.415783 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:21:10.415824 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:21:11.525969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:21:41.525875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:22:10.425413 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:22:10.425456 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:22:11.525902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:22:41.525942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:23:10.434236 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:23:10.434279 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:23:11.525935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:23:41.525924 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:24:10.450917 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:24:10.451216 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:24:11.525963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:24:41.525975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:25:10.458736 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:25:10.458790 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:25:11.525946 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:25:41.526005 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:26:10.477844 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:26:10.477904 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:26:11.525896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:26:41.526005 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:27:10.484528 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:27:10.484566 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:27:11.525965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:27:41.525955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:28:10.498449 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:28:10.498503 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:28:11.525971 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:28:41.525906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:29:10.506197 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:29:10.506320 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:29:11.525932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:29:41.525929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:30:10.515606 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:30:10.515653 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:30:11.525961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:30:41.525941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:31:10.522980 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:31:10.523027 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:31:11.525970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:31:41.525930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:32:10.535379 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:32:10.535413 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:32:11.525905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:32:41.525931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:33:10.544883 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:33:10.544929 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:33:11.525918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:33:41.526022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:34:10.553829 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:34:10.553868 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:34:11.525939 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:34:41.525874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:35:10.570416 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:35:10.570469 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:35:11.525913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:35:41.525866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:36:10.580678 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:36:10.580744 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:36:11.525918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:36:41.525977 metrics.go:34: INFO No non-zero metrics in the last 30s