By type
2022/03/25 03:03:32.630834 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/25 03:03:32.630918 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/25 03:03:32.631100 logstash.go:90: INFO Max Retries set to: 3
2022/03/25 03:03:32.631295 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/25 03:03:32.631431 metrics.go:23: INFO Metrics logging every 30s
2022/03/25 03:03:32.631501 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-m645v
2022/03/25 03:03:32.631800 async.go:63: INFO Flush Interval set to: 1s
2022/03/25 03:03:32.631832 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/25 03:03:32.632338 beat.go:221: INFO filebeat start running.
2022/03/25 03:03:32.632415 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/25 03:03:32.638740 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/25 03:03:32.638820 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/25 03:03:32.638859 crawler.go:38: INFO Loading Prospectors: 1
2022/03/25 03:03:32.639002 registrar.go:236: INFO Starting Registrar
2022/03/25 03:03:32.639076 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/25 03:03:32.639070 sync.go:41: INFO Start sending events to output
2022/03/25 03:03:32.639246 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/25 03:03:32.639342 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/25 03:03:32.639280 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/25 03:03:52.641847 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/25 03:03:52.642010 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/25 03:03:52.642365 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/25 03:03:52.642475 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/25 03:03:52.642637 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/25 03:03:52.664140 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:03:52.664189 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:03:53.669009 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:03:53.669054 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:03:55.673885 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:03:55.674140 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:03:59.687781 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:03:59.687824 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:04:02.632082 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=63 registrar.writes=1
2022/03/25 03:04:07.701627 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:04:07.701666 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:04:23.727076 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:04:23.727154 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:04:32.631766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:04:55.745084 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:04:55.745162 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:05:02.631838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:05:32.633622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:05:55.765224 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:05:55.765270 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:06:02.633113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:06:32.631888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:06:55.784138 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:06:55.784190 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:07:02.631814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:07:32.631798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:07:55.806392 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:07:55.806451 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:08:02.631738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:08:32.631735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:08:55.825605 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:08:55.825651 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:08:57.657076 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/25 03:09:02.631869 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/25 03:09:32.631831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:09:55.845063 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:09:55.845125 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:10:02.631848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:10:32.631797 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:10:55.864727 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:10:55.864775 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:11:02.631762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:11:32.632068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:11:55.883040 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:11:55.883107 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:12:02.631753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:12:32.631683 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:12:57.903666 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:12:57.903718 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:13:02.631749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:13:32.631754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:13:57.921829 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:13:57.921870 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:14:02.631812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:14:32.631794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:14:57.940918 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:14:57.940970 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:15:02.631826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:15:32.632254 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:15:57.959040 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:15:57.959092 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:16:02.632299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:16:32.631744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:16:57.978184 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:16:57.978234 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:17:02.635384 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:17:32.635345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:17:57.995771 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:17:57.995815 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:18:02.631715 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:18:32.631879 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:18:58.015226 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:18:58.015709 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:19:02.631777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:19:32.631810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:19:58.035351 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:19:58.035412 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:20:02.631729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:20:32.631725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:20:58.054415 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:20:58.054463 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:21:02.631812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:21:32.631812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:21:58.073874 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:21:58.073932 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:22:02.631961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:22:32.631790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:22:58.093456 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:22:58.093496 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:23:02.631806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:23:32.631866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:23:58.113960 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:23:58.114019 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:24:02.631787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:24:32.632410 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:24:58.137028 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:24:58.137090 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:25:02.631761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:25:32.631958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:25:58.159074 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:25:58.159179 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:26:02.631781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:26:32.631778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:26:58.180879 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:26:58.181130 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:27:02.631810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:27:32.631904 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:27:58.201855 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:27:58.201902 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:28:02.631845 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:28:32.631866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:28:58.220144 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:28:58.220230 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:29:02.631778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:29:32.631724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:29:58.242051 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:29:58.242095 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:30:02.631781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:30:32.631854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:30:58.260197 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:30:58.260236 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:31:02.631798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:31:32.631763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:31:58.281339 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:31:58.281395 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:32:02.631818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:32:32.631823 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:32:58.301591 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:32:58.301783 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:33:02.631800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:33:32.631793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:33:58.320399 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:33:58.320441 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:34:02.631724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:34:32.631712 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:34:58.339691 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:34:58.339845 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:35:02.631766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:35:32.631727 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:35:58.367651 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:35:58.367713 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:36:02.631747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:36:32.632568 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:36:58.387066 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:36:58.387107 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:37:02.631803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:37:32.631819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:37:58.404710 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:37:58.404764 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:38:02.631756 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:38:32.631754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:38:58.424472 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:38:58.424529 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:39:02.631783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:39:32.631888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:39:58.442277 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:39:58.442315 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:40:02.631846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:40:32.631748 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:40:58.460468 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:40:58.460508 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:41:02.631819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:41:32.631812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:41:58.479904 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:41:58.479976 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:42:02.631821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:42:32.631739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:42:58.497951 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:42:58.498018 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:43:02.631773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:43:32.631748 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:43:58.516415 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:43:58.516528 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:44:02.631778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:44:32.631772 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:44:58.536123 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:44:58.536178 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:45:02.631739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:45:32.632042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:45:58.562479 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:45:58.562531 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:46:02.631823 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:46:32.631712 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:46:58.570719 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:46:58.570756 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:47:02.631770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:47:32.631819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:47:58.593109 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:47:58.593170 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:48:02.631745 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:48:32.635531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:48:58.611524 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:48:58.611593 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:49:02.631732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:49:32.631780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:49:58.638754 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:49:58.638815 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:50:02.631832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:50:32.631790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:50:58.657700 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:50:58.657753 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:51:02.631778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:51:32.631782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:51:58.674565 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:51:58.674630 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:52:02.631797 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:52:32.632028 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:52:58.696317 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:52:58.696365 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:53:02.631796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:53:32.631743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:53:58.715577 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:53:58.715630 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:54:02.631733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:54:32.631868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:54:58.734206 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:54:58.734255 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:55:02.631753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:55:32.631800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:55:58.752630 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:55:58.752683 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:56:02.631831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:56:32.631886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:56:58.771352 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:56:58.771410 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:57:02.631829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:57:32.631806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:57:58.791515 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:57:58.791575 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:58:02.631775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:58:32.631952 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:58:58.815471 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:58:58.815525 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:59:02.631729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:59:32.631918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:59:58.836277 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:59:58.836322 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:00:02.632255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:00:32.631762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:00:58.857144 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:00:58.857208 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:01:02.631898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:01:32.631817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:01:58.875594 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:01:58.875662 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:02:02.634366 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:02:32.631802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:02:58.894588 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:02:58.894633 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:03:02.631724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:03:32.631793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:03:58.914175 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:03:58.914231 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:04:02.631780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:04:32.631931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:04:58.935231 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:04:58.935411 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:05:02.631848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:05:32.631832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:05:58.973675 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:05:58.973733 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:06:02.631848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:06:32.631896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:06:58.992336 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:06:58.992390 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:07:02.631790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:07:32.631888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:07:59.012398 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:07:59.012510 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:08:02.631737 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:08:32.631938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:08:59.030306 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:08:59.030351 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:09:02.632000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:09:32.631782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:09:59.050806 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:09:59.050861 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:10:02.631787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:10:32.631795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:10:59.071777 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:10:59.071832 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:11:02.631698 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:11:32.631832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:11:59.090334 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:11:59.090387 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:12:02.631807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:12:32.631828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:12:59.117552 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:12:59.117588 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:13:02.631825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:13:32.631796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:13:59.135526 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:13:59.135579 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:14:02.631741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:14:32.632825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:14:59.154988 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:14:59.155089 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:15:02.631739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:15:32.631817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:15:59.183091 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:15:59.183256 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:16:02.631758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:16:32.631755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:16:59.204549 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:16:59.204708 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:17:02.631683 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:17:32.631760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:17:59.224651 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:17:59.224714 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:18:02.631782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:18:32.632044 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:18:59.246184 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:18:59.246225 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:19:02.631751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:19:32.631836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:19:59.265405 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:19:59.265445 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:20:02.631822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:20:32.631782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:20:59.286236 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:20:59.286282 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:21:02.631757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:21:32.631746 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:21:59.306802 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:21:59.306846 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:22:02.631802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:22:32.631748 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:22:59.327860 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:22:59.327923 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:23:02.631793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:23:32.631805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:23:59.346493 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:23:59.346539 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:24:02.631741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:24:32.631849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:24:59.366914 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:24:59.366962 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:25:02.631773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:25:32.631843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:25:59.391927 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:25:59.391993 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:26:02.631799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:26:32.631808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:26:59.415678 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:26:59.415732 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:27:02.631761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:27:32.631726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:27:59.434527 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:27:59.434583 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:28:02.631818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:28:32.631873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:28:59.453685 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:28:59.453750 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:29:02.631723 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:29:32.631965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:29:59.474069 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:29:59.474117 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:30:02.631807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:30:32.631887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:30:59.495453 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:30:59.495513 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:31:02.631795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:31:32.631745 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:31:59.516196 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:31:59.516246 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:32:02.631750 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:32:32.631832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:32:59.535815 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:32:59.536645 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:33:02.631844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:33:32.631776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:33:59.566524 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:33:59.566562 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:34:02.631876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:34:32.631863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:34:59.594813 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:34:59.594862 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:35:02.631774 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:35:32.631798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:35:59.613517 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:35:59.613557 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:36:02.635579 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:36:32.631818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:36:59.633161 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:36:59.633203 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:37:02.631794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:37:32.631778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:37:59.651304 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:37:59.651348 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:38:02.631766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:38:32.631809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:38:59.671728 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:38:59.671763 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:39:02.631896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:39:32.631728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:39:59.693855 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:39:59.693911 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:40:02.631735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:40:32.631792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:40:59.714515 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:40:59.714559 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:41:02.631913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:41:32.631734 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:41:59.733435 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:41:59.733472 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 04:42:02.631771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 04:42:32.631900 metrics.go:34: INFO No non-zero metrics in the last 30s