2022/03/16 03:26:51.185574 beat.go:285: INFO Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs] 2022/03/16 03:26:51.185629 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0 2022/03/16 03:26:51.185714 logstash.go:90: INFO Max Retries set to: 3 2022/03/16 03:26:51.185799 outputs.go:108: INFO Activated logstash as output plugin. 2022/03/16 03:26:51.185915 publish.go:295: INFO Publisher name: onap-vfc-zte-vnfm-driver-65d7c4d97b-jlzzx 2022/03/16 03:26:51.186072 metrics.go:23: INFO Metrics logging every 30s 2022/03/16 03:26:51.186268 async.go:63: INFO Flush Interval set to: 1s 2022/03/16 03:26:51.186293 async.go:64: INFO Max Bulk Size set to: 2048 2022/03/16 03:26:51.187667 beat.go:221: INFO filebeat start running. 2022/03/16 03:26:51.187865 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file. 2022/03/16 03:26:51.194804 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry 2022/03/16 03:26:51.194880 registrar.go:123: INFO States Loaded from registrar: 0 2022/03/16 03:26:51.194909 crawler.go:38: INFO Loading Prospectors: 1 2022/03/16 03:26:51.195136 prospector_log.go:65: INFO Prospector with previous states loaded: 0 2022/03/16 03:26:51.195256 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 2022/03/16 03:26:51.195297 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1 2022/03/16 03:26:51.199763 registrar.go:236: INFO Starting Registrar 2022/03/16 03:26:51.199874 sync.go:41: INFO Start sending events to output 2022/03/16 03:26:51.199936 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s 2022/03/16 03:26:51.200939 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log 2022/03/16 03:27:21.186860 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/03/16 03:27:51.186506 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:28:21.186504 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:28:51.186688 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:29:21.188277 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:29:51.187454 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:30:21.186599 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:30:51.186471 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:31:21.186476 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:31:51.186659 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:31:56.220313 log.go:116: INFO File is inactive: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log. Closing because close_inactive of 5m0s reached. 2022/03/16 03:32:21.186535 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/03/16 03:32:51.186440 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:33:21.186453 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:33:51.186745 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:34:21.188238 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:34:51.186519 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:35:21.186438 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:35:51.186385 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:36:21.186453 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:36:51.186586 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:37:21.186453 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:37:51.186377 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:38:21.186489 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:38:51.186541 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:39:21.186449 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:39:51.186431 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:40:21.186643 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:40:51.186583 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:41:21.186394 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:41:51.186465 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:42:21.186465 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:42:51.186382 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:43:21.186421 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:43:51.186635 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:44:21.186497 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:44:51.186538 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:45:21.186376 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:45:51.186509 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:46:21.186633 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:46:51.186488 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:47:21.186546 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:47:51.186413 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:48:21.186543 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:48:51.186344 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:49:21.186400 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:49:51.186612 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:50:21.186361 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:50:51.186388 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:51:21.186440 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:51:51.186367 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:52:21.186418 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:52:51.186527 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:53:21.186443 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:53:51.186406 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:54:21.186421 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:54:51.186375 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:55:21.186410 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:55:51.186363 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:56:21.186353 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:56:51.186533 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:57:11.405527 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log 2022/03/16 03:57:16.368396 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 03:57:16.368440 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 03:57:17.376559 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 03:57:17.376593 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 03:57:19.380381 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 03:57:19.380420 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 03:57:21.186534 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/03/16 03:57:23.384947 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 03:57:23.385000 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 03:57:31.393614 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 03:57:31.394048 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 03:57:47.412118 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 03:57:47.412158 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 03:57:51.186409 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:58:19.430897 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 03:58:19.430942 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 03:58:21.186461 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:58:51.186523 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:59:19.451674 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 03:59:19.451717 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 03:59:21.186514 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 03:59:51.186607 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:00:19.483712 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:00:19.483755 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:00:21.186363 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:00:51.186378 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:01:19.506000 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:01:19.506054 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:01:21.186358 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:01:51.186457 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:02:19.528566 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:02:19.528619 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:02:21.186424 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:02:51.186445 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:03:19.549704 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:03:19.549746 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:03:21.186397 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:03:51.186421 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:04:19.568802 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:04:19.568858 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:04:21.186437 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:04:51.186606 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:05:19.585720 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:05:19.585780 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:05:21.186344 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:05:51.186634 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:05:56.432850 log.go:116: INFO File is inactive: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log. Closing because close_inactive of 5m0s reached. 2022/03/16 04:06:19.604082 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:06:19.604154 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:06:21.186486 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/03/16 04:06:51.186515 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:07:19.625395 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:07:19.625433 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:07:21.186384 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:07:51.186382 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:08:19.642334 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:08:19.642513 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:08:21.186470 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:08:51.186438 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:09:19.661842 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:09:19.661886 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:09:21.186565 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:09:51.186575 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:10:19.683950 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:10:19.683996 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:10:21.186398 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:10:51.186505 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:11:19.706086 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:11:19.706130 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:11:21.186450 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:11:51.186401 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:12:19.726626 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:12:19.726668 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:12:21.186421 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:12:51.186469 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:13:19.754919 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:13:19.754963 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:13:21.186349 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:13:51.186629 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:14:19.775357 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:14:19.775516 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:14:21.186454 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:14:51.186432 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:15:19.793920 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:15:19.793978 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:15:21.186482 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:15:51.186373 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:16:19.815857 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:16:19.815907 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:16:21.186362 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:16:51.186448 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:17:19.838843 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:17:19.838947 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:17:21.186468 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:17:51.186529 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:18:19.858674 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:18:19.858730 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:18:21.186360 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:18:51.186943 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:19:19.881923 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:19:19.881966 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:19:21.186516 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:19:51.186443 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:20:19.902315 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:20:19.902357 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:20:21.186476 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:20:51.186527 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:21:19.922982 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:21:19.923051 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:21:21.186458 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:21:51.186405 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:22:19.945284 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:22:19.945353 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:22:21.186470 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:22:51.186396 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:23:19.973919 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:23:19.973992 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:23:21.186443 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:23:51.186337 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:24:19.993866 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:24:19.993928 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:24:21.186534 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:24:51.186486 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:25:20.016302 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:25:20.016357 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:25:21.186466 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:25:51.186361 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:26:20.038025 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:26:20.038072 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:26:21.186410 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:26:51.186581 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:27:20.058456 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:27:20.058512 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:27:21.186383 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:27:51.186345 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:28:20.078196 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:28:20.078250 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:28:21.186410 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:28:51.186485 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:29:20.098211 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:29:20.098267 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:29:21.186508 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:29:51.186817 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:30:20.117498 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:30:20.117560 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:30:21.186401 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:30:51.186508 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:31:20.138241 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:31:20.138297 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:31:21.186455 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:31:51.186492 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:32:20.159192 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:32:20.159267 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:32:21.186406 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:32:51.186371 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:33:20.190122 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:33:20.190173 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:33:21.186362 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:33:51.186391 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:34:20.214785 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:34:20.214841 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:34:21.186390 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:34:51.186488 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:35:20.234077 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:35:20.234246 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:35:21.186491 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:35:51.186350 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:36:20.257373 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:36:20.257456 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:36:21.186531 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:36:51.186365 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:37:20.275881 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:37:20.276109 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:37:21.188087 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:37:51.186373 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:38:20.295926 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:38:20.295979 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:38:21.186385 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:38:51.186382 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:39:20.314858 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:39:20.314908 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:39:21.186403 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:39:51.186519 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:40:20.340371 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:40:20.340427 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/16 04:40:21.186569 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/16 04:40:51.186429 metrics.go:34: INFO No non-zero metrics in the last 30s