2022/04/02 03:27:11.012367 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:27:11.012415 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/04/02 03:27:11.012493 logstash.go:90: INFO Max Retries set to: 3
2022/04/02 03:27:11.012550 outputs.go:108: INFO Activated logstash as output plugin.
2022/04/02 03:27:11.012674 publish.go:295: INFO Publisher name: onap-vfc-vnfmgr-8594ffd488-hklvx
2022/04/02 03:27:11.012924 metrics.go:23: INFO Metrics logging every 30s
2022/04/02 03:27:11.012994 async.go:63: INFO Flush Interval set to: 1s
2022/04/02 03:27:11.013207 async.go:64: INFO Max Bulk Size set to: 2048
2022/04/02 03:27:11.013875 beat.go:221: INFO filebeat start running.
2022/04/02 03:27:11.013952 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/04/02 03:27:11.049020 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/04/02 03:27:11.049115 registrar.go:123: INFO States Loaded from registrar: 0
2022/04/02 03:27:11.049157 crawler.go:38: INFO Loading Prospectors: 1
2022/04/02 03:27:11.049189 registrar.go:236: INFO Starting Registrar
2022/04/02 03:27:11.049261 sync.go:41: INFO Start sending events to output
2022/04/02 03:27:11.049403 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/04/02 03:27:11.049407 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/04/02 03:27:11.049618 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/04/02 03:27:11.049665 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/04/02 03:27:11.050700 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnfmgr/runtime_mgr.log
2022/04/02 03:27:41.013416 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:28:11.013403 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:28:41.013615 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:29:11.013459 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:29:41.013388 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:30:11.013496 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:30:41.013488 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:31:11.013372 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:31:41.013695 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:32:11.013390 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:32:16.060523 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfm-vnfmgr/runtime_mgr.log. Closing because close_inactive of 5m0s reached.
2022/04/02 03:32:41.013568 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:33:11.013441 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:33:41.013404 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:34:11.013437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:34:41.017101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:35:11.014882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:35:41.013450 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:36:11.013379 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:36:41.013575 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:37:11.013452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:37:41.013453 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:38:11.013524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:38:41.013441 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:39:11.013429 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:39:41.013617 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:40:11.013397 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:40:41.013527 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:41:11.013405 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:41:41.013362 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:42:11.013630 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:42:41.013547 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:43:11.013393 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:43:41.013506 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:44:11.013556 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:44:41.013502 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:45:11.013642 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:45:41.013395 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:46:11.013484 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:46:41.013491 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:47:11.013440 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:47:41.013408 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:48:11.013447 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:48:41.013382 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:49:11.013472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:49:41.013383 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:50:11.013703 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:50:41.013500 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:51:11.013559 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:51:41.013495 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:52:11.013422 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:52:41.013322 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:53:11.013385 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:53:41.013420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:54:11.013356 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:54:11.195154 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnfmgr/runtime_mgr.log
2022/04/02 03:54:16.168566 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.168599 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:17.172096 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:17.172139 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:19.179302 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:19.179357 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:23.183334 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:23.183515 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:31.186777 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:31.186817 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:41.013592 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:47.193233 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:47.193270 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:11.013502 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:55:19.197162 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:19.197325 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:41.013632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:56:11.013583 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:56:19.203044 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:19.203134 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:41.013440 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:57:11.013455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:57:19.206451 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:19.206485 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:41.013523 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:58:11.013458 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:58:19.209837 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:19.209886 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:41.013491 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:59:11.013355 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 03:59:16.206255 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfm-vnfmgr/runtime_mgr.log. Closing because close_inactive of 5m0s reached.
2022/04/02 03:59:19.217479 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:19.217537 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:41.013493 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:11.013498 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:00:19.220634 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:19.220766 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:41.013628 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:01:11.013408 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:01:19.223871 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:19.223904 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:41.013491 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:02:11.013370 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:02:19.227247 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:19.227286 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:41.013413 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:03:11.013370 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:03:19.231099 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:19.231159 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:41.020343 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:04:11.013468 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:04:19.234856 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:19.234914 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:41.013962 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:05:11.013935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:05:19.238657 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:19.238722 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:41.013670 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:06:11.013850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:06:19.242454 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:19.242522 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:41.013805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:07:11.013846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:07:19.245586 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:19.245623 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:41.013940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:08:11.013973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:08:19.248883 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:19.248920 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:41.013397 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:09:11.013420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:09:19.253121 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:19.253163 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:41.013412 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:10:11.013333 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:10:19.256253 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:19.256291 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:41.013404 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:11:11.013416 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:11:19.268688 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:19.268723 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:41.013446 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:12:11.013412 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:12:19.274735 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:19.274892 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:41.013408 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:13:11.013361 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:13:19.287337 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.287721 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:41.013484 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:14:11.013399 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:14:19.291478 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.291542 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:41.013507 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:15:11.013491 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:15:19.295742 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.296490 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:41.013798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:16:11.013561 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:16:19.301901 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.302075 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:41.013538 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:17:11.013643 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:17:19.306565 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.306614 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:41.013641 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:18:11.013598 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:18:19.310397 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.310434 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:41.013388 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:19:11.013432 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:19:19.313823 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.313868 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:41.013294 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:20:11.013397 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:20:19.316770 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.316835 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:41.013385 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:21:11.013476 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:21:19.320597 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.320638 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:41.013391 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:22:11.013414 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:22:19.324697 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.324729 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:41.013640 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:23:11.013319 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:23:19.328186 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.328220 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:41.013395 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:24:11.013426 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:24:19.332127 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.332205 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:41.014208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:25:11.013488 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:25:19.339109 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.339147 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:41.013556 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:26:11.013442 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:26:19.343135 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.343187 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:41.013395 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:27:11.013421 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:27:19.349858 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.350026 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:41.013613 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:28:11.013731 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:28:19.362743 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.362784 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:41.013419 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:29:11.013444 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:29:19.366893 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.366945 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:41.013481 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:30:11.013403 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:30:19.370245 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.370285 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:41.013380 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:31:11.013417 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:31:19.373443 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.373482 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:41.013400 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:32:11.013385 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:32:19.376751 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.376785 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:41.013443 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:33:11.013387 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:33:19.380862 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.380951 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:41.013452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:34:11.013596 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:34:19.386838 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.386890 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:41.013407 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:35:11.013433 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:35:19.392720 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.392840 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:41.013500 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:36:11.013516 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:36:19.407045 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.407088 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:41.013453 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:37:11.013498 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:37:19.411783 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.411818 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:41.013467 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:38:11.013405 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:38:19.417110 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.417151 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:41.013384 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:39:11.013470 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:39:19.422540 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.422623 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:41.013510 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:40:11.013370 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:40:19.426681 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.426726 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:41.013454 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:41:11.013408 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:41:19.430834 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.430922 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:41.013552 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:42:11.013417 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:42:19.436337 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.436433 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:41.013356 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:43:11.013337 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:43:19.440083 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.440121 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:41.013339 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:44:11.013572 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:44:19.444635 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.444685 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:41.013428 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:45:11.013689 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:45:19.448011 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.448047 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:41.013539 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:46:11.013446 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:46:19.451903 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.451937 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:41.013451 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:47:11.013456 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:47:19.457026 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.457102 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:41.014296 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:48:11.013392 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:48:19.461266 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.461317 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:41.013420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:49:11.013399 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:49:19.465499 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.465544 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:41.013521 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:50:11.013605 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:50:19.469888 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.470095 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:41.013412 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:51:11.013458 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:51:19.473264 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.473306 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:41.013428 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:52:11.013445 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:52:19.478609 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.478657 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:41.013456 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:53:11.013419 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:53:19.482373 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.482416 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:41.013377 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:54:11.013378 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:54:19.486256 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.486291 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:41.013406 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:55:11.013927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:55:19.491878 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.491916 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:41.013472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:56:11.013352 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:56:19.496378 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.496421 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:41.013574 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:57:11.013533 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:57:19.505840 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.505875 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:41.013481 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:58:11.013477 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:58:19.509840 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.509873 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:41.013547 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:59:11.014398 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 04:59:19.513743 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.513920 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:41.013511 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:00:11.013404 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:00:19.518900 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.518954 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:41.013458 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:01:11.013930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:01:19.523555 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.523619 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:41.013499 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:02:11.013393 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:02:19.526765 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.526808 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:41.013398 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:03:11.013426 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:03:19.530089 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.530423 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:41.013490 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:04:11.013331 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:04:19.533724 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.534023 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:41.013407 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:05:11.013386 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:05:19.539055 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:19.539092 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:41.013471 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:06:11.014403 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:06:19.543061 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:19.543097 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:41.013380 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:07:11.013408 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:07:19.546287 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:19.546326 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:41.014145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:08:11.013367 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:08:19.549581 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:19.549614 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:41.013463 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:09:11.014656 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:09:19.555900 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:19.555979 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:41.013433 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:10:11.013423 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:10:19.561475 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:19.561519 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:41.013397 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:11:11.013436 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:11:19.564596 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:19.564656 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:41.013506 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:12:11.013599 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:12:19.568373 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:19.568415 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:41.013366 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:13:11.013402 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:13:19.572129 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:19.572168 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:41.013470 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:14:11.013509 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:14:19.576757 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:19.576895 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:41.013472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:15:11.013651 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:15:19.580716 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:19.580769 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:41.013406 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:16:11.013385 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:16:19.584133 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:19.584171 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:41.013416 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:17:11.013442 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:17:19.589061 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:19.589242 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:41.014319 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:18:11.014061 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:18:19.593340 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:19.593397 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:41.013338 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:19:11.013588 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:19:19.597164 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:19.597205 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:41.013721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:20:11.013457 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:20:19.601757 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:19.601909 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:41.013487 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:21:11.014074 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:21:19.606209 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:19.606286 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:41.013552 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:22:11.013430 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:22:19.609589 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:19.609637 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:41.013368 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:23:11.013402 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:23:19.614097 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:19.614151 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:41.013487 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:24:11.013397 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:24:19.618065 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:19.618188 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:41.013616 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:25:11.013407 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:25:19.622070 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:19.622112 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:41.013400 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:26:11.013461 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:26:19.626429 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:19.626466 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:41.013385 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:27:11.013349 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:27:19.630300 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:19.630458 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:41.013394 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:28:11.013383 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:28:19.634390 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:19.634427 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:41.013414 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:29:11.013402 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:29:19.640753 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:19.640816 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:41.013398 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:30:11.014266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:30:19.644139 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:19.644271 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:41.013501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:31:11.013465 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:31:19.647885 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:19.647922 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:41.013456 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:32:11.013481 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:32:19.652582 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:19.652617 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:41.013445 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:33:11.013374 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:33:19.657280 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:19.657317 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:41.013439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:34:11.013437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:34:19.661244 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:19.661280 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:41.013342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:35:11.013463 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:35:19.665054 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:19.665252 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:41.013503 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:36:11.013698 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:36:19.669297 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:19.669332 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:41.013353 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:37:11.013376 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:37:19.672920 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:19.672974 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:41.013426 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:38:11.013484 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:38:19.678290 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:19.678329 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:41.013465 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:39:11.013400 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:39:19.682595 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:19.682665 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:41.013436 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:40:11.013512 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:40:19.686489 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:19.686534 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:41.013434 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:41:11.013380 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:41:19.690609 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:19.690654 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:41.013509 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:42:11.013672 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:42:19.694825 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:19.694887 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:41.013418 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:43:11.013428 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:43:19.699136 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:19.699541 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:41.013481 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:44:11.013439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:44:19.703444 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:19.703503 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:41.013527 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:45:11.013396 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:45:19.707538 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:19.707575 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:41.013430 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:46:11.013477 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:46:19.711358 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:19.711403 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:41.013340 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:47:11.013379 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:47:19.714844 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:19.714897 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:41.013594 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:48:11.013401 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:48:19.718071 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:19.718112 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:41.013401 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:49:11.013402 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:49:19.722032 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:19.722063 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:41.013453 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:50:11.013524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:50:19.726246 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:19.726287 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:41.013449 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:51:11.013360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:51:19.729615 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:19.729658 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:41.013365 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:52:11.013406 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/02 05:52:19.733911 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:19.733949 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host