Results

          2022/03/16 03:27:00.675631 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:27:00.675696 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/16 03:27:00.675842 logstash.go:90: INFO Max Retries set to: 3
2022/03/16 03:27:00.676065 metrics.go:23: INFO Metrics logging every 30s
2022/03/16 03:27:00.676220 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/16 03:27:00.676437 publish.go:295: INFO Publisher name: onap-vfc-vnfmgr-8594ffd488-tqt7n
2022/03/16 03:27:00.676751 async.go:63: INFO Flush Interval set to: 1s
2022/03/16 03:27:00.676793 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/16 03:27:00.677640 beat.go:221: INFO filebeat start running.
2022/03/16 03:27:00.677760 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/16 03:27:00.689032 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/16 03:27:00.689187 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/16 03:27:00.689304 crawler.go:38: INFO Loading Prospectors: 1
2022/03/16 03:27:00.689536 registrar.go:236: INFO Starting Registrar
2022/03/16 03:27:00.689612 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/16 03:27:00.689659 sync.go:41: INFO Start sending events to output
2022/03/16 03:27:00.689740 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/16 03:27:00.689762 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/16 03:27:00.689809 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/16 03:27:00.690497 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnfmgr/runtime_mgr.log
2022/03/16 03:27:30.676611 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:28:00.676751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:28:30.676496 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:29:00.676523 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:29:30.676660 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:30:00.676659 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:30:30.676500 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:31:00.676474 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:31:30.676544 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:32:00.676689 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:32:05.708710 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfm-vnfmgr/runtime_mgr.log. Closing because close_inactive of 5m0s reached.
2022/03/16 03:32:30.676857 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:33:00.676758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:33:30.676492 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:34:00.677156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:34:30.676565 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:35:00.676494 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:35:30.676415 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:36:00.676416 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:36:30.676548 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:37:00.676489 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:37:30.676543 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:38:00.677071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:38:30.676441 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:39:00.676521 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:39:30.676523 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:40:00.676923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:40:30.676326 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:41:00.676830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:41:30.676378 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:42:00.677555 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:42:30.676508 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:43:00.676320 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:43:30.676801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:44:00.676667 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:44:30.676420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:45:00.676678 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:45:30.676410 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:46:00.676505 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:46:30.676686 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:47:00.677231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:47:30.676540 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:48:00.676391 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:48:30.676407 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:49:00.676711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:49:30.676434 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:50:00.677116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:50:30.676572 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:51:00.676568 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:51:30.676506 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:52:00.676450 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:52:30.676555 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:53:00.676645 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:53:30.676518 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:54:00.676522 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:54:30.676364 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:55:00.676445 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:55:30.676722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:56:00.678550 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:56:30.682748 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:57:00.677608 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:57:10.957984 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnfmgr/runtime_mgr.log
2022/03/16 03:57:15.939722 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:15.939784 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:16.946543 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.946603 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:18.959281 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:18.959341 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:22.975486 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:22.975544 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:30.676605 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:31.001703 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.001758 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.026534 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.026583 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:00.676484 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:58:19.046094 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.046167 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:30.676676 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:59:00.676488 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 03:59:19.064712 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.064774 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:30.676427 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:00:00.676538 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:00:19.095697 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.095751 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:30.676575 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:01:00.676643 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:01:19.115001 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.115040 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:30.677970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:02:00.682485 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:02:19.136808 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.136875 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:30.676449 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:03:00.676543 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:03:19.156567 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.156614 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:30.682617 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:04:00.676358 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:04:19.179683 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.179739 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:30.676518 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:05:00.676657 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:05:19.201915 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.202045 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:30.676726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:05:55.994108 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfm-vnfmgr/runtime_mgr.log. Closing because close_inactive of 5m0s reached.
2022/03/16 04:06:00.676492 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:19.223072 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.223136 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:30.676673 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:07:00.678528 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:07:19.247598 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.247787 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:30.678647 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:08:00.676467 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:08:19.268053 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.268123 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:30.676427 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:09:00.676420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:09:19.287750 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.287841 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:30.676413 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:10:00.676466 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:10:19.307122 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.307187 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:30.676400 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:11:00.676467 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:11:19.326569 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.326621 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:30.677606 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:12:00.676409 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:12:19.348500 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.348559 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:30.677851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:13:00.677578 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:13:19.375197 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.375254 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:30.676530 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:14:00.676489 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:14:19.414309 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.414374 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:30.676693 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:15:00.677342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:15:19.439043 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.439100 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:30.690522 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:16:00.677037 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:16:19.458736 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.458892 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:30.676582 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:17:00.676796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:17:19.485116 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.485272 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:30.676508 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:18:00.676600 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:18:19.510811 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.510858 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:30.676462 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:19:00.681095 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:19:19.567697 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.567875 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:30.676674 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:20:00.678573 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:20:19.589135 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.589199 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:30.676615 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:21:00.911870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:21:19.609463 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.609864 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:30.676796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:22:00.676577 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:22:19.640393 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.640772 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:30.676783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:23:00.677360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:23:19.667908 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.667949 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:30.676399 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:24:00.676358 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:24:19.701257 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.701324 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:30.677045 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:25:00.676512 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:25:19.726674 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:19.727008 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:30.678592 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:26:00.676429 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:26:21.752340 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:21.752414 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:30.676641 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:27:00.676739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:27:21.772521 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:21.772585 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:30.676449 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:28:00.676613 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:28:21.793901 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:21.793972 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:30.676344 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:29:00.676502 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:29:21.816347 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:21.816419 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:30.676482 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:30:00.676519 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:30:21.833997 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:21.834063 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:30.676732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:31:00.676457 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:31:21.853579 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:21.853644 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:30.676446 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:32:00.676545 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:32:21.873167 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:21.873232 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:30.676467 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:33:00.676385 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:33:21.897512 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:21.897561 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:30.676426 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:34:00.676470 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:34:21.917100 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:21.917173 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:30.676735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:35:00.676584 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:35:21.941482 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:21.941542 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:30.676505 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:36:00.676402 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:36:21.966513 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:21.966579 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:30.676524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:37:00.676546 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:37:21.991722 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:21.991809 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:30.676509 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:38:00.676472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:38:22.012755 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:22.012806 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:30.676444 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:39:00.677370 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:39:22.030844 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:22.030902 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:30.676390 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:40:00.676983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/16 04:40:22.051035 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:22.051092 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:30.676472 metrics.go:34: INFO No non-zero metrics in the last 30s