By type
2022/03/10 14:47:24.699203 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/10 14:47:24.699293 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/10 14:47:24.699450 metrics.go:23: INFO Metrics logging every 30s
2022/03/10 14:47:24.699496 logstash.go:90: INFO Max Retries set to: 3
2022/03/10 14:47:24.699592 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/10 14:47:24.699729 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-x5s88
2022/03/10 14:47:24.700010 async.go:63: INFO Flush Interval set to: 1s
2022/03/10 14:47:24.700033 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/10 14:47:24.700586 beat.go:221: INFO filebeat start running.
2022/03/10 14:47:24.700662 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/10 14:47:24.705228 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/10 14:47:24.705380 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/10 14:47:24.705453 crawler.go:38: INFO Loading Prospectors: 1
2022/03/10 14:47:24.705507 registrar.go:236: INFO Starting Registrar
2022/03/10 14:47:24.705713 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/10 14:47:24.705734 sync.go:41: INFO Start sending events to output
2022/03/10 14:47:24.705887 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/10 14:47:24.706189 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/10 14:47:24.706246 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/10 14:47:44.708978 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/10 14:47:44.709328 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/10 14:47:44.709497 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/10 14:47:44.709576 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/10 14:47:44.709674 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/10 14:47:49.735245 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:47:49.735298 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:47:50.741879 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:47:50.741937 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:47:52.751239 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:47:52.751365 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:47:54.700649 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/10 14:47:56.759052 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:47:56.759151 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:48:04.767495 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:48:04.767672 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:48:20.784365 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:48:20.784647 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:48:24.699958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:48:52.804457 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:48:52.804500 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:48:54.699811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:49:24.699898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:49:52.825763 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:49:52.825829 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:49:54.700140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:50:24.699773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:50:52.846212 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:50:52.846260 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:50:54.699784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:51:24.699843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:51:52.867755 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:51:52.867878 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:51:54.699814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:52:24.699827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:52:49.721020 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/10 14:52:49.721012 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/10 14:52:49.721039 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/10 14:52:49.721230 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/10 14:52:52.889338 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:52:52.889393 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:52:54.699851 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/10 14:52:59.727401 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/03/10 14:53:24.699790 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/10 14:53:52.908907 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:53:52.908963 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:53:54.699814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:54:24.699993 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:54:52.927099 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:54:52.927138 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:54:54.699804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:55:24.699843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:55:52.949610 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:55:52.949669 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:55:54.699859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:56:24.699812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:56:52.969041 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:56:52.969108 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:56:54.699822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:57:24.699805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:57:52.987348 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:57:52.987391 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:57:54.699868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:58:24.699728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:58:53.007194 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:58:53.007268 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:58:54.699949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:59:24.699747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:59:53.039074 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:59:53.039145 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:59:54.705393 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:00:24.699790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:00:53.058006 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:00:53.058066 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:00:54.699828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:01:24.700429 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:01:53.086857 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:01:53.086905 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:01:54.702774 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:02:24.699832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:02:53.105410 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:02:53.105456 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:02:54.699846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:03:24.699874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:03:53.124329 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:03:53.124372 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:03:54.699848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:04:24.700190 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:04:53.141792 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:04:53.141856 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:04:54.699763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:05:24.700052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:05:53.162277 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:05:53.162332 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:05:54.699794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:06:24.699926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:06:53.179361 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:06:53.179412 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:06:54.699784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:07:24.700001 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:07:53.198646 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:07:53.198690 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:07:54.699844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:08:24.700031 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:08:53.220283 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:08:53.220322 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:08:54.699922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:09:24.699927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:09:53.238941 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:09:53.238998 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:09:54.700160 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:10:24.699798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:10:53.259094 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:10:53.259152 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:10:54.699799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:11:24.699768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:11:53.278763 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:11:53.278817 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:11:54.699795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:12:24.699757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:12:53.297769 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:12:53.297810 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:12:54.699852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:13:24.700093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:13:53.320488 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:13:53.320541 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:13:54.699845 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:14:24.699845 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:14:53.339058 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:14:53.339209 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:14:54.699876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:15:24.699822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:15:53.360055 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:15:53.360126 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:15:54.699890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:16:24.699745 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:16:53.379359 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:16:53.379401 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:16:54.699828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:17:24.699787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:17:53.399013 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:17:53.399058 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:17:54.699806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:18:24.700058 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:18:53.431191 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:18:53.431244 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:18:54.699815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:19:24.699776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:19:53.449835 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:19:53.449877 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:19:54.699737 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:20:24.699840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:20:53.468803 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:20:53.468857 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:20:54.699749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:21:24.699852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:21:53.488379 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:21:53.488431 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:21:54.699800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:22:24.699910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:22:53.510220 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:22:53.510260 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:22:54.699789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:23:24.699784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:23:53.530050 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:23:53.530104 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:23:54.699790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:24:24.699888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:24:53.549046 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:24:53.549112 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:24:54.699882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:25:24.699808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:25:53.568586 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:25:53.568698 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:25:54.699808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:26:24.699858 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:26:53.588184 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:26:53.588237 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:26:54.699760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:27:24.699848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:27:53.591620 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:27:53.591678 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:27:54.699838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:28:24.700045 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:28:53.599726 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:28:53.599761 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:28:54.699788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:29:24.699830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:29:53.607564 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:29:53.607616 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:29:54.699882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:30:24.699818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:30:53.614699 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:30:53.614833 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:30:54.699786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:31:24.699930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:31:53.621934 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:31:53.621987 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:31:54.699838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:32:24.699938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:32:53.630658 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:32:53.630724 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:32:54.699879 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:33:24.700138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:33:53.637996 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:33:53.638052 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:33:54.699775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:34:24.699838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:34:53.645545 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:34:53.645593 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:34:54.699889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:35:24.699860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:35:53.654682 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:35:53.654857 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:35:54.699789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:36:24.699806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:36:53.662531 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:36:53.662593 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:36:54.699958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:37:24.699802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:37:53.669496 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:37:53.669839 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:37:54.699879 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:38:24.699788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:38:53.676914 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:38:53.676966 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:38:54.699766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:39:24.699866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:39:53.684359 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:39:53.684406 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:39:54.699868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:40:24.699750 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:40:53.691463 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:40:53.691499 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:40:54.699918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:41:24.700328 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:41:53.699539 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:41:53.699947 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:41:54.699812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:42:24.699813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:42:53.707579 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:42:53.707628 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:42:54.699865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:43:24.699862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:43:53.715112 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:43:53.715160 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:43:54.699801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:44:24.699870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:44:53.722772 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:44:53.723120 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:44:54.699738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:45:24.700193 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:45:53.730775 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:45:53.730823 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:45:54.699774 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:46:24.699775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:46:53.737614 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:46:53.737651 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:46:54.699886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:47:24.699791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:47:53.745357 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:47:53.745406 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:47:54.699782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:48:24.699861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:48:53.757397 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:48:53.757436 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:48:54.699843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:49:24.699797 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:49:53.763633 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:49:53.763687 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:49:54.699831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:50:24.700046 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:50:53.771962 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:50:53.771999 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:50:54.699839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:51:24.700014 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:51:53.779249 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:51:53.779281 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:51:54.699919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:52:24.699838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:52:53.806952 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:52:53.807004 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:52:54.699882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:53:24.699870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:53:53.815183 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:53:53.815365 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:53:54.699763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:54:24.699822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:54:53.822775 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:54:53.822827 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:54:54.699956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:55:24.699738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:55:53.830842 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:55:53.830879 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:55:54.699788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:56:24.699875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:56:53.839017 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:56:53.839062 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:56:54.699830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:57:24.699743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:57:53.848877 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:57:53.848915 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:57:54.699898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:58:24.699863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:58:53.856714 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:58:53.856792 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:58:54.699810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:59:24.699864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:59:53.864470 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:59:53.864533 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:59:54.700224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:00:24.699765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:00:53.873303 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:00:53.873369 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:00:54.699724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:01:24.699765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:01:53.881185 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:01:53.881235 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:01:54.699849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:02:24.699826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:02:53.889066 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:02:53.889109 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:02:54.699890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:03:24.699925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:03:53.895627 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:03:53.895678 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:03:54.699796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:04:24.700336 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:04:53.903237 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:04:53.903471 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:04:54.699920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:05:24.699819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:05:53.912210 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:05:53.912298 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:05:54.699940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:06:24.699735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:06:53.920272 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:06:53.920317 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:06:54.699841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:07:24.699855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:07:53.927758 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:07:53.927804 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:07:54.699943 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:08:24.699794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:08:53.936618 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:08:53.936681 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:08:54.699853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:09:24.699828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:09:53.944307 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:09:53.944355 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:09:54.699903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:10:24.699754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:10:53.953925 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:10:53.953989 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:10:54.699862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:11:24.699801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:11:53.961971 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:11:53.962013 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:11:54.699773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:12:24.699764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:12:53.972520 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:12:53.972551 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:12:54.699828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:13:24.699767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:13:53.979172 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:13:53.979212 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:13:54.699787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:14:24.699883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:14:53.988116 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:14:53.988285 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:14:54.699768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:15:24.699793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:15:54.003319 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:15:54.003409 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:15:54.699768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:16:24.699844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:16:54.011699 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:16:54.011750 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:16:54.699767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:17:24.699814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:17:54.019073 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:17:54.019157 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:17:54.699813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:18:24.699850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:18:54.026252 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:18:54.026417 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:18:54.699748 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:19:24.699804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 16:19:54.034403 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:19:54.034507 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 16:19:54.699870 metrics.go:34: INFO No non-zero metrics in the last 30s