By type
2022/03/14 02:46:53.737905 beat.go:285: INFO Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs]
2022/03/14 02:46:53.737943 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/14 02:46:53.738025 logstash.go:90: INFO Max Retries set to: 3
2022/03/14 02:46:53.738091 metrics.go:23: INFO Metrics logging every 30s
2022/03/14 02:46:53.738138 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/14 02:46:53.738237 publish.go:295: INFO Publisher name: onap-portal-sdk-856bc9b5d4-7cqfk
2022/03/14 02:46:53.738402 async.go:63: INFO Flush Interval set to: 1s
2022/03/14 02:46:53.738424 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/14 02:46:53.738821 beat.go:221: INFO filebeat start running.
2022/03/14 02:46:53.738954 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/14 02:46:54.189763 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/14 02:46:54.189846 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/14 02:46:54.189883 crawler.go:38: INFO Loading Prospectors: 1
2022/03/14 02:46:54.190030 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/14 02:46:54.190030 registrar.go:236: INFO Starting Registrar
2022/03/14 02:46:54.190108 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/14 02:46:54.190148 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/14 02:46:54.190180 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/14 02:46:54.190206 sync.go:41: INFO Start sending events to output
2022/03/14 02:47:23.738473 metrics.go:39: INFO Non-zero metrics in the last 30s: registrar.writes=1
2022/03/14 02:47:24.191898 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/14 02:47:24.192202 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/14 02:47:24.192276 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/14 02:47:24.192350 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/14 02:47:24.192294 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/14 02:47:29.200916 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:47:29.200985 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:47:30.204095 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:47:30.204141 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:47:32.207107 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:47:32.207144 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:47:36.213187 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:47:36.213218 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:47:44.218564 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:47:44.218785 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:47:53.738455 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/14 02:48:00.224496 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:48:00.224527 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:48:23.738439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:48:32.231504 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:48:32.231532 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:48:53.738480 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:49:23.738519 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:49:32.237353 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:49:32.237381 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:49:53.738443 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:50:23.738635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:50:32.245192 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:50:32.245251 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:50:53.738372 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:51:23.738423 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:51:32.250794 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:51:32.250823 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:51:53.738398 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:52:23.738342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:52:29.201118 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/14 02:52:32.256936 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:52:32.256995 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:52:44.202665 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/14 02:52:44.202759 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/14 02:52:44.202786 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/14 02:52:53.738650 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-4
2022/03/14 02:53:23.738354 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:53:32.263411 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:53:32.263445 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:53:53.738485 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:54:23.738376 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:54:32.269423 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:54:32.269468 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:54:53.738439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:55:23.738482 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:55:32.275590 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:55:32.275629 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:55:53.738413 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:56:23.738378 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:56:32.281568 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:56:32.281596 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:56:53.738595 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:57:23.738396 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:57:32.287423 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:57:32.287480 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:57:53.738392 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:58:23.738401 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:58:32.293175 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:58:32.293207 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:58:53.738408 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:59:23.738323 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 02:59:32.299437 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:59:32.299477 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 02:59:53.738378 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:00:23.738373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:00:32.304752 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:00:32.304786 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:00:53.738359 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:01:23.738400 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:01:32.310926 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:01:32.310975 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:01:53.738406 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:02:23.738396 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:02:32.318169 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:02:32.318206 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:02:53.738417 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:03:23.738390 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:03:32.324485 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:03:32.324521 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:03:53.738397 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:04:23.738479 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:04:32.330481 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:04:32.330514 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:04:53.738426 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:05:23.738390 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:05:32.337039 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:05:32.337090 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:05:53.738425 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:06:23.738444 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:06:32.344284 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:06:32.344324 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:06:53.738390 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:07:23.738406 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:07:32.351259 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:07:32.351291 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:07:53.738400 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:08:23.738447 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:08:32.356992 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:08:32.357036 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:08:53.738406 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:09:23.738397 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:09:32.363412 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:09:32.363460 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:09:53.738392 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:10:23.738392 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:10:32.369166 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:10:32.369226 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:10:53.738435 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:11:23.738380 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:11:32.375909 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:11:32.375959 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:11:53.738438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:12:23.738347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:12:32.381593 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:12:32.381621 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:12:53.738423 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:13:23.738387 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:13:32.388198 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:13:32.388243 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:13:53.738477 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:14:23.738405 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:14:32.394535 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:14:32.394576 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:14:53.738463 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:15:23.738373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:15:32.400985 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:15:32.401019 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:15:53.738384 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:16:23.738354 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:16:32.407963 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:16:32.408000 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:16:53.738432 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:17:23.738404 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:17:32.414754 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:17:32.414792 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:17:53.738389 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:18:23.738418 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:18:32.421563 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:18:32.421604 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:18:53.738414 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:19:23.738513 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:19:32.429547 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:19:32.429591 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:19:53.738418 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:20:23.738436 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:20:32.435893 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:20:32.435924 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:20:53.738388 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:21:23.738386 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:21:32.442605 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:21:32.442635 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:21:53.738436 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:22:23.738345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:22:32.448658 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:22:32.448925 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:22:53.738331 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:23:23.738429 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:23:32.455738 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:23:32.455771 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:23:53.738459 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:24:23.738394 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:24:32.466715 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:24:32.466747 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:24:53.738359 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:25:23.738415 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:25:32.472246 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:25:32.472279 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:25:53.738450 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:26:23.738429 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:26:32.477974 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:26:32.478006 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:26:53.738424 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:27:23.738390 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:27:32.484533 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:27:32.484564 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:27:53.738452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:28:23.738393 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:28:32.490315 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:28:32.490365 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:28:53.738345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:29:23.738365 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:29:32.497538 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:29:32.497580 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:29:53.738437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:30:23.738371 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:30:32.507202 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:30:32.507245 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:30:53.738380 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:31:23.738398 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:31:32.513641 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:31:32.513687 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:31:53.738425 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:32:23.738421 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:32:32.520108 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:32:32.520151 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:32:53.738445 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:33:23.738391 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:33:32.525738 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:33:32.525795 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:33:53.738444 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:34:23.738440 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:34:32.532152 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:34:32.532189 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:34:53.738428 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:35:23.738397 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:35:32.540920 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:35:32.540978 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:35:53.738401 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:36:23.738392 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:36:32.547397 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:36:32.547427 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:36:53.738404 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:37:23.738437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:37:32.553202 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:37:32.553235 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:37:53.738368 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:38:23.738412 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:38:32.559521 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:38:32.559551 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:38:53.738402 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:39:23.738433 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:39:32.564524 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:39:32.564560 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:39:53.738392 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:40:23.738368 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:40:32.570297 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:40:32.570338 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:40:53.738375 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:41:23.738420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:41:32.576925 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:41:32.576979 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:41:53.738413 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:42:23.738383 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:42:32.582831 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:42:32.582862 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:42:53.738347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:43:23.738409 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:43:32.591023 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:43:32.591054 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:43:53.738427 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:44:23.738364 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:44:32.596542 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:44:32.596649 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:44:53.738462 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:45:23.738376 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:45:32.602116 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:45:32.602142 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:45:53.738448 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:46:23.738382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:46:32.608143 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:46:32.608188 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:46:53.738366 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:47:23.738334 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:47:32.614181 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:47:32.614228 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:47:53.738426 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:48:23.738386 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:48:32.620078 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:48:32.620105 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:48:53.738395 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:49:23.738417 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:49:32.626111 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:49:32.626143 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:49:53.738512 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:50:23.738411 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:50:32.631891 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:50:32.631922 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:50:53.738442 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:51:23.738347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:51:32.637839 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:51:32.637877 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:51:53.738430 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:52:23.738324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:52:32.643653 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:52:32.643684 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:52:53.738393 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:53:23.738441 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:53:32.649462 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:53:32.649500 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:53:53.738409 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:54:23.738356 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:54:32.655247 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:54:32.655283 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:54:53.738389 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:55:23.738428 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:55:32.661307 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:55:32.661346 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:55:53.738432 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:56:23.738399 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:56:32.667140 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:56:32.667173 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:56:53.738349 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:57:23.738364 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:57:32.673250 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:57:32.673300 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:57:53.738431 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:58:23.738411 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:58:32.679385 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:58:32.679418 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:58:53.738449 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:59:23.738360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:59:32.685738 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:59:32.685773 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:59:53.738462 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:00:23.738431 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:00:32.692336 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:00:32.692370 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:00:53.738421 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:01:23.738369 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:01:32.698514 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:01:32.698547 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:01:53.738534 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:02:23.738347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:02:32.704086 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:02:32.704116 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:02:53.738450 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:03:23.738413 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:03:32.710398 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:03:32.710428 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:03:53.738399 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:04:23.738396 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:04:32.716034 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:04:32.716071 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:04:53.738416 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:05:23.738408 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:05:32.721293 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:05:32.721323 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:05:53.738371 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:06:23.738392 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:06:32.726795 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:06:32.726829 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:06:53.738454 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:07:23.738439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:07:32.731990 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:07:32.732021 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:07:53.738405 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:08:23.738431 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:08:32.737760 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:08:32.737792 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:08:53.738433 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:09:23.738348 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:09:32.743973 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:09:32.744012 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:09:53.738432 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:10:23.738433 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:10:32.749526 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:10:32.749553 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:10:53.738471 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:11:23.738452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:11:32.755279 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:11:32.755308 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:11:53.738449 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:12:23.738382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:12:32.761249 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:12:32.761283 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:12:53.738406 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:13:23.738372 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:13:32.766872 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:13:32.766905 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:13:53.738376 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:14:23.738426 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:14:32.772786 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:14:32.772811 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:14:53.738360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:15:23.738396 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:15:32.778710 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:15:32.778756 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:15:53.738402 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:16:23.738403 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:16:32.785052 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:16:32.785084 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:16:53.738376 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:17:23.738419 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:17:32.791061 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:17:32.791094 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:17:53.738439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:18:23.738369 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:18:32.797087 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:18:32.797120 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:18:53.738401 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:19:23.738364 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:19:32.803275 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:19:32.803311 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:19:53.738481 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:20:23.738354 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:20:32.809798 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:20:32.809839 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:20:53.738469 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:21:23.738405 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:21:32.815330 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:21:32.815368 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:21:53.738467 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:22:23.738360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:22:32.820713 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:22:32.820746 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:22:53.738412 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:23:23.738398 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:23:32.826195 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:23:32.826238 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:23:53.738419 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:24:23.738421 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:24:32.832594 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:24:32.832624 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:24:53.738411 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:25:23.738422 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:25:32.838438 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:25:32.838472 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:25:53.738404 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:26:23.738375 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:26:32.843811 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:26:32.843840 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:26:53.738439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:27:23.738386 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:27:32.849922 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:27:32.849971 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:27:53.738431 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:28:23.738431 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:28:32.855636 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:28:32.855670 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:28:53.738465 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:29:23.738431 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:29:32.861297 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:29:32.861331 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:29:53.738378 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:30:23.738399 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:30:32.866516 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:30:32.866561 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:30:53.738408 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:31:23.738428 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:31:32.871975 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:31:32.872013 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:31:53.738403 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:32:23.738387 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:32:32.877783 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:32:32.877820 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:32:53.738380 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:33:23.738367 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:33:32.883294 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:33:32.883341 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:33:53.738444 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:34:23.738371 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:34:32.889292 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:34:32.889326 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:34:53.738421 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:35:23.738383 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:35:32.895310 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:35:32.895339 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:35:53.738424 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:36:23.738420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:36:32.901429 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:36:32.901466 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:36:53.738406 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:37:23.738393 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:37:32.907436 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:37:32.907470 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:37:53.738432 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:38:23.738459 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:38:32.912770 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:38:32.912804 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:38:53.738420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:39:23.738365 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:39:32.919174 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:39:32.919211 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:39:53.738393 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:40:23.738387 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:40:32.925390 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:40:32.925438 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:40:53.738402 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:41:23.738377 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:41:32.931428 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:41:32.931455 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:41:53.738388 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:42:23.738359 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:42:32.937548 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:42:32.937677 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:42:53.738476 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:43:23.738378 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:43:32.950184 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:43:32.950227 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:43:53.738362 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:44:23.738397 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:44:32.955700 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:44:32.955741 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:44:53.738428 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:45:23.738402 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:45:32.961670 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:45:32.961705 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:45:53.738394 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:46:23.738398 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:46:32.967717 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:46:32.967753 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:46:53.738407 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:47:23.738402 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:47:32.972990 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:47:32.973021 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:47:53.738497 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:48:23.738384 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:48:32.979163 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:48:32.979208 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:48:53.738350 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:49:23.738434 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:49:32.984919 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:49:32.984990 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:49:53.738363 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:50:23.738355 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:50:32.991442 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:50:32.991482 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:50:53.738360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:51:23.738331 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:51:32.998206 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:51:32.998241 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:51:53.738426 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:52:23.738363 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:52:33.003899 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:52:33.003934 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:52:53.738441 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:53:23.738412 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:53:33.009397 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:53:33.009428 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:53:53.738401 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:54:23.738336 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:54:33.015040 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:54:33.015086 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:54:53.738377 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:55:23.738420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:55:33.022742 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:55:33.022769 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:55:53.738414 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:56:23.738389 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:56:33.029617 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:56:33.029649 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:56:53.738383 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:57:23.738393 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:57:33.036121 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:57:33.036154 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:57:53.738489 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:58:23.738391 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:58:33.041425 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:58:33.041455 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:58:53.738362 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:59:23.738420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 04:59:33.046894 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:59:33.046917 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 04:59:53.738434 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 05:00:23.738417 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 05:00:33.052023 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 05:00:33.052057 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 05:00:53.738407 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 05:01:23.738391 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 05:01:33.058081 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 05:01:33.058108 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 05:01:53.738391 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 05:02:23.738394 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 05:02:33.063802 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 05:02:33.063835 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 05:02:53.738440 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 05:03:23.738407 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 05:03:33.069117 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 05:03:33.069148 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 05:03:53.738454 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 05:04:23.738432 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 05:04:33.074852 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 05:04:33.074892 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 05:04:53.738369 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 05:05:23.738390 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 05:05:33.080727 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 05:05:33.080757 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 05:05:53.738405 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 05:06:23.738335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 05:06:33.086047 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 05:06:33.086078 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 05:06:53.738354 metrics.go:34: INFO No non-zero metrics in the last 30s