By type
2022/03/11 03:06:05.939687 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/11 03:06:05.939790 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/11 03:06:05.939932 logstash.go:90: INFO Max Retries set to: 3
2022/03/11 03:06:05.940061 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/11 03:06:05.940291 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-7qbss
2022/03/11 03:06:05.940387 metrics.go:23: INFO Metrics logging every 30s
2022/03/11 03:06:05.940726 async.go:63: INFO Flush Interval set to: 1s
2022/03/11 03:06:05.940767 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/11 03:06:05.941564 beat.go:221: INFO filebeat start running.
2022/03/11 03:06:05.941671 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/11 03:06:05.953385 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/11 03:06:05.953489 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/11 03:06:05.953716 registrar.go:236: INFO Starting Registrar
2022/03/11 03:06:05.953913 crawler.go:38: INFO Loading Prospectors: 1
2022/03/11 03:06:05.953931 sync.go:41: INFO Start sending events to output
2022/03/11 03:06:05.954096 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/11 03:06:05.954409 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/11 03:06:05.954568 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/11 03:06:05.954618 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/11 03:06:35.941101 metrics.go:39: INFO Non-zero metrics in the last 30s: registrar.writes=1
2022/03/11 03:06:35.971360 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/11 03:06:35.971577 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/11 03:06:35.971978 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/11 03:06:35.972232 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/11 03:06:35.972331 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/11 03:06:40.997627 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:06:40.997699 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:06:42.003784 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:06:42.007056 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:06:44.013177 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:06:44.013230 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:06:48.022095 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:06:48.022130 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:06:56.045784 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:06:56.045881 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:07:05.940948 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=76
2022/03/11 03:07:12.079744 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:07:12.079809 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:07:35.940872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:07:44.113353 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:07:44.113491 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:08:05.941052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:08:35.941098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:08:44.157688 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:08:44.157753 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:09:05.940801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:09:35.940846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:09:44.181312 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:09:44.181379 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:10:05.940770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:10:35.940801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:10:44.220994 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:10:44.221177 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:11:05.940776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:11:35.940996 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:11:40.997377 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/11 03:11:44.266173 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:11:44.266229 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:12:05.943231 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/11 03:12:35.941448 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:12:44.293965 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:12:44.294019 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:13:05.940753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:13:35.940804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:13:44.319999 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:13:44.320040 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:14:05.940793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:14:35.944420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:14:44.340692 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:14:44.340745 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:15:05.941145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:15:35.940831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:15:44.366570 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:15:44.366620 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:16:05.943090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:16:35.941054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:16:44.390520 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:16:44.390583 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:17:05.941854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:17:35.940985 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:17:44.410622 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:17:44.410685 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:18:05.940757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:18:35.943568 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:18:44.456424 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:18:44.456490 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:19:05.940808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:19:35.940859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:19:44.479666 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:19:44.479762 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:20:05.941015 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:20:35.941142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:20:44.500806 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:20:44.500873 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:21:05.941234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:21:35.940787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:21:44.543798 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:21:44.543855 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:22:05.940928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:22:35.941605 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:22:44.570271 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:22:44.570390 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:23:05.940889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:23:35.940805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:23:44.595578 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:23:44.595919 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:24:05.940823 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:24:35.940842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:24:44.628561 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:24:44.628632 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:25:05.941162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:25:35.940953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:25:44.661453 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:25:44.661533 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:26:05.942079 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:26:35.942309 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:26:44.690777 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:26:44.690844 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:27:05.940870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:27:35.941133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:27:44.724012 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:27:44.724069 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:28:05.940849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:28:35.940967 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:28:44.755840 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:28:44.755894 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:29:05.940871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:29:35.941132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:29:44.779997 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:29:44.780058 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:30:05.941195 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:30:35.943370 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:30:44.805658 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:30:44.805754 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:31:05.941185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:31:35.940794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:31:44.830505 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:31:44.830591 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:32:05.940877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:32:35.940786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:32:44.853990 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:32:44.854063 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:33:05.940889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:33:35.940845 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:33:44.876657 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:33:44.876732 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:34:05.940750 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:34:35.941197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:34:44.904788 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:34:44.904844 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:35:05.942920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:35:35.940928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:35:44.930519 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:35:44.930595 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:36:05.940809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:36:35.941846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:36:44.956250 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:36:44.956302 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:37:05.941213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:37:35.940792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:37:44.980976 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:37:44.981095 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:38:05.940991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:38:35.940822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:38:45.003326 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:38:45.003384 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:39:05.940773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:39:35.940874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:39:45.024379 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:39:45.024446 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:40:05.941143 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:40:35.940996 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:40:45.049004 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:40:45.049097 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:41:05.940871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:41:35.940927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:41:45.071080 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:41:45.071140 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:42:05.941167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:42:35.940778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:42:45.094783 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:42:45.094822 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:43:05.940830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:43:35.940837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:43:45.114464 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:43:45.114522 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:44:05.940882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:44:35.941089 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:44:45.150800 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:44:45.150877 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:45:05.940795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:45:35.940789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:45:45.176630 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:45:45.176696 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:46:05.940841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:46:35.941121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:46:45.210742 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:46:45.210790 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:47:05.941624 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:47:35.940850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:47:45.235016 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:47:45.235067 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:05.940953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:48:35.941168 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:48:45.243491 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:45.243536 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:49:05.941186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:49:35.940980 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:49:45.273940 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:49:45.273998 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:50:05.940921 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:50:35.940817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:50:45.305818 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:50:45.305890 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:51:05.942944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:51:35.941143 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:51:45.327713 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:51:45.327791 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:52:05.940848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:52:35.940856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:52:45.349942 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:52:45.350010 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:53:05.940959 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:53:35.940838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:53:45.390238 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:53:45.390309 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:54:05.940780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:54:35.940908 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:54:45.411127 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:54:45.411183 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:55:05.940945 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:55:35.940750 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:55:45.470933 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:55:45.470995 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:56:05.941137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:56:35.941299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:56:45.493866 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:56:45.493926 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:57:05.941295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:57:35.940856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:57:45.518718 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:57:45.518785 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:58:05.940971 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:58:35.940919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:58:45.541495 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:58:45.541541 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:59:05.940901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:59:35.940862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:59:45.563009 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:59:45.563059 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:00:05.941047 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:00:35.940900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:00:45.595686 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:00:45.595744 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:01:05.940846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:01:35.940899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:01:45.620827 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:01:45.620874 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:02:05.941094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:02:35.940898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:02:45.640604 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:02:45.640660 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:03:05.941031 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:03:35.940806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:03:45.661316 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:03:45.661403 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:04:05.940821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:04:35.941745 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:04:45.692515 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:04:45.692579 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:05:05.941017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:05:35.940783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:05:45.751975 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:05:45.752021 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:06:05.944387 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:06:35.940927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:06:45.779014 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:06:45.779108 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:07:05.943901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:07:35.943233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:07:45.807878 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:07:45.807954 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:08:05.944243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:08:35.941187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:08:45.830116 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:08:45.830217 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:09:05.940735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:09:35.945886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:09:45.859955 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:09:45.859994 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:10:05.942028 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:10:35.940722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:10:45.883849 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:10:45.883910 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:11:05.940914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:11:35.941053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:11:45.904039 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:11:45.904091 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:12:05.941034 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:12:35.940824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:12:45.949335 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:12:45.949414 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:13:05.940747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:13:35.940826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:13:45.973929 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:13:45.973986 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:14:05.940869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:14:35.940956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:14:45.999331 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:14:45.999400 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:15:05.940829 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:15:35.940825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:15:46.020754 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:15:46.020817 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:16:05.940887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:16:35.941056 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:16:46.044300 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:16:46.044436 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:17:05.941356 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:17:35.940917 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:17:46.071844 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:17:46.071906 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:18:05.940843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:18:35.940945 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:18:46.098455 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:18:46.098523 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:19:05.940846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:19:35.940822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:19:46.120081 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:19:46.120139 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:20:05.940933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:20:35.940828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:20:46.146453 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:20:46.146513 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:21:05.941083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:21:35.940926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:21:46.170913 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:21:46.171129 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:22:05.940816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:22:35.940846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:22:46.197095 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:22:46.197151 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:23:05.940765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:23:35.940984 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:23:46.219370 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:23:46.219663 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:24:05.942948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:24:35.940849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:24:46.243430 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:24:46.243496 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:25:05.940838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:25:35.945562 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:25:46.266910 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:25:46.266956 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:26:05.940888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:26:35.940787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:26:46.306278 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:26:46.306353 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:27:05.940796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:27:35.940721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:27:46.335998 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:27:46.336059 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:28:05.940842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:28:35.940741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:28:46.358662 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:28:46.358761 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:29:05.940874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:29:35.941073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:29:46.385448 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:29:46.385529 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:30:05.941050 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:30:35.940830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:30:46.409144 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:30:46.409205 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:31:05.941795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:31:35.941076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:31:46.428286 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:31:46.428344 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:32:05.940856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:32:35.940812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:32:46.455481 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:32:46.455542 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host