By type
2022/03/23 02:11:00.016619 beat.go:285: INFO Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs]
2022/03/23 02:11:00.016671 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/23 02:11:00.016751 logstash.go:90: INFO Max Retries set to: 3
2022/03/23 02:11:00.016796 metrics.go:23: INFO Metrics logging every 30s
2022/03/23 02:11:00.016847 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/23 02:11:00.016982 publish.go:295: INFO Publisher name: onap-portal-sdk-856bc9b5d4-bhnd9
2022/03/23 02:11:00.017205 async.go:63: INFO Flush Interval set to: 1s
2022/03/23 02:11:00.017244 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/23 02:11:00.017794 beat.go:221: INFO filebeat start running.
2022/03/23 02:11:00.017852 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/23 02:11:00.059516 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/23 02:11:00.059642 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/23 02:11:00.059728 crawler.go:38: INFO Loading Prospectors: 1
2022/03/23 02:11:00.059802 registrar.go:236: INFO Starting Registrar
2022/03/23 02:11:00.059935 sync.go:41: INFO Start sending events to output
2022/03/23 02:11:00.060146 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/23 02:11:00.060221 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/23 02:11:00.060357 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/23 02:11:00.060420 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/23 02:11:30.017276 metrics.go:39: INFO Non-zero metrics in the last 30s: registrar.writes=1
2022/03/23 02:11:50.064149 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/23 02:11:50.064262 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/23 02:11:50.064471 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/23 02:11:50.064559 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/23 02:11:50.064599 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/23 02:11:55.071982 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:11:55.072104 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:11:56.077715 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:11:56.077854 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:11:58.085168 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:11:58.085276 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:12:00.017288 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=55
2022/03/23 02:12:02.094427 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:12:02.094462 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:12:10.105080 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:12:10.105127 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:12:26.114744 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:12:26.114778 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:12:30.017200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:12:58.124791 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:12:58.124901 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:13:00.017280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:13:30.017403 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:13:58.137678 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:13:58.137737 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:14:00.017171 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:14:30.017436 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:14:58.148114 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:14:58.148178 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:15:00.017234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:15:30.017367 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:15:58.158097 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:15:58.158126 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:16:00.017225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:16:30.017235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:16:55.076737 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/23 02:16:58.168512 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:16:58.168562 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:17:00.017328 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/23 02:17:10.078483 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/23 02:17:10.078581 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/23 02:17:10.078606 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/23 02:17:30.017281 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-3
2022/03/23 02:17:58.178048 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:17:58.178077 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:18:00.017156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:18:30.017264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:18:58.187620 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:18:58.187699 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:19:00.017243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:19:30.017183 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:19:58.197868 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:19:58.197914 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:20:00.017148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:20:30.017141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:20:58.207264 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:20:58.207303 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:21:00.017489 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:21:30.017099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:21:58.218808 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:21:58.218845 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:22:00.017225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:22:30.017323 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:22:58.227765 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:22:58.227798 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:23:00.017254 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:23:30.017096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:23:58.238022 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:23:58.238062 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:24:00.017174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:24:30.017140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:24:58.245851 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:24:58.245896 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:25:00.017217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:25:30.017199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:25:58.257412 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:25:58.257446 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:26:00.017109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:26:30.017146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:26:58.266430 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:26:58.266454 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:27:00.017534 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:27:30.017057 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:27:58.277030 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:27:58.277068 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:28:00.017162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:28:30.017330 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:28:58.285223 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:28:58.285245 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:29:00.017205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:29:30.017139 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:29:58.295834 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:29:58.295868 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:30:00.017154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:30:30.017247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:30:58.305088 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:30:58.305115 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:31:00.017182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:31:30.017261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:31:58.316144 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:31:58.316189 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:32:00.017162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:32:30.017181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:32:58.325703 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:32:58.325779 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:33:00.017255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:33:30.017257 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:33:58.336034 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:33:58.336077 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:34:00.017234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:34:30.017195 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:34:58.346249 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:34:58.346301 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:35:00.017140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:35:30.017171 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:35:58.364748 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:35:58.364790 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:36:00.017200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:36:30.017178 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:36:58.374428 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:36:58.374507 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:37:00.017201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:37:30.017195 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:37:58.384975 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:37:58.385027 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:38:00.017159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:38:30.017151 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:38:58.394475 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:38:58.394512 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:39:00.017175 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:39:30.017152 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:39:58.404811 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:39:58.404875 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:40:00.017170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:40:30.017134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:40:58.414401 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:40:58.414465 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:41:00.017259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:41:30.017225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:41:58.423999 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:41:58.424034 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:42:00.017243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:42:30.017173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:42:58.433115 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:42:58.433159 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:43:00.017244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:43:30.017220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:43:58.442418 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:43:58.442443 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:44:00.017225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:44:30.017295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:44:58.450924 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:44:58.451080 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:45:00.017209 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:45:30.017215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:45:58.461949 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:45:58.461997 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:46:00.017243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:46:30.017202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:46:58.471881 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:46:58.471934 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:47:00.017243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:47:30.017136 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:47:58.481707 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:47:58.481755 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:48:00.017189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:48:30.017280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:48:58.490859 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:48:58.490900 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:49:00.017169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:49:30.017154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:49:58.499925 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:49:58.499959 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:50:00.017205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:50:30.017292 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:50:58.510654 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:50:58.510717 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:51:00.017188 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:51:30.017207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:51:58.521480 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:51:58.521523 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:52:00.017241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:52:30.017279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:52:58.530853 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:52:58.530896 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:53:00.017243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:53:30.017230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:53:58.541774 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:53:58.541814 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:54:00.017210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:54:30.017317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:54:58.551157 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:54:58.551225 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:55:00.017137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:55:30.017269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:55:58.560909 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:55:58.561075 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:56:00.017220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:56:30.017294 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:56:58.570470 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:56:58.570505 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:57:00.017248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:57:30.017077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:57:58.580260 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:57:58.580294 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:58:00.017294 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:58:30.017278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:58:58.589930 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:58:58.590068 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:59:00.017180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:59:30.017235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 02:59:58.599479 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 02:59:58.599512 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:00:00.017188 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:00:30.017143 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:00:58.609057 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:00:58.609101 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:01:00.017215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:01:30.017227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:01:58.620617 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:01:58.620663 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:02:00.017164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:02:30.017273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:02:58.630067 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:02:58.630110 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:03:00.017169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:03:30.017251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:03:58.639891 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:03:58.639928 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:04:00.017259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:04:30.017172 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:04:58.649115 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:04:58.649162 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:05:00.017158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:05:30.017267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:05:58.660672 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:05:58.660707 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:06:00.017171 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:06:30.017229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:06:58.670616 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:06:58.670676 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:07:00.017234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:07:30.017188 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:07:58.681803 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:07:58.681844 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:08:00.017232 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:08:30.017163 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:08:58.691130 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:08:58.691165 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:09:00.017240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:09:30.017200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:09:58.702448 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:09:58.702476 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:10:00.017264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:10:30.017249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:10:58.711246 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:10:58.711280 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:11:00.017158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:11:30.017207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:11:58.722122 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:11:58.722182 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:12:00.017145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:12:30.017251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:12:58.732421 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:12:58.732462 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:13:00.017212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:13:30.017367 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:13:58.743501 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:13:58.743532 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:14:00.017071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:14:30.017179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:14:58.751764 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:14:58.751808 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:15:00.017185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:15:30.017150 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:15:58.762072 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:15:58.762104 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:16:00.017287 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:16:30.017210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:16:58.772047 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:16:58.772089 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:17:00.017184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:17:30.017148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:17:58.782312 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:17:58.782344 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:18:00.017028 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:18:30.017214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:18:58.790337 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:18:58.790371 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:19:00.017234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:19:30.017096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:19:58.799581 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:19:58.799806 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:20:00.017353 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:20:30.017182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:20:58.808546 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:20:58.808579 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:21:00.017187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:21:30.017182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:21:58.818649 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:21:58.818693 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:22:00.017215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:22:30.017230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:22:58.830121 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:22:58.830163 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:23:00.017114 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:23:30.017321 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:23:58.840724 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:23:58.840775 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:24:00.017278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:24:30.017185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:24:58.849026 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:24:58.849062 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:25:00.017123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:25:30.017262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:25:58.860485 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:25:58.860527 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:26:00.017140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:26:30.017243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:26:58.870157 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:26:58.870206 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:27:00.017074 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:27:30.017187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:27:58.880535 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:27:58.880573 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:28:00.017333 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:28:30.017181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:28:58.890973 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:28:58.891110 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:29:00.017284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:29:30.017185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:29:58.902600 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:29:58.902640 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:30:00.017122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:30:30.017233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:30:58.912453 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:30:58.912509 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:31:00.017077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:31:30.017266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:31:58.922077 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:31:58.922132 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:32:00.017256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:32:30.017230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:32:58.932173 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:32:58.932206 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:33:00.017085 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:33:30.017109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:33:58.941487 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:33:58.941526 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:34:00.017262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:34:30.017201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:34:58.950641 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:34:58.950690 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:35:00.017214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:35:30.017198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:35:58.960220 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:35:58.960269 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:36:00.017107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:36:30.017238 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:36:58.969551 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:36:58.969593 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:37:00.017129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:37:30.017317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:37:58.980487 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:37:58.980543 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:38:00.017154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:38:30.017227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:38:58.990168 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:38:58.990230 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:39:00.017230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:39:30.017195 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:39:59.000457 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:39:59.000495 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:40:00.017231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:40:30.017248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:40:59.009621 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:40:59.009656 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:41:00.017235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:41:30.017170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:41:59.019283 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:41:59.019324 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:42:00.017314 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:42:30.017293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:42:59.029443 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:42:59.029514 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:43:00.017205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:43:30.017183 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:43:59.038763 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:43:59.038806 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:44:00.017189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:44:30.017211 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:44:59.048538 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:44:59.048580 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:45:00.017259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:45:30.017302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:45:59.058552 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:45:59.058580 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:46:00.017232 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:46:30.017220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:46:59.067445 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:46:59.067489 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:47:00.017268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:47:30.017252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:47:59.075364 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:47:59.075393 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:48:00.017083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:48:30.017210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:48:59.083701 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:48:59.083747 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:49:00.017136 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:49:30.017155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:49:59.092980 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:49:59.093035 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:50:00.017146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:50:30.017222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:50:59.102080 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:50:59.102125 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:51:00.017333 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:51:30.017336 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:51:59.113127 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:51:59.113150 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:52:00.017301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:52:30.017256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:52:59.122203 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:52:59.122238 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:53:00.017260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:53:30.017212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:53:59.133628 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:53:59.133678 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:54:00.017166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:54:30.017140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:54:59.179649 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:54:59.179699 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:55:00.017134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:55:30.017082 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:55:59.188198 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:55:59.188244 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:56:00.017243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:56:30.017205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:56:59.198066 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:56:59.198107 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:57:00.017193 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:57:30.017158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:57:59.210316 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:57:59.210376 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:58:00.017142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:58:30.017190 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:58:59.219170 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:58:59.219227 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:59:00.017093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:59:30.017245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:59:59.228921 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:59:59.228996 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:00:00.017207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:00:30.017285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:00:59.237652 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:00:59.237682 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:01:00.017220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:01:30.017211 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:01:59.247667 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:01:59.247702 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:02:00.017180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:02:30.017210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:02:59.257881 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:02:59.257940 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:03:00.017223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:03:30.017201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:03:59.269285 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:03:59.269333 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:04:00.017208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:04:30.017205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:04:59.278250 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:04:59.278296 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:05:00.017190 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:05:30.017196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:05:59.290313 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:05:59.290351 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:06:00.017176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:06:30.017199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:06:59.301758 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:06:59.301817 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:07:00.017221 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:07:30.017236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:07:59.312773 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:07:59.312876 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:08:00.017088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:08:30.017235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:08:59.322420 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:08:59.322623 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:09:00.017276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:09:30.017184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:09:59.333909 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:09:59.333949 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:10:00.017203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:10:30.017138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:10:59.343333 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:10:59.343378 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:11:00.017185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:11:30.017120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:11:59.353910 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:11:59.353951 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:12:00.017236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:12:30.017263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:12:59.364430 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:12:59.364495 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:13:00.017302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:13:30.017255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:13:59.375186 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:13:59.375232 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:14:00.017236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:14:30.017225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:14:59.385563 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:14:59.385602 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:15:00.017239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:15:30.017159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:15:59.394850 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:15:59.394895 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:16:00.017198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:16:30.017100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:16:59.405019 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:16:59.405063 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:17:00.017152 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:17:30.017119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:17:59.414435 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:17:59.414484 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:18:00.017169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:18:30.017202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:18:59.424944 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:18:59.424989 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:19:00.017186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:19:30.017239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:19:59.435448 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:19:59.435521 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:20:00.017233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:20:30.017229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:20:59.445832 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:20:59.445877 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:21:00.017150 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:21:30.017237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:21:59.455822 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:21:59.455866 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:22:00.017243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:22:30.017274 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:22:59.466997 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:22:59.467069 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:23:00.017255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:23:30.017202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:23:59.477255 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:23:59.477293 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:24:00.017198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:24:30.017212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:24:59.488816 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:24:59.488865 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:25:00.017287 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:25:30.017222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:25:59.499545 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:25:59.499593 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:26:00.017191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:26:30.017185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:26:59.510697 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:26:59.510726 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:27:00.017083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:27:30.017182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:27:59.520976 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:27:59.521013 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:28:00.017186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:28:30.017233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:28:59.529947 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:28:59.529998 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:29:00.017233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:29:30.017217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:29:59.540230 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:29:59.540283 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:30:00.017176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:30:30.017305 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:30:59.551263 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:30:59.551305 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:31:00.017157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:31:30.017181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 04:31:59.561533 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:31:59.561570 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 04:32:00.017148 metrics.go:34: INFO No non-zero metrics in the last 30s