Results

          2022/04/05 03:11:00.536004 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:00.536071 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/04/05 03:11:00.536179 metrics.go:23: INFO Metrics logging every 30s
2022/04/05 03:11:00.536198 logstash.go:90: INFO Max Retries set to: 3
2022/04/05 03:11:00.536331 outputs.go:108: INFO Activated logstash as output plugin.
2022/04/05 03:11:00.536541 publish.go:295: INFO Publisher name: onap-vfc-zte-vnfm-driver-65d7c4d97b-hfhdm
2022/04/05 03:11:00.536850 async.go:63: INFO Flush Interval set to: 1s
2022/04/05 03:11:00.536883 async.go:64: INFO Max Bulk Size set to: 2048
2022/04/05 03:11:00.537465 beat.go:221: INFO filebeat start running.
2022/04/05 03:11:00.537542 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/04/05 03:11:00.552748 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/04/05 03:11:00.552865 registrar.go:123: INFO States Loaded from registrar: 0
2022/04/05 03:11:00.552915 crawler.go:38: INFO Loading Prospectors: 1
2022/04/05 03:11:00.552976 registrar.go:236: INFO Starting Registrar
2022/04/05 03:11:00.553174 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/04/05 03:11:00.553209 sync.go:41: INFO Start sending events to output
2022/04/05 03:11:00.553295 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/04/05 03:11:00.553455 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/04/05 03:11:00.553501 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/04/05 03:11:00.554235 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log
2022/04/05 03:11:30.536858 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:00.536541 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:12:30.536854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:13:00.536711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:13:30.536575 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:14:00.536487 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:14:30.536554 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:15:00.536938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:15:30.536499 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:16:00.536532 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:16:05.568083 log.go:116: INFO File is inactive: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log. Closing because close_inactive of 5m0s reached.
2022/04/05 03:16:30.536547 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:00.536595 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:17:30.536517 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:18:00.536518 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:18:30.537168 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:19:00.536536 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:19:30.536435 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:20:00.536535 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:20:30.536537 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:21:00.536547 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:21:30.536516 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:22:00.536440 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:22:30.536458 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:23:00.536466 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:23:30.536446 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:24:00.536496 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:24:30.536478 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:25:00.536515 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:25:30.536514 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:26:00.536491 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:26:30.536564 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:27:00.536438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:27:30.536557 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:28:00.536542 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:28:30.536744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:29:00.536638 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:29:30.536550 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:30:00.536516 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:30:30.536489 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:31:00.536459 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:31:30.536688 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:32:00.536486 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:32:30.536549 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:33:00.537152 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:33:30.536493 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:34:00.536454 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:34:30.536558 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:35:00.536511 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:35:30.536618 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:36:00.536520 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:36:30.536431 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:37:00.536534 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:37:30.536675 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:38:00.536541 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:38:30.536433 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:39:00.536694 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:39:30.536751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:40:00.536473 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:40:00.705258 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log
2022/04/05 03:40:05.685558 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:05.685618 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:06.690424 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:06.690541 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:08.697292 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.697344 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:12.708045 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:12.708095 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:20.714793 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:20.714832 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:30.536510 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:36.732875 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:36.733074 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:00.536495 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:41:08.751147 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:08.751203 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:30.536491 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:42:00.536565 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:42:08.768525 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:08.768575 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:30.536454 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:43:00.536466 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:43:08.789050 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:08.789322 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:30.536503 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:44:00.536533 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:44:08.807011 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:08.807051 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:30.536540 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:45:00.536546 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:45:05.718537 log.go:116: INFO File is inactive: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log. Closing because close_inactive of 5m0s reached.
2022/04/05 03:45:08.826041 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:08.826113 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:30.536539 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:00.536678 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:46:08.844581 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:08.844640 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:30.536500 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:47:00.536582 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:47:08.862996 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:08.863041 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:30.536480 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:48:00.536538 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:48:08.881835 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:08.881892 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:30.536521 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:49:00.536507 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:49:08.899646 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:08.899711 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:30.536465 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:50:00.536467 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:50:08.921137 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:08.921199 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:30.536606 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:51:00.536623 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:51:08.938688 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:08.938731 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:30.536423 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:52:00.536444 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:52:08.960869 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:08.960927 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:30.536486 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:53:00.536480 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:53:08.979027 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:08.979069 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:30.536504 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:54:00.536602 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:54:09.000899 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:09.000951 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:30.536686 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:55:00.536489 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:55:09.021467 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:09.021525 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:30.536628 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:56:00.536597 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:56:09.046150 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:09.046211 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:30.536456 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:57:00.537952 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:57:09.072492 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:09.072538 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:30.536537 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:58:00.536477 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:58:09.090776 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:09.090822 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:30.537886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:59:00.537652 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:59:09.111091 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:09.111143 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:30.536555 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:00:00.536510 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:00:09.132017 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:09.132088 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:30.536564 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:01:00.536475 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:01:09.158507 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:09.158553 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:30.536495 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:02:00.536456 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:02:09.183144 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:09.183238 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:30.536545 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:03:00.536524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:03:09.203429 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:09.203485 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:30.536507 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:04:00.536466 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:04:09.222076 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:09.222132 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:30.536557 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:05:00.536443 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:05:09.243334 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:09.243394 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:30.536578 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:06:00.536534 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:06:09.264039 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:09.264094 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:30.536522 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:07:00.536582 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:07:09.284569 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:09.284620 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:30.536504 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:08:00.536517 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:08:09.305133 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:09.305256 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:30.536521 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:09:00.537012 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:09:09.323379 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:09.323419 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:30.536484 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:10:00.536531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:10:09.340699 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:09.340737 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:30.536632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:11:00.536483 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:11:09.357795 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:09.357836 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:30.536510 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:12:00.536457 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:12:09.374340 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:09.374382 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:30.536505 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:13:00.537463 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:13:09.395333 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:09.395387 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:30.536557 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:14:00.536586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:14:09.414655 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:09.414810 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:30.536453 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:15:00.536622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:15:09.440846 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:09.440915 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:30.536499 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:16:00.536484 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:16:09.462489 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:09.462567 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:30.536700 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:17:00.536568 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:17:09.482555 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:09.482611 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:30.536545 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:18:00.536508 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:18:09.503443 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:09.503501 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:30.536459 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:19:00.536684 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:19:09.522000 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:09.522068 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:30.536801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:20:00.536558 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:20:09.543827 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:09.543874 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:30.536495 metrics.go:34: INFO No non-zero metrics in the last 30s