2022/04/05 03:11:33.387498 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/05 03:11:33.387573 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/04/05 03:11:33.387642 logstash.go:90: INFO Max Retries set to: 3
2022/04/05 03:11:33.387717 outputs.go:108: INFO Activated logstash as output plugin.
2022/04/05 03:11:33.388054 metrics.go:23: INFO Metrics logging every 30s
2022/04/05 03:11:33.388427 publish.go:295: INFO Publisher name: onap-vfc-nslcm-54bbdbd75d-2vh86
2022/04/05 03:11:33.389010 async.go:63: INFO Flush Interval set to: 1s
2022/04/05 03:11:33.389056 async.go:64: INFO Max Bulk Size set to: 2048
2022/04/05 03:11:33.389825 beat.go:221: INFO filebeat start running.
2022/04/05 03:11:33.389980 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/04/05 03:11:33.394308 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/04/05 03:11:33.394359 registrar.go:123: INFO States Loaded from registrar: 0
2022/04/05 03:11:33.394528 crawler.go:38: INFO Loading Prospectors: 1
2022/04/05 03:11:33.394935 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/04/05 03:11:33.395203 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/04/05 03:11:33.395372 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/04/05 03:11:33.395525 registrar.go:236: INFO Starting Registrar
2022/04/05 03:11:33.395561 sync.go:41: INFO Start sending events to output
2022/04/05 03:11:33.395801 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/04/05 03:11:33.396684 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/nslcm/runtime_nslcm.log
2022/04/05 03:12:03.388915 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/05 03:12:33.388621 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:13:03.388584 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:13:33.388522 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:14:03.388585 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:14:33.388584 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:15:03.388552 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:15:33.388669 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:16:03.388581 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:16:33.388553 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:16:38.408293 log.go:116: INFO File is inactive: /var/log/onap/vfc/nslcm/runtime_nslcm.log. Closing because close_inactive of 5m0s reached.
2022/04/05 03:17:03.388836 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/05 03:17:33.388727 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:18:03.388958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:18:33.388511 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:19:03.388541 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:19:33.388473 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:20:03.388550 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:20:33.388450 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:21:03.388532 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:21:33.388788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:22:03.388542 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:22:33.388775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:23:03.388799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:23:33.388448 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:24:03.388567 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:24:33.388586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:25:03.388590 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:25:33.388602 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:26:03.390708 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:26:33.388433 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:27:03.388600 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:27:33.388493 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:28:03.388533 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:28:33.388637 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:29:03.388596 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:29:33.388501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:30:03.388565 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:30:33.388496 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:31:03.388558 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:31:33.388534 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:32:03.388542 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:32:33.388739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:33:03.388473 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:33:33.389081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:34:03.388632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:34:33.388566 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:35:03.388605 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:35:33.388464 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:36:03.388554 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:36:33.388511 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:37:03.388562 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:37:33.389837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:38:03.388475 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:38:33.388521 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:39:03.388600 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:39:33.388517 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:40:03.388747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:40:03.590457 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/nslcm/runtime_nslcm.log
2022/04/05 03:40:08.565104 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:40:08.565143 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:40:09.582603 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:40:09.582668 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:40:11.586731 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:40:11.586771 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:40:15.603242 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:40:15.603279 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:40:23.610438 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:40:23.610485 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:40:33.388569 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/05 03:40:39.637101 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:40:39.637181 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:41:03.388645 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:41:11.646031 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:41:11.646070 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:41:33.388612 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:42:03.388506 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:42:11.652726 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:42:11.652769 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:42:33.388739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:43:03.388527 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:43:11.660294 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:43:11.660333 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:43:33.388533 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:44:03.388504 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:44:11.669398 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:44:11.669457 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:44:33.388542 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:45:03.388497 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:45:08.607008 log.go:116: INFO File is inactive: /var/log/onap/vfc/nslcm/runtime_nslcm.log. Closing because close_inactive of 5m0s reached.
2022/04/05 03:45:11.675176 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:45:11.675212 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:45:33.388538 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/05 03:46:03.388595 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:46:11.683261 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:46:11.683307 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:46:33.388439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:47:03.388461 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:47:11.690801 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:47:11.690853 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:47:33.388475 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:48:03.388654 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:48:11.697283 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:48:11.697325 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:48:33.388745 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:49:03.388764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:49:11.703575 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:49:11.703626 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:49:33.388532 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:50:03.388485 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:50:11.710428 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:50:11.710463 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:50:33.388542 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:51:03.388616 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:51:11.717540 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:51:11.717601 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:51:33.388543 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:52:03.388522 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:52:11.729363 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:52:11.729405 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:52:33.388498 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:53:03.388415 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:53:11.736135 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:53:11.736189 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:53:33.388927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:54:03.388676 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:54:11.743700 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:54:11.743742 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:54:33.388798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:55:03.388529 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:55:11.750349 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:55:11.750406 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:55:33.388557 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:56:03.388857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:56:11.758280 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:56:11.758320 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:56:33.388579 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:57:03.388619 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:57:11.767509 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:57:11.767565 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:57:33.388599 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:58:03.388553 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:58:11.773856 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:58:11.773897 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:58:33.388559 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:59:03.388684 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:59:11.779548 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:59:11.779587 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:59:33.388591 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:00:03.388584 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:00:11.788460 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:00:11.788509 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:00:33.388769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:01:03.388493 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:01:11.794513 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:01:11.794567 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:01:33.388544 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:02:03.388523 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:02:11.801217 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:02:11.801268 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:02:33.388574 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:03:03.388460 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:03:11.807454 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:03:11.807505 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:03:33.388722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:04:03.388567 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:04:11.815299 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:04:11.815368 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:04:33.388468 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:05:03.388484 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:05:11.822543 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:05:11.822589 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:05:33.388464 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:06:03.388479 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:06:11.829303 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:06:11.829349 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:06:33.388533 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:07:03.388525 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:07:11.836259 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:07:11.836310 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:07:33.388468 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:08:03.388551 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:08:11.846675 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:08:11.846713 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:08:33.388489 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:09:03.388570 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:09:11.855818 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:09:11.855868 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:09:33.388475 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:10:03.388855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:10:11.861753 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:10:11.861794 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:10:33.388521 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:11:03.388535 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:11:11.869715 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:11:11.869750 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:11:33.388510 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:12:03.388671 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:12:11.877694 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:12:11.877738 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:12:33.388691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:13:03.388598 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:13:11.887201 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:13:11.887246 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:13:33.388477 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:14:03.388546 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:14:11.894486 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:14:11.894570 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:14:33.388508 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:15:03.388579 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:15:11.901602 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:15:11.901662 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:15:33.388483 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:16:03.388632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:16:11.914425 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:16:11.914561 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:16:33.388520 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:17:03.388478 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:17:11.920630 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:17:11.920668 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:17:33.391069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:18:03.388473 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:18:11.926939 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:18:11.926984 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:18:33.388573 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:19:03.388592 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:19:11.933822 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:19:11.933862 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:19:33.388498 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:20:03.388463 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:20:11.940349 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:20:11.940451 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:20:33.388617 metrics.go:34: INFO No non-zero metrics in the last 30s