2022/04/02 03:26:30.477841 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/04/02 03:26:30.477896 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/04/02 03:26:30.478001 metrics.go:23: INFO Metrics logging every 30s
2022/04/02 03:26:30.478010 logstash.go:90: INFO Max Retries set to: 3
2022/04/02 03:26:30.478118 outputs.go:108: INFO Activated logstash as output plugin.
2022/04/02 03:26:30.478628 publish.go:295: INFO Publisher name: onap-vfc-generic-vnfm-driver-757795dcf7-tbzfj
2022/04/02 03:26:30.478852 async.go:63: INFO Flush Interval set to: 1s
2022/04/02 03:26:30.478870 async.go:64: INFO Max Bulk Size set to: 2048
2022/04/02 03:26:30.479961 beat.go:221: INFO filebeat start running.
2022/04/02 03:26:30.480043 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/04/02 03:26:30.483617 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/04/02 03:26:30.483699 registrar.go:123: INFO States Loaded from registrar: 0
2022/04/02 03:26:30.483737 crawler.go:38: INFO Loading Prospectors: 1
2022/04/02 03:26:30.483752 registrar.go:236: INFO Starting Registrar
2022/04/02 03:26:30.483827 sync.go:41: INFO Start sending events to output
2022/04/02 03:26:30.483889 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/04/02 03:26:30.483921 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/04/02 03:26:30.484010 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/04/02 03:26:30.484044 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/04/02 03:26:30.484864 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfmdriver/runtime_gvnfmdriver.log
2022/04/02 03:27:00.478491 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=1 filebeat.harvester.running=1 filebeat.harvester.started=1 publish.events=1 registrar.states.current=1 registrar.states.update=1 registrar.writes=2
2022/04/02 03:27:30.478333 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:28:00.478310 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:28:30.478446 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:29:00.478502 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:29:30.478401 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:30:00.478467 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:30:30.478468 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:31:00.478380 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:31:30.478446 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:31:35.497260 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfmdriver/runtime_gvnfmdriver.log. Closing because close_inactive of 5m0s reached.
2022/04/02 03:32:00.478391 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=1 filebeat.harvester.open_files=-1 filebeat.harvester.running=-1 publish.events=1 registrar.states.update=1 registrar.writes=1
2022/04/02 03:32:30.478367 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:33:00.478394 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:33:30.478394 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:34:00.478392 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:34:30.478324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:35:00.478321 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:35:30.478406 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:36:00.478365 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:36:30.478516 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:37:00.478432 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:37:30.478314 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:38:00.478299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:38:30.482479 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:39:00.478618 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:39:30.478458 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:40:00.478488 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:40:30.478313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:41:00.478298 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:41:30.478311 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:42:00.478302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:42:30.478424 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:43:00.478293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:43:30.478269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:44:00.478242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:44:30.480903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:45:00.478456 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:45:30.478713 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:46:00.478251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:46:30.478355 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:47:00.478334 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:47:30.478746 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:48:00.478294 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:48:30.478426 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:49:00.478742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:49:30.478268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:50:00.478256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:50:30.478478 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:51:00.478313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:51:30.478376 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:52:00.478307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:52:30.478333 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:53:00.478522 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:53:30.479262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:54:00.479002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:54:10.639965 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfmdriver/runtime_gvnfmdriver.log
2022/04/02 03:54:15.610521 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:15.610584 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:16.613837 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:16.613869 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:18.617867 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:18.617909 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:22.624835 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:22.624902 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:30.479270 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=1 filebeat.harvester.running=1 filebeat.harvester.started=1 libbeat.publisher.published_events=1
2022/04/02 03:54:30.631257 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:30.631296 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:46.649257 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:54:46.649296 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:55:00.478435 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:55:18.668147 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:55:18.668221 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:55:30.478299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:56:00.478403 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:56:18.686361 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:56:18.686404 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:56:30.478380 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:57:00.478424 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:57:18.702424 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:57:18.702457 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:57:30.478300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:58:00.478360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:58:18.718051 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:58:18.718109 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:58:30.478356 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:59:00.478302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:59:15.650998 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfmdriver/runtime_gvnfmdriver.log. Closing because close_inactive of 5m0s reached.
2022/04/02 03:59:18.734527 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:59:18.734572 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 03:59:30.478318 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=1 filebeat.harvester.open_files=-1 filebeat.harvester.running=-1
2022/04/02 04:00:00.479300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:00:18.750800 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:00:18.750859 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:00:30.478457 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:01:00.478327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:01:18.770543 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:01:18.770577 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:01:30.478282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:02:00.478836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:02:18.790999 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:02:18.791047 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:02:30.478369 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:03:00.478268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:03:18.810631 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:03:18.810678 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:03:30.478396 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:04:00.478442 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:04:18.829716 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:04:18.829772 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:04:30.478270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:05:00.478344 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:05:18.850196 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:05:18.850233 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:05:30.478334 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:06:00.478261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:06:18.868484 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:06:18.868532 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:06:30.478368 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:07:00.478634 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:07:18.889158 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:07:18.889222 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:07:30.478254 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:08:00.478338 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:08:18.909655 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:08:18.909693 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:08:30.478317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:09:00.478251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:09:18.928341 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:09:18.928381 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:09:30.482576 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:10:00.478504 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:10:18.946208 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:10:18.946260 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:10:30.478335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:11:00.478294 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:11:18.965885 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:11:18.965935 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:11:30.478284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:12:00.478331 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:12:18.984649 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:12:18.984703 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:12:30.478263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:13:00.478300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:13:19.002143 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:13:19.002205 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:13:30.483042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:14:00.478585 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:14:19.024762 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:14:19.024811 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:14:30.478279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:15:00.478307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:15:19.042472 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:15:19.042520 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:15:30.478320 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:16:00.478365 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:16:19.060804 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:16:19.060854 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:16:30.483462 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:17:00.478374 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:17:19.081161 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:17:19.081202 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:17:30.478340 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:18:00.478451 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:18:19.113679 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:18:19.113719 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:18:30.478340 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:19:00.478331 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:19:19.135591 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:19:19.135626 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:19:30.478509 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:20:00.478398 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:20:19.152174 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:20:19.152233 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:20:30.478346 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:21:00.478413 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:21:19.172556 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:21:19.172610 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:21:30.478355 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:22:00.478365 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:22:19.190580 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:22:19.190623 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:22:30.478271 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:23:00.478315 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:23:19.210337 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:23:19.210397 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:23:30.478832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:24:00.478321 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:24:19.229432 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:24:19.229484 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:24:30.478266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:25:00.478306 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:25:19.250113 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:25:19.250161 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:25:30.478300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:26:00.478310 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:26:19.272981 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:26:19.273028 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:26:30.478321 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:27:00.478279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:27:19.292531 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:27:19.292570 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:27:30.480579 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:28:00.478246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:28:19.310868 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:28:19.311159 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:28:30.478300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:29:00.478375 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:29:19.330490 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:29:19.330540 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:29:30.478450 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:30:00.478333 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:30:19.349161 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:30:19.349199 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:30:30.478330 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:31:00.480198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:31:19.368665 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:31:19.368724 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:31:30.478264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:32:00.478325 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:32:19.394567 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:32:19.394604 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:32:30.478328 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:33:00.478335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:33:19.414853 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:33:19.415031 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:33:30.478345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:34:00.478284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:34:19.432699 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:34:19.432846 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:34:30.478350 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:35:00.478313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:35:19.449322 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:35:19.449557 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:35:30.478264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:36:00.478486 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:36:19.467789 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:36:19.467827 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:36:30.478402 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:37:00.478295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:37:19.488004 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:37:19.488175 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:37:30.479625 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:38:00.478313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:38:19.512024 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:38:19.512100 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:38:30.479132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:39:00.478577 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:39:19.531538 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:39:19.531578 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:39:30.478253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:40:00.478233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:40:19.551009 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:40:19.551059 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:40:30.478325 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:41:00.478353 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:41:19.568039 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:41:19.568129 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:41:30.478373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:42:00.478716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:42:19.584262 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:42:19.584302 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:42:30.478345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:43:00.478263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:43:19.601605 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:43:19.601635 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:43:30.479657 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:44:00.478297 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:44:19.618550 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:44:19.618587 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:44:30.478338 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:45:00.478711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:45:19.634797 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:45:19.634835 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:45:30.478532 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:46:00.478303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:46:19.652856 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:46:19.652898 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:46:30.478340 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:47:00.478278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:47:19.670792 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:47:19.670834 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:47:30.478416 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:48:00.478274 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:48:19.690125 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:48:19.690163 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:48:30.478329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:49:00.502753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:49:19.709345 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:49:19.709382 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:49:30.478263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:50:00.478273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:50:19.727475 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:50:19.727518 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:50:30.478315 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:51:00.478321 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:51:19.746327 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:51:19.746364 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:51:30.478311 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:52:00.478369 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:52:19.764023 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:52:19.764173 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:52:30.478286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:53:00.478278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:53:19.783948 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:53:19.784036 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:53:30.478321 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:54:00.478247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:54:19.805928 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:54:19.805989 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:54:30.479372 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:55:00.478327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:55:19.825319 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:55:19.825352 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:55:30.478280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:56:00.478263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:56:19.844813 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:56:19.844860 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:56:30.478308 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:57:00.478283 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:57:19.863221 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:57:19.863263 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:57:30.478345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:58:00.478341 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:58:19.880833 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:58:19.880954 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:58:30.478376 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:59:00.478362 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:59:19.899442 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:59:19.899482 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 04:59:30.478406 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:00:00.478496 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:00:19.916705 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:00:19.916739 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:00:30.478332 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:01:00.478278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:01:19.936845 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:01:19.936900 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:01:30.478412 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:02:00.478272 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:02:19.955064 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:02:19.955098 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:02:30.478350 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:03:00.478288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:03:19.973970 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:03:19.974128 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:03:30.479610 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:04:00.478291 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:04:19.992734 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:04:19.992799 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:04:30.478276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:05:00.478501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:05:20.012518 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:05:20.012557 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:05:30.478328 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:06:00.478261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:06:20.030516 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:06:20.030646 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:06:30.478243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:07:00.478309 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:07:20.048651 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:07:20.048726 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:07:30.481807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:08:00.478304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:08:20.068203 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:08:20.068244 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:08:30.478413 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:09:00.478249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:09:20.085917 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:09:20.085966 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:09:30.478308 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:10:00.478329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:10:20.105771 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:10:20.105839 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:10:30.479386 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:11:00.479712 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:11:20.127493 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:11:20.127528 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:11:30.478309 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:12:00.478262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:12:20.147062 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:12:20.147130 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:12:30.478376 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:13:00.478483 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:13:20.166969 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:13:20.167019 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:13:30.478406 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:14:00.478259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:14:20.187972 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:14:20.188011 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:14:30.478358 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:15:00.478280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:15:20.206455 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:15:20.206494 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:15:30.478370 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:16:00.478337 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:16:20.235151 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:16:20.235200 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:16:30.478388 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:17:00.478325 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:17:20.255128 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:17:20.255201 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:17:30.478315 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:18:00.478262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:18:20.276038 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:18:20.276075 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:18:30.478286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:19:00.478241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:19:20.290514 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:19:20.290540 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:19:30.478274 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:20:00.478706 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:20:20.309412 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:20:20.309450 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:20:30.480038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:21:00.478355 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:21:20.330880 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:21:20.330917 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:21:30.478365 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:22:00.478313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:22:20.348277 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:22:20.348483 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:22:30.478302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:23:00.478344 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:23:20.376389 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:23:20.376428 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:23:30.478304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:24:00.478362 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:24:20.393760 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:24:20.393800 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:24:30.478440 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:25:00.478403 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:25:20.412523 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:25:20.412561 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:25:30.478254 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:26:00.478362 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:26:20.429491 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:26:20.429518 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:26:30.478429 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:27:00.478375 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:27:20.447531 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:27:20.447582 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:27:30.478284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:28:00.478522 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:28:20.465309 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:28:20.465488 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:28:30.478282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:29:00.479267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:29:20.485775 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:29:20.485891 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:29:30.478748 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:30:00.478345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:30:20.504798 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:30:20.504828 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:30:30.478276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:31:00.479556 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:31:20.522072 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:31:20.522114 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:31:30.478289 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:32:00.478932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:32:20.539711 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:32:20.539756 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:32:30.478359 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:33:00.478363 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:33:20.559396 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:33:20.559424 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:33:30.478769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:34:00.478516 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:34:20.581402 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:34:20.581436 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:34:30.478771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:35:00.478328 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:35:20.601083 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:35:20.601123 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:35:30.478361 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:36:00.478496 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:36:20.621074 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:36:20.621104 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:36:30.478339 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:37:00.478407 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:37:20.638660 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:37:20.638699 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:37:30.478350 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:38:00.478353 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:38:20.656804 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:38:20.656862 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:38:30.478364 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:39:00.478397 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:39:20.676077 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:39:20.676139 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:39:30.478288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:40:00.478297 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:40:20.694514 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:40:20.694548 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:40:30.478296 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:41:00.478327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:41:20.714699 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:41:20.714727 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:41:30.478296 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:42:00.478323 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:42:20.738586 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:42:20.738616 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:42:30.478409 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:43:00.478531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:43:20.759330 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:43:20.759382 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:43:30.478702 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:44:00.478259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:44:20.780260 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:44:20.780448 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:44:30.478335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:45:00.478328 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:45:20.802246 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:45:20.802302 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:45:30.478325 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:46:00.478369 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:46:20.819844 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:46:20.820047 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:46:30.478327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:47:00.478352 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:47:20.842265 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:47:20.842306 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:47:30.478240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:48:00.478371 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:48:20.863219 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:48:20.863257 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:48:30.478354 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:49:00.478452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:49:20.881181 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:49:20.881214 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:49:30.478301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:50:00.478476 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:50:20.902909 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:50:20.902965 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:50:30.478218 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:51:00.478300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:51:20.918937 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:51:20.918985 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:51:30.479250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:52:00.478355 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:52:20.937611 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:52:20.937649 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/02 05:52:30.478318 metrics.go:34: INFO No non-zero metrics in the last 30s