By type
2022/03/09 11:49:29.962479 beat.go:285: INFO Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs]
2022/03/09 11:49:29.962548 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/09 11:49:29.962941 logstash.go:90: INFO Max Retries set to: 3
2022/03/09 11:49:29.963455 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/09 11:49:29.963562 metrics.go:23: INFO Metrics logging every 30s
2022/03/09 11:49:29.963921 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-57pdp
2022/03/09 11:49:29.964290 async.go:63: INFO Flush Interval set to: 1s
2022/03/09 11:49:29.964326 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/09 11:49:29.964953 beat.go:221: INFO filebeat start running.
2022/03/09 11:49:29.965057 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/09 11:49:29.973939 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/09 11:49:29.974095 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/09 11:49:29.974365 registrar.go:236: INFO Starting Registrar
2022/03/09 11:49:29.974510 crawler.go:38: INFO Loading Prospectors: 1
2022/03/09 11:49:29.974863 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/09 11:49:29.975115 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/09 11:49:29.975146 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/09 11:49:29.975141 sync.go:41: INFO Start sending events to output
2022/03/09 11:49:29.975214 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/09 11:49:49.979335 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/09 11:49:49.979466 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/09 11:49:49.979566 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/09 11:49:49.979629 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/09 11:49:49.979871 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/09 11:49:55.006217 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:49:55.006269 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:49:56.010781 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:49:56.010876 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:49:58.022590 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:49:58.022635 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:49:59.964126 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=5 filebeat.harvester.running=5 filebeat.harvester.started=5 libbeat.publisher.published_events=64 registrar.writes=1
2022/03/09 11:50:02.029124 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:50:02.029171 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:50:10.036456 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:50:10.036730 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:50:26.054583 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:50:26.054674 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:50:29.963882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 11:50:58.078162 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:50:58.078218 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:50:59.966576 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 11:51:29.963891 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 11:51:58.101029 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:51:58.101076 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:51:59.963917 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 11:52:29.963960 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 11:52:58.121464 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:52:58.121524 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:52:59.963887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 11:53:29.964154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 11:53:58.140149 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:53:58.140203 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:53:59.964017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 11:54:29.963861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 11:54:55.000171 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/09 11:54:55.000372 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/09 11:54:55.000378 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/09 11:54:55.000443 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/09 11:54:58.161361 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:54:58.161408 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:54:59.963930 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=4 filebeat.harvester.open_files=-4 filebeat.harvester.running=-4
2022/03/09 11:55:06.008544 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/03/09 11:55:29.963923 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=1 filebeat.harvester.open_files=-1 filebeat.harvester.running=-1
2022/03/09 11:55:58.179923 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:55:58.179971 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:55:59.963883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 11:56:29.963841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 11:56:58.199745 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:56:58.199799 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:56:59.963873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 11:57:29.964005 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 11:57:58.220436 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:57:58.220501 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:57:59.964045 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 11:58:29.963936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 11:58:58.238462 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:58:58.238525 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:58:59.964030 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 11:59:29.963927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 11:59:58.258281 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:59:58.258426 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 11:59:59.966339 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:00:29.963880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:00:58.277388 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:00:58.277442 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:00:59.965767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:01:29.966839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:01:58.333249 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:01:58.333340 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:01:59.966512 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:02:29.965226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:02:58.356280 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:02:58.356330 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:02:59.963918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:03:29.964150 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:03:58.400879 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:03:58.400927 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:03:59.967600 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:04:29.963963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:04:58.442238 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:04:58.442297 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:04:59.965575 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:05:29.967148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:05:58.490138 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:05:58.490185 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:05:59.973832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:06:29.971262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:06:58.521643 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:06:58.521695 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:06:59.963991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:07:29.963869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:07:58.540003 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:07:58.540051 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:07:59.963990 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:08:29.963931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:08:58.561015 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:08:58.561078 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:08:59.963953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:09:29.964013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:09:58.579597 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:09:58.579655 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:09:59.964031 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:10:29.963943 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:10:58.603544 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:10:58.603588 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:10:59.963876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:11:29.963936 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:11:58.621966 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:11:58.622008 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:11:59.964654 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:12:29.963898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:12:58.641048 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:12:58.641110 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:12:59.963903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:13:29.963844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:13:58.660107 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:13:58.660152 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:13:59.963922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:14:29.963913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:14:58.679547 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:14:58.679595 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:14:59.964002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:15:29.964715 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:15:58.701123 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:15:58.701189 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:15:59.963860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:16:29.964000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:16:58.733301 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:16:58.733425 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:16:59.963868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:17:29.964001 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:17:58.753698 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:17:58.753757 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:17:59.963894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:18:29.963876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:18:58.772133 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:18:58.772182 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:18:59.963973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:19:29.963944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:19:58.792822 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:19:58.792884 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:19:59.963933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:20:29.963972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:20:58.812998 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:20:58.813045 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:20:59.963924 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:21:29.963933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:21:58.837112 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:21:58.837162 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:21:59.963880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:22:29.964010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:22:58.857420 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:22:58.857460 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:22:59.963943 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:23:29.964021 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:23:58.877485 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:23:58.877562 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:23:59.963883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:24:29.963925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:24:58.901918 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:24:58.902150 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:24:59.963920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:25:29.963955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:25:58.926930 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:25:58.927310 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:25:59.964022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:26:29.963846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:26:58.948954 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:26:58.949005 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:26:59.963914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:27:29.963932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:27:58.966286 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:27:58.966323 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:27:59.963875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:28:29.963902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:28:58.992981 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:28:58.993025 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:28:59.963958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:29:29.963868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:29:59.012747 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:29:59.012893 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:29:59.963919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:30:29.963838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:30:59.035033 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:30:59.035082 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:30:59.963892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:31:29.964155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:31:59.053476 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:31:59.053543 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:31:59.963983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:32:29.963863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:32:59.071609 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:32:59.071648 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:32:59.963833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:33:29.963923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:33:59.091742 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:33:59.091797 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:33:59.963924 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:34:29.963907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:34:59.111964 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:34:59.112017 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:34:59.963838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:35:29.964564 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:35:59.130658 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:35:59.130716 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:35:59.963927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:36:29.964333 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:36:59.152177 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:36:59.152229 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:36:59.963931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:37:29.964017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:37:59.172963 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:37:59.173013 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:37:59.963905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:38:29.963895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:38:59.195748 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:38:59.195791 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:38:59.963994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:39:29.964079 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:39:59.202777 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:39:59.202830 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:39:59.963862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:40:29.964223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:40:59.226861 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:40:59.226951 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:40:59.963915 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:41:29.964007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:41:59.243822 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:41:59.244272 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:41:59.964201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:42:29.963950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:42:59.268248 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:42:59.268285 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:42:59.963998 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:43:29.963885 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:43:59.288190 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:43:59.288245 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:43:59.964989 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:44:29.963838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:44:59.309280 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:44:59.309329 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:44:59.963927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:45:29.963923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:45:59.327283 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:45:59.327326 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:45:59.964097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:46:29.963908 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:46:59.348278 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:46:59.348332 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:46:59.963890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:47:29.964039 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:47:59.367981 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:47:59.368049 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:47:59.963914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:48:29.963844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:48:59.390106 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:48:59.390158 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:48:59.963898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:49:29.963867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:49:59.408911 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:49:59.408962 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:49:59.963846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:50:29.963896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:50:59.430354 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:50:59.430409 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:50:59.963894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:51:29.963846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:51:59.450220 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:51:59.450259 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:51:59.963913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:52:29.963945 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:52:59.469248 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:52:59.469288 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:52:59.963954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:53:29.963977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:53:59.493151 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:53:59.493204 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:53:59.963828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:54:29.963891 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:54:59.514078 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:54:59.514135 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:54:59.963861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:55:29.963939 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:55:59.539643 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:55:59.539724 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:55:59.963991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:56:29.963887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:56:59.563716 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:56:59.563753 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:56:59.963853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:57:29.963872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:57:59.587141 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:57:59.587194 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:57:59.964025 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:58:29.963921 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:58:59.607320 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:58:59.607360 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:58:59.963973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:59:29.963952 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 12:59:59.634741 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:59:59.634831 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 12:59:59.963899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:00:29.964000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:00:59.652769 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:00:59.652811 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:00:59.963906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:01:29.963969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:01:59.672502 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:01:59.672545 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:01:59.963858 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:02:29.964148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:02:59.692610 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:02:59.692675 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:02:59.963953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:03:29.963846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:03:59.714454 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:03:59.714527 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:03:59.964001 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:04:29.963935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:04:59.741334 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:04:59.741371 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:04:59.963912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:05:29.963954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:05:59.770191 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:05:59.770244 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:05:59.963896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:06:29.963928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:06:59.806657 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:06:59.806708 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:06:59.966585 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:07:29.963873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:07:59.828945 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:07:59.828999 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:07:59.963840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:08:29.963908 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:08:59.855720 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:08:59.855759 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:08:59.963946 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:09:29.963866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:09:59.877846 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:09:59.877910 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:09:59.964112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:10:29.964108 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:10:59.898788 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:10:59.898847 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:10:59.963889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:11:29.963891 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:11:59.922819 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:11:59.922881 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:11:59.963885 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:12:29.963856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:12:59.941595 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:12:59.941935 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:12:59.963892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:13:29.964091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:13:59.959976 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:13:59.960014 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:13:59.963854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:14:29.963889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:14:59.964525 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:14:59.977747 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:14:59.977931 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:15:29.963882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:15:59.963867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:15:59.998667 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:15:59.998708 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:16:29.963955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:16:59.963934 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:17:00.023372 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:17:00.023432 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:17:29.963990 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:17:59.963874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:18:00.045671 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:18:00.045721 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:18:29.963875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:18:59.963889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:19:00.064602 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:19:00.064993 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:19:29.964088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:19:59.964003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:20:00.087028 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:20:00.087085 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:20:29.963918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:20:59.963929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:21:00.106379 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:21:00.106444 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:21:29.964048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:21:59.963944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:22:00.136869 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:22:00.136918 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:22:29.963905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:22:59.963961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 13:23:00.156041 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:23:00.156089 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 13:23:29.963988 metrics.go:34: INFO No non-zero metrics in the last 30s