By type
2022/02/18 02:50:51.228491 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/02/18 02:50:51.228545 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/02/18 02:50:51.228639 logstash.go:90: INFO Max Retries set to: 3
2022/02/18 02:50:51.228655 metrics.go:23: INFO Metrics logging every 30s
2022/02/18 02:50:51.228761 outputs.go:108: INFO Activated logstash as output plugin.
2022/02/18 02:50:51.228860 publish.go:295: INFO Publisher name: onap-portal-app-9c5c78dc6-cpnjq
2022/02/18 02:50:51.229035 async.go:63: INFO Flush Interval set to: 1s
2022/02/18 02:50:51.229053 async.go:64: INFO Max Bulk Size set to: 2048
2022/02/18 02:50:51.229554 beat.go:221: INFO filebeat start running.
2022/02/18 02:50:51.229643 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/02/18 02:50:51.557856 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/02/18 02:50:51.557956 registrar.go:123: INFO States Loaded from registrar: 0
2022/02/18 02:50:51.558053 crawler.go:38: INFO Loading Prospectors: 1
2022/02/18 02:50:51.558118 registrar.go:236: INFO Starting Registrar
2022/02/18 02:50:51.558209 sync.go:41: INFO Start sending events to output
2022/02/18 02:50:51.558242 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/02/18 02:50:51.558287 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/02/18 02:50:51.558412 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/02/18 02:50:51.558453 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/02/18 02:50:51.559283 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/02/18 02:50:51.559399 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/02/18 02:50:51.559492 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/02/18 02:50:51.559520 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/02/18 02:50:51.559668 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/02/18 02:50:51.604029 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:50:51.604064 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:50:52.609236 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:50:52.609282 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:50:54.613567 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:50:54.613604 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:50:58.622921 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:50:58.622957 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:51:06.631866 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:51:06.631910 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:51:21.229578 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=2043 registrar.writes=1
2022/02/18 02:51:22.642919 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:51:22.642964 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:51:51.229730 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 02:51:54.649707 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:51:54.649750 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:52:21.229149 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 02:52:51.229165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 02:52:54.658987 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:52:54.659026 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:53:21.229174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 02:53:51.229138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 02:53:54.671235 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:53:54.671297 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:54:21.229169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 02:54:51.229007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 02:54:54.681067 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:54:54.681115 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:55:21.229077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 02:55:51.229120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 02:55:54.689425 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:55:54.689486 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:55:56.571007 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/02/18 02:56:21.229216 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/02/18 02:56:51.229255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 02:56:54.700356 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:56:54.700406 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:57:21.229157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 02:57:51.229133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 02:57:54.708068 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:57:54.708165 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:58:21.229138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 02:58:51.229207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 02:58:54.730875 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:58:54.730916 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:59:21.229119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 02:59:51.229089 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 02:59:54.740016 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 02:59:54.740057 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:00:21.229120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:00:51.229064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:00:54.751860 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:00:54.751903 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:01:21.229134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:01:51.229133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:01:54.761320 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:01:54.761358 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:02:21.229033 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:02:51.229175 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:02:54.772938 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:02:54.772982 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:03:21.229165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:03:51.229114 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:03:54.782939 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:03:54.782985 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:04:21.229259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:04:51.229198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:04:54.804624 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:04:54.804657 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:05:21.229130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:05:51.229035 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:05:54.814538 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:05:54.814600 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:06:21.229162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:06:51.229160 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:06:54.840563 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:06:54.840593 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:07:21.229112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:07:51.229128 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:07:54.848722 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:07:54.848766 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:08:21.229188 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:08:51.229127 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:08:54.861612 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:08:54.861636 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:09:21.229044 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:09:51.229138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:09:54.871461 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:09:54.871512 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:10:21.229032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:10:51.229059 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:10:54.886818 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:10:54.886848 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:11:21.229160 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:11:51.229164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:11:54.895210 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:11:54.895259 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:12:21.229117 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:12:51.229144 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:12:54.906220 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:12:54.906271 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:13:21.229097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:13:51.229070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:13:54.918154 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:13:54.918183 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:14:21.229071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:14:51.229108 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:14:54.927496 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:14:54.927523 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:15:21.229109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:15:51.229184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:15:54.935950 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:15:54.935992 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:16:21.229085 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:16:51.229114 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:16:54.946855 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:16:54.946914 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:17:21.229249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:17:51.229196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:17:54.962787 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:17:54.962831 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:18:21.229126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:18:51.229125 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:18:54.977834 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:18:54.977874 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:19:21.229099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:19:51.229126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:19:54.987692 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:19:54.987743 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:20:21.229081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:20:51.229121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:20:55.002143 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:20:55.002188 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:21:21.229133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:21:51.229116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:21:55.011930 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:21:55.011964 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:22:21.229161 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:22:51.229124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:22:55.030218 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:22:55.030247 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:23:21.229001 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:23:51.229157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:23:55.039177 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:23:55.039226 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:24:21.229145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:24:51.229180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:24:55.054295 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:24:55.054329 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:25:21.229208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:25:51.229124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:25:55.062852 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:25:55.062890 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:26:21.229121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:26:51.229081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:26:55.076059 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:26:55.076175 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:27:21.229060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:27:51.229218 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:27:55.088194 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:27:55.088249 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:28:21.229122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:28:51.229219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:28:55.099056 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:28:55.099233 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:29:21.229302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:29:51.229239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:29:55.112397 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:29:55.112431 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:30:21.229205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:30:51.230783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:30:55.123470 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:30:55.123497 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:31:21.229151 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:31:51.229091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:31:55.131994 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:31:55.132032 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:32:21.229097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:32:51.229152 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:32:55.147017 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:32:55.147115 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:33:21.229632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:33:51.229147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:33:55.160494 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:33:55.160588 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:34:21.229132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:34:51.229884 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:34:55.173728 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:34:55.173755 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:35:21.228976 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:35:51.229112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:35:55.183318 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:35:55.183360 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:36:21.229043 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:36:51.229136 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:36:55.196126 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:36:55.196156 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:37:21.229108 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:37:51.229198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:37:55.204896 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:37:55.204951 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:38:21.229088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:38:51.229156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:38:55.215383 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:38:55.215420 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:39:21.229048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:39:51.229134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:39:55.224253 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:39:55.224308 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:40:21.229205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:40:51.229274 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:40:55.235226 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:40:55.235254 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:41:21.229222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:41:51.229113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:41:55.243438 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:41:55.243479 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:42:21.229070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:42:51.229195 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:42:55.252981 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:42:55.253023 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:43:21.229181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:43:51.229027 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:43:55.264235 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:43:55.264283 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:44:21.229025 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:44:51.229109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:44:55.274365 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:44:55.274387 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:45:21.229093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:45:51.229572 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:45:55.283345 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:45:55.283391 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:46:21.229197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:46:51.229335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:46:55.300806 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:46:55.300832 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:47:21.229179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:47:51.229173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:47:55.309820 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:47:55.309879 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:48:21.229180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:48:51.229143 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:48:55.320045 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:48:55.320072 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:49:21.229152 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:49:51.229134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:49:55.330840 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:49:55.330870 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:50:21.229221 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:50:51.229144 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:50:55.345849 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:50:55.345874 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:51:21.229072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:51:51.229184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:51:55.353146 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:51:55.353246 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:52:21.229124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:52:51.229167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/18 03:52:55.367261 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/18 03:52:55.367298 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host